Hi, > I agree the source of truth is our jira release notes.
I'm new to maven projects here. If the quoted statement is true, what about just set a link to the JIRA release notes for all GitHub release notes. Then the task is eased and we don't maintain multiple pages with full content. ... or the issue is that the absence of release note ifself that our process can easily miss this step? Best, tison. Slawomir Jaranowski <s.jaranow...@gmail.com> 于2023年2月12日周日 23:15写道： > 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 >
