[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-tech-pkg
Subject:    Big devel/gradle update
From:       Kevin Bloom <ktnb () posteo ! net>
Date:       2024-03-28 20:18:19
Message-ID: 20240328201819.l0dgQ%ktnb () posteo ! net
[Download RAW message or body]

Hi all,

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].

Thanks,

Kev

[1] https://docs.gradle.org/8.7/release-notes.html
[2] https://docs.gradle.org/7.6.2/release-notes.html
[prev in list] [next in list] [prev in thread] [next in thread]