...
- Major version number will remain 0 until we make a "marketing" decision that we are calling Synapse production instead of under development. Minor version number will correspond to Sprint number.
- Code should never be deployed to any production system on Amazon directly from a development environment build. All Neither should you ever do a maven deploy directly from a development environment. All deployed artifacts should be produced by a successful Bamboo build and deployed to Artifactory by that build process. Only deploy artifacts to AWS that have been obtained from Artifactory.
- Code from the tip of trunk or a release branch should always have a maven version of 0.x-SNAPSHOT where x is the sprint (minor version) number. Snapshots are stored in libs-snapshots-local/org/sagebionetworks/<path-to-artifact>. Note that every successful Bamboo build overwrites artifactory's snapshots location.
- For weekly dev-team integration deployments, it's not necessary to create a new version. We will simply deploy snapshots off trunk, and include the svn build number and date in the version label when deploying to Beanstalk. Any deployments to customer-facing stacks need to be tagged in SVN and archived in Artifactory. Artifacts for numbered releases are stored in Artifactory in libs-releases-local/org/sagebionetworks/<path-to-artifact>. Note that the branching and tagging patterns described below are designed so that we never overwrite numbered versions in Artifactory after they are generated.
Creating an Initial Minor Release
...