jira-importer commented on issue #629: URL: https://github.com/apache/maven-scm/issues/629#issuecomment-2964607882
**[clintgilbert](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=clintgilbert)** commented It makes sense to tag from the local copy, since that's the code that's just been compiled and tested. Someone could have checked in a breaking change to the trunk which you wouldn't want in the release, for instance. But how about this (I'm just brainstorming; I don't know enough about the SCM code to know how feasible this is)? * release:prepare runs, updating poms, removing -SNAPSHOT from versions, etc. * The release plugin checks in the updated poms. If there's an error (the working copy is out of date, say), notify the user to update and re-try release:prepare * The release plugin records the revision number of the commit * The release plugin tags (via a remote URL) the recorded trunk revision as the release * The release plugin updates the needed poms to new snapshot versions and checks them in. I hope there's a fix for this soon; we're fine with SVN 1.4.x for now, but it would be much more convenient to be able to upgrade. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
