Changes between Version 9 and Version 10 of DevNotes/Processeses/DeploymentProcess

Timestamp:

Oct 31, 2015 7:56:48 PM (9 years ago)

Author:

butler

Comment:

—

DevNotes/Processeses/DeploymentProcess

@@ -25 +25 @@
  - docs/sphynx-docs/source/conf.py (change both version and release numbers)
  - sasview.latestversion has now been superseded by the json file stored at the sasview site.
-- The release manager will then announce to the team the beginning of the release process. Developers should not push anything to the GitHub repository untill the release 
+- The release manager will then announce to the team the beginning of the release process. Developers should not push anything to the !GitHub repository until the release 
 - The release manager will download the mac and windows builds from the build site.
-- The release manager will then tag the current repo for release and execute the release process as described at [https://help.github.com/articles/creating-releases/]. Note that the mac and windows builds will need to be renamed appropriately and uploaded as binaries along with the .
+- The release manager will then tag the current repo for release and execute the release process as described at [https://help.github.com/articles/creating-releases/]. Note that the mac and windows builds will need to be renamed appropriately and uploaded as binaries along. Current naming convention is:
+ - Windows: !SasView-V.v.v.exe
+ - mac: !SasView-V.v.v.dmg
+- The documentation folder contents needs to be moved to the sasview.github.io repo under docs (commit and push). Currently the release manager can either build the docs locally, but for consistency with the release docs it is strongly recommended that instead they install the release version and copy the docs from the install path. 
 - An abbreviated version of the  release notes in the README.txt should be entered in the Release Description section.
 - The release manager will email the team to announce the release process is complete.