jira-importer commented on issue #661: URL: https://github.com/apache/maven-scm/issues/661#issuecomment-2964611856
**[Mark Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)** commented Petter, pushing to the current branch should already be the default behaviour. We also had a discussion about whether we should add more support for distributed SCMs in maven-scm-api in the future, because bazaar, hg, etc works the same way basically. There are 2 issues: * The current way of always pushing is good for projects like we have here at Apache and a few other pretty centralised projects where basically only 1 main repository exists. But it the project is more a forked pull-it-from-wherever-you-need approach, this probably wont work for the long term. Another idea is that it would make testing releases a lot easier. You do a 'local' release and push it to a staging repo. If all works out fine then you can push the tag to the central repo... * For release:perform we currently do a git-clone from the upstream repo. This may cause some unnecessary traffic (and time). This is not such a big problem for git but for hg and bazaar which performs a lot slower. Since with all DCMS we have the full repo available locally, we may easily checkout into target/checkout from our _local_ repo instead of going to the remote. -- 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]
