or, for trivial changes (fixing a typo, etc.), make changes in master checkout, commit to master (locally), and push to remote?
-Marshall On 11/26/2018 1:47 PM, Marshall Schor wrote: > Hi, > > In the svn world, we have "trunk" and tags. Users make changes to the trunk, > and commit them. The maven release plugin does things with svn, changing > -SNAPSHOT, committing to svn /tags, and the new version to /trunk. > > How does this process work for git? > - should committers push changes to a temp branch, and when done, "rebase" > (unless you want to keep the details of every commit that was done in the > branch), and push to "master"? (This seems to emulate the commit to "trunk"). > > I guess the maven release plugin has some way of working with git; > see > https://stackoverflow.com/questions/39573409/how-to-setup-the-maven-release-plugin-with-git > > Is the process for release to use the same mvn release:prepare, and > release:perform? > > -Marshall >
