Hi, First, with every vote for a release, there is a link for the issues fixed in Jira, but I have seen that some links to the Release Notes of Jira, and others just link to the filter of "Fix version" in Jira, to me the link should always be the Release Notes, not the filter of issues.
A second point is that if Jira will be used, each Release Note has a "Copy Release Notes" that can be simply copied over. For example, the Release Notes for Maven 3.9.0 should be https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350913&projectId=12316922 (not the link for the Fix version filter), and there is nothing to "maintained" as Jira already generates the HTML in the "Copy Release Notes" section that can be used to copy/paste on the GitHub release notes, the only point is to include an additional step on the release process that every project should follow and that once the release is "done" this should be copied from Jira to GH, and that's it. Now, a third point, with some bots like dependabot, they don't create a Jira issue automatically, this might or might not be ok depending on each use case (an updated dependency could break something that should be noted in the release notes), so Jira issues fall short on tracking this kind of commits unless someone handles manually the creation of the Jira issue and that is annoying, here I don't see an easy solution since using "GH Generate release notes" or something like "Release Drafter" will differ with Jira Release Notes. In any case, since Jira is the current source of truth, the only reasonable thing to do is to simply use the "Copy Release Notes" section and include it in every release process (assuming the release process is documented somewhere). Regards, On Sun, Feb 12, 2023 at 4:15 PM Slawomir Jaranowski <s.jaranow...@gmail.com> wrote: > > Hi, > > I know the subject is returning again ... > > When we once create GitHub release notes we should maintain it for each new > release ... > I agree the source of truth is our jira release notes. > > In other cases we have missing information about releases and users can be > confused. > > Dependabot uses GitHub releases notes for next PR and we can lose some of > the versions ... like in [1] > > For Maven 3.9.0 we also have no current release notes [2] > probably for other components ... > > [1] https://github.com/mojohaus/mojo-parent/pull/342 > [2] https://github.com/apache/maven/releases > > -- > Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
