I do agree. The real work is doing some triage between sections such as: major changes, bug fixes, dependency updates, build related stuff. Basically, listing most important things at the beginning, and minor things at the end on the GitHub release page. GitHub does a nice thing at generating a skeleton, we just need to order things a bit before publishing the release.
Le lun. 9 déc. 2024 à 18:08, Slawomir Jaranowski <s.jaranow...@gmail.com> a écrit : > On Sun, 8 Dec 2024 at 23:03, Elliotte Rusty Harold <elh...@ibiblio.org> > wrote: > > > > On Sun, Dec 8, 2024 at 9:47 PM Slawomir Jaranowski > > <s.jaranow...@gmail.com> wrote: > > > > > > Hi, > > > > > > I see that more and more PR are not connected to Jira issues ... > > > So we simply take a decision and formally accept what we do > > > > > > > I think that might be simply related to what the PRs do. Accrual bug > > fix and new feature PRs are usually connected to Jira. issues. > > Refactoring and cleanups generally aren't, and that's as it should be > > IMHO. As long as Jira issues are used to create release notes, we > > shouldn't file a Jira issue for anything that doesn't deserve a > > release note, and changes that don't directly impact users of the > > plugin don't deserve release notes. > > > > There's some disagreement about whether dependency upgrades should > > have Jira issues. Personally I think not, both because this doesn't > > directly impact how a user interacts with the plugin, and also because > > dependabot isn't smart enough to do that automatically. If folks > > really, really want Jira issues for every .0.0.1 update, then we might > > as well turn off dependabot. > > > > For me every change should be listed in release notes. > Even dependency upgrade or simple code refactor, cleanups can > introduce bug which can appears for users > > > > -- > > Elliotte Rusty Harold > > elh...@ibiblio.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- > Sławomir Jaranowski > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- ------------------------ Guillaume Nodet
