Changes between Version 4 and Version 5 of DevNotes/Processeses/DeploymentProcess
- Timestamp:
- Oct 18, 2015 9:21:42 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevNotes/Processeses/DeploymentProcess
v4 v5 4 4 == Reminders == 5 5 - The SasView builds can be found here: [https://jenkins.esss.dk/sasview/view/Master-Builds/]. Note we are not releasing Unix versions at this time despite the Ubuntu build machine. 6 - The released software is available for download on [https://github.com/SasView/sasview/releases !GitHub].6 - The released software is available for download on [https://github.com/SasView/sasview/releases GitHub]. 7 7 8 8 == Planning a new major release == … … 20 20 == Preparing a new major release == 21 21 - The release manager will make sure that the version number is correctly placed in all the correct places. That currently includes: 22 -- sasview/__init__.py23 -- sasview/README.txt24 -- docs/sphynx-docs/source/conf.py (change both version and release numbers)25 -- sasview.latestversion has now been superseded by the json file stored at the sasview site.22 -- sasview/__init__.py 23 -- sasview/README.txt 24 -- docs/sphynx-docs/source/conf.py (change both version and release numbers) 25 -- sasview.latestversion has now been superseded by the json file stored at the sasview site. 26 26 - The release manager will download the mac and windows builds from the build site. 27 27 - 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 .