ppalaga commented on issue #542: URL: https://github.com/apache/maven-mvnd/issues/542#issuecomment-1005491519
As for 1. vs. 2., if a GH release is the only way how to publish the changelog before publishing the binaries, then 1. sounds preferable. It is useful for the voters to read the changelog before they vote and possibly decide based on the information from the changelog. > Now, there's also the matter of shipping convenience binaries for snapshot releases only, such as on every push to a particular branch. Here the JReleaser tool also helps but then again the team should decide if this is worth adding and according to the rules. There is something like that in the current GH Actions workflow: the ZIPs for the infividual platforms are stored as the given Workflow execution's artifacts. See e.g. here in a recent successful build: https://github.com/apache/maven-mvnd/actions/runs/1648385567  The community members voting about a release can use these to manually test the release and adjust their vote based on that. -- 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]
