...
- Developers are responsible for down-merging patches to the branch from trunk (or vice versa as appropriate).
- Verify that the most recent check-in on the branch resulted in a clean Bamboo build, and verify with the developer who created the patch that it is in fact checked in.
- Do a svn copy of branches/Synapse-0.x to tags/Synapse-0.x.y
- Reconfigure the Bamboo build of the branch (the "Repository Path" field under "Configuration") to point to tags/Synapse-0.x.y.
- Check out tags/Synapse-0.x.y, then:
- edit tools/SynapseDeployer/pomVersioner.py so that oldVersion=0.x-SNAPSHOT, newVersion=0.x.y, and startPath 'points' to your local copy, then run pomVersioner.py.
- Validate that changes to poms and any version info in R client makes sense
- Check this into SVN. Eclipse will give you a warning that you shouldn't be checking in to a tag. Do it anyway.
- Bamboo should now run a clean build of the tag, which will end up as a permanent versioned artifact in artifactory.
- Reconfigure the Bamboo build to point back to trunkthe branch
- Delete the tag code from your workspace so you never accidentally modify the tagged version again.
- Clean labeled artifacts are sitting in artifactory libs-releases-local/org/sagebionetworks/<path-to-artifact>