aalmiray commented on issue #542: URL: https://github.com/apache/maven-mvnd/issues/542#issuecomment-1005043027
Correct. We must follow the Apache Maven release process, which means IF convenience binaries are to be posted it must happen after a release vote has been successful. However before or after the vote is done the project has the _choice_ of posting a Git release with changelog. 1. If the Git release is posted BEFORE the vote then if **must** be set as a prerelease (in GitHub terms) and have **no** convenience binary assets. If the vote is canceled or fails then the Git release is dropped. If the vote is successful then the Git release is moved to final and convenience binaries _could_ be uploaded as release assets. 2. If the Git release is posted AFTER the vote passes then it _could_ contain convenience binaries as release assets. These 2 options are a matter of process. The JReleaser tool can help creating the Git releases and uploading the release assets when needed. 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. Final convenience binaries (that is, non snapshots) may be posted to additional distribution channels and package managers such as: Only require a Git repository, GitHub being the preferred option: - Homebrew - Gofish - Macports - Scoop Require a username/password owned by the mvnd team on the given build service associated with the packager: - Chocolatey - Snapcraft - Docker - Fedora COPR All platform packagers are optional. You can pick an choose which ones you'd want to use or none at all. -- 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]
