Re: Big devel/gradle update

[Kevin Bloom <ktnb%posteo.net@localhost>]

>  > I've updated devel/gradle in wip to version 8.7. The version in
>  > -current is currently 6.8.3 and there have been a LOT of updates
>  > since then. Not to mention, each update has its own entire page for
>  > release notes[1]. Granted most of the page is how to upgrade and
>  > how to work with the new version but still there are a lot of updates.
>  > Is there a correct way to handle this in the commit message?
>  > 
>  > I wouldn't be concerned if each version only had a handful of updates
>  > or easy short line explanations but these are like entire
>  > explanations.
>  > 
>  > To be fair, the minor version updates (i.e. 7.6.1 -> 7.6.2) aren't
>  > that bad and have a list[2].
> 
> Since nobody's responded in week...
> 
> I would just say "five years of active development" or whatever and
> include the links. Maybe list some highlights if it's not too much
> trouble to put together.
> 
> Won't be the first package where this has happened.

Okay, thanks!

Kev