gnodet commented on pull request #574: URL: https://github.com/apache/maven-mvnd/pull/574#issuecomment-1009767706
> > Id vote for triggering by a tag, but how about the third option: let release-candidate create the tag itself? > > This is of course possible but here I wonder how will the workflow interact with the Apache Maven release process? I'm not familiar with it so that's why I did not push to automate that part just yet. Who and when is responsible for tagging a repository before a vote is started? > > If the tag happens earlier in the process and IF this workflow creates the tag then the changelog will be ready before the e-mail vote is sent, right? Perhaps @hboutemy may help us clarify this point 😄 I think we can somehow mimic the process with pure maven: when `mvn release:prepare release:perform` is run, the invocation will change the version, create a tag, upload to nexus staging repo. A vote is then started and at the end, the staging repo is published to central and the release to its final destination in the ASF public distribution area. So I think a manual trigger which would set the version and create a tag before building the binaries is fine. We then need to be able to review and vote on the packages which will be published during a next step. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
