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

Timestamp:

Oct 18, 2015 9:48:51 PM (9 years ago)

Author:

butler

Comment:

—

DevNotes/Processeses/DeploymentProcess

@@ -19 +19 @@
 
 == Preparing a new major release ==
-- The release manager will make sure that the version number is correctly placed in all the correct places.  That currently includes:
- - sasview/init.py
+manager announces the process is complete
+- The release manager will make sure that the version number is correctly placed in all the appropriate places.  That currently includes:
+ - sasview/_init_.py
  - sasview/README.txt
  - 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 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 .
 - 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.
+- The release manager will email the team to announce the release process is complete.
 - The team will download the new release to make sure it installs.
+- Once final approval is given, the release number will be updated in latestversion.json on the !SasView website repo which will alert all !SasView users that a new version is available.
 
 == Patch releases ==