THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
2. Create release candidate branch
| Code Block |
|---|
git checkout -b 3.2.10-RC1 master |
git push -u origin 3.2.10-RC1 |
3. Build Rya, prepare and perform release
| Code Block |
|---|
mvn clean package -Papache-release |
| Code Block |
|---|
mvn release:prepare |
| Code Block |
|---|
What is the release version for "Apache Rya Project"? (org.apache.rya:rya-project) 3.2.10: : |
What is SCM release tag or label for "Apache Rya Project"? (org.apache.rya:rya-project) v3.2.10: : v3.2.10-RC1 |
What is the new development version for "Apache Rya Project"? (org.apache.rya:rya-project) 3.2.11-SNAPSHOT: : |
| Code Block |
|---|
mvn release:perform |
Once the release has been performed, the artifacts should be in a staging repository:
From "Publishing Maven Artifacts" page:
Now you must close the staging repository to indicate to Nexus that the build is done and to make the artifacts available. Follow the steps in Closing the Staged Repositoryto close your new repository, this will allow your community to VOTE on the staged atrifacts.
If there is something wrong with the staging repo:
delete the tag:
| Code Block |
|---|
git tag -d v3.2.10 |
-RC1 git push origin :refs/tags/v3.2.10-RC1 git branch -D 3.2.10-RC1 git push origin --delete 3.2.10-RC1 |
Rya uses Mini Accumulo Cluster for a number of it's tests and I've run into a number of gotchas:
...