Changes between Version 25 and Version 26 of DevNotes/Processeses/DeploymentProcess

Timestamp:

Feb 10, 2019 1:58:20 PM (5 years ago)

Author:

butler

Comment:

—

DevNotes/Processeses/DeploymentProcess

@@ -33 +33 @@
  * Tag HEAD or the appropriate !SasView commit point for the release. This can be done either by:
      * Use git to tag HEAD or a commit `$ git tag -a vx.y.z -m "SasView version x.y.z"`or
-     * create a release from github following instructions published on !GitHub [https://help.github.com/articles/creating-releases/]. NOTE: creating a `Draft release` will **NOT** create a tag
-       * Note: if decision is made to make a release from an old enough commit point that it is not available on the !GitHub interface the tag can be generated using the local git interface
+     * create a pre-release from github following instructions published on !GitHub [https://help.github.com/articles/creating-releases/]. NOTE: creating a `Draft release` will **NOT** create a tag
+       * '''NOTE''' 1: It is impotant at this point to label as pre-release so that the link from the webpage continues to send people to the old version as there is no executable yet for them to download from here.
+       * '''NOTE''' 2: if decision is made to make a release from an old enough commit point that it is not available on the !GitHub interface the tag can be generated using the local git interface
 '''NOTE:''' sasview.latestversion has now been superseded by the json file stored at the sasview site.
 === sasmodels update ===
@@ -68 +69 @@
  * The release manager will email the team to announce the release process is complete.
  * The team should download the new release to make sure it installs. Because the release build servers are different than the developer build servers, build server fixes and dependency updates may not have been propagated over to the release server so some rudimentary testing should be done to double check that all is well.
- * Once final approval is given, the release number should be updated in latestversion.json on the !SasView website repo which will alert all !SasView users that a new version is available.
+ * Once final approval is given
+   * The release number should be updated in latestversion.json on the !SasView website repo which will alert all !SasView users that a new version is available.
+   * Update the github release page and remove the pre-release tag