ReleaseProcedure

• UPCXX nightly test results

1. Update UPCXX_VERSION version number in src/upcxx.hpp
   1. should be of the form: YYYYMMPP
   2. Y and M represent numeric year and month of the release
   3. PP = patch number, starting at 0 for a "normal" (ie not hotfix) release
2. Update ChangeLog + version info in README
3. Update nobs default URL to point at EX release tarball
4. 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
5. 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
6. 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
7. Email local group to review the release-candidate
8. Ask an ADMIN to grant you WRITE access to the 'master' branch
9. 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
10. Ask an ADMIN to revoke WRITE access to the 'master' branch
11. 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
12. 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
13. Advance patch version number on develop branch in src/upcxx.hpp
14. Change nobs URL back to collaborator-snapshot on develop
15. Review and revise the release announcement
16. Navigate to the wiki and git clone it to your local system
17. Add any new publications (eg updated spec or guide) to wiki/Publications.md and wiki/pubs/*.pdf
18. Update all 3 issue trackers: add this release to Versions, next one to Milestones and as default Milestone
19. Update Download section of wiki/Home.md with info on the new release download including links
20. Update wiki/{README.md,INSTALL.md,docs/*} with files from the release, overwriting the version there. Be sure to audit these changes before committing to look for information loss.
21. Audit {README,INSTALL}.md for links within the source tree (which will be broken on wiki) and de-link them
    1. Currently known:
    2. INSTALL.md: example/prog-guide/Makefile
    3. Update this list after each audit
22. Push your wiki changes and audit everything on the live page, especially checking for broken links.
23. Send the announcement