ReleaseProcedure

• UPCXX nightly test results

1. Update ChangeLog + version info in README
2. Update nobs default URL to point at EX release tarball
3. Commit final guide PDF to docs/guide.pdf
   1. upload to upcxx/upcxx downloads area with name like upcxx-guide-2017.9.0.pdf
   2. TAG the guide repo
4. Commit final spec PDF to docs/spec.pdf
   1. upload to upcxx/upcxx downloads area with name like upcxx-spec-V1.0-Draft4.pdf
   2. TAG the spec repo
5. Generate source release-candidate tarball (from git working dir)
   Be sure to change version in the following:
   git archive --remote=origin develop --prefix=upcxx-2017.9.0/ --format=tar.gz --output=upcxx-2017.9.0.tar.gz Upload this release candidate to (private) berkeleylab/upcxx downloads area
6. Email local group to review the release-candidate
7. Merge to master (updating version below)
   git remote update
git checkout master
git pull --ff-only
git merge --no-ff -m 'Merge develop for 2017.9.0 release' origin/develop
   (push to a private fork on BitBucket or inspect locally with git log)
   git push origin master
8. TAG master (updating version below)
   git tag -a -m 'UPC++ 2017.9.0 release' upcxx-2017.9.0 master
git push origin upcxx-2017.9.0
9. Generate final tarball
   Same command as release candidate except "master" replaces "develop"
   Be sure to change version in the following:
   git archive --remote=origin master --prefix=upcxx-2017.9.0/ --format=tar.gz --output=upcxx-2017.9.0.tar.gz
   Upload this final release to (public) upcxx/upcxx downloads area
10. Advance patch version number on develop branch in src/upcxx.hpp
11. Change nobs URL back to collaborator-snapshot on develop
12. Review and revise the release announcement
13. Navigate to the wiki and git clone it to your local system
14. Add any new publications (eg updated spec or guide) to wiki/Publications and wiki/pubs
15. Update Download section of wiki/Home.md w/ three links: spec, guide and impl
16. Update all 3 issue trackers: add this release to Versions, next one to Milestones and as default Milestone
17. Update Download section of wiki/Home.md with info on the new release including links
18. Update wiki/{README.md,INSTALL.md,docs/*} with files from the release, overwriting the version there. Be sure to audit the changes before committing to look for information loss.
19. Push your wiki changes and audit everything on the live page, especially checking for broken links.
20. Send the announcement