-
Notifications
You must be signed in to change notification settings - Fork 13
How to Release the CDR
gregjan edited this page Oct 3, 2011
·
27 revisions
- Go to a cdr master folder:
cd cdr
- or if no cdr folder has been cloned:
git clone git@github.com:UNC-Libraries/Carolina-Digital-Repository.git cdr
cd cdr
- make sure you are on master branch and have no outgoing/incoming changes
- do
git pull
- do
git status
- set the email and user name for the m2e-core local git repository, if not already set
git config -l
git config user.email <your eclipse commiter email address>
git config user.name <your name>
- create a local release branch (not checked out yet)
git branch rb-<version>
- This local branch will not be pushed to the remote repository. It is just a local branch used for this release process.
- update the checked out master branch pom files to the next -SNAPSHOT version.
-
vim pom.xml
(repeat for modules, replace version numbers where they appear) git commit -s -a -m "new version <version+1>-SNAPSHOT"
git push
- checkout the release branch
git checkout rb-<version>
- update checked out release branch pom files to the release version.
-
vim pom.xml
(repeat for modules, replace version numbers where they appear)
- deploy the release artifacts to Artifactory
mvn clean deploy
- commit and tag your changes
git commit -s -a -m "new release <version>"
git tag <version>
- push the release tag
git push origin <version>
- remove release branch if you intend to keep local git repository
git branch -D rb-<version>