On Tue, 31 May 2022 at 18:22, Slawomir Jaranowski <[email protected]> wrote:
> wt., 31 maj 2022 o 09:58 Olivier Lamy <[email protected]> napisał(a): > > > On Tue, 31 May 2022 at 02:22, Slawomir Jaranowski < > [email protected]> > > wrote: > > > > > Hi, > > > > > > On page Releasing A Parent POM [1] we have Call the vote template with > > > info: > > > > > > "In the vote, instead of providing links to JIRA, the parent POMs > should > > > include a link to the Git changes since the last release:" > > > > > > It can be understood by someone that we don't need to create release > > notes > > > in jira for parent poms. > > > For historical releases we did release notes in jira, we also sent > > release > > > notes in announcements about poms release. > > > > > > So to be consistent we can: > > > > > > 1. Change template with information that links to the Git changes is > > > additional to the jira link. > > > > or > > > 2. Put clear confirm that we don't need jira release notes and don't > > track > > > issues in jira for parents poms ... > > > > > > > +1 (maybe github release notes generated by release drafter? (well it > works > > if everything has been done via PR otherwise need some manual entries to > be > > added) ) > > > To be clear GitHub releases notes generated by release drafter are > additionally to jira - not instead of. Right? > your 2. says "we do not need jira release notes" as you mention Jita I'm lost now :) frankly not sure we need jira etc.. for parent poms especially plugins or shared etc... Those parent poms are very internal and most of the time the activity is merging dependabot PRs. so just having PRs which automatically generate a release note and voila. > > > > > > > > > > > Please vote for 1 or 2 ... or provide another idea :-) > > > > > > > [1] > > > > > > > > > https://maven.apache.org/developers/release/parent-pom-release.html#call-the-vote > > > > > > -- > > > Sławomir Jaranowski > > > > > > > > -- > Sławomir Jaranowski >
