rroesch1 commented on issue #1422: URL: https://github.com/apache/maven-release/issues/1422#issuecomment-3617012615
@kwin sorry, but this change is totally awkward 😠Yes, there are two commits: * the commit for the next development version (this one is to be pushed to the branch) * the commit for the release version (this one is to be pushed to the tag) In a proper CI setups there are CI pipelines for both commits. i.e.: * one for the branch: this one is supposed the build and deploy the next SNAPSHOT * one for the tag: this one is supposed to build and deploy the new release I really do not get why the latter on should be disabled by default. To me, this looks like a totally pointless change probably raising a lot of confusion and frustration. -- 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]
