Version 26 (modified by butler, 5 years ago) (diff)

Release Process

The following outlines the SasView release process.


Planning a new major release

  • Releases are discussed at the bi-weekly meeting. As a release date approaches the team agrees on what changes/pull requests will be included and which will not.
  • Only approved changes should be merged into master from this point till the release. All other changes should remain in their branches till after the release.
  • Completed approved changes should be reviewed and then merged to master. NOTE: don't forget to close the relevant tickets upon merging either with the closes #ticketno key phrase in the merge notes or manually.
  • Once all approved changes have been merged into master (or is clearly imminent), the release should be discussed at the following conference call.
  • During that call, a "release manager" will be appointed for that release. That person is responsible for following the release process below and communicating progress to the team. The release manager will need to have release privileges on the repository and on Jenkins.

Testing a new major release

Besides the ongoing testing with every pull request, extra care in testing should be taken for a major release. A first step should be for the developers (and any identified "friendly users" to install the master build from Jenkins and thoroughly test. It is recommended that an actual beta pre-release be published on github to broaden the nunber of testers.

All bugs and issues identified during this testing phase will be ticketed and either fixed or discussed on the conference call to ascertain if they must be fixed (blockers) or can remain known issues to be reported in release notes and fixed in a future release.

Once everyone agrees that the master build is ready, the release manager will start the final release process.

Penultimate release steps performed by the release manager

sasview update

  • Create a proposed_release_x_y_z branch
  • Update the /sasview/docs/sphinx-docs/source/user/RELEASE.rst with the latest version of the release notes
  • Obtain the Zenodo DOI
  • Update src/sas/sasview/ with
    • The Zenodo link
    • The new version number
    • The year of the release (used in various copyright notices)
  • Currently we also need to manually update the current year string in two places:
    • /installers/license.txt
  • When branch changes (mainly release notes) are approved merge the proposed release branch into master - then delete the branch.
  • 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 pre-release from github following instructions published on GitHub 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

We should only be using tagged version of sasmodels in a SasView release unless there is a compelling reason to release from the current sasmodels HEAD. Assuming this release is against a NEW version of sasmodels

  • Make sure to update to the correct version number
  • Tag HEAD, or the appropriate commit with the release number. To do so one can either:

Create the Jenkins release builds

  • Log into the Jenkins server, navigate to the releases tab and for each platform use "configure" to edit the configuration to use the appropriate sasmodels and SasView tags for the build.
  • Next, manually launch the Jenkins build processes for each platform being supported.

Final update of the github release page

  • Once the build process is complete, download the mac and windows builds from the Jenkins release build tab and upload the binaries to the releases page. Note that the mac and windows builds will need to be renamed appropriately. Current naming convention is:
    • Windows: setupSasView-V.v.v.exe
    • mac: SasView-V.v.v-MacOSX.dmg
  • The portion of the release notes in the RELEASE.rst for this new release version should be entered in the Release Description section (i.e do not copy the full release notes which includes notes for ALL previous versions as well). Also a copy of the Acknowledgment and citation and Bug Reporting sections should be included at the end of the Release Description section.

update posted documentation

Currently we maintain both an html and a PDF copy of the documentation available on the SasView website. Make sure to follow BOTH steps below.

  • The documentation folder contents (html version) needs to be moved to the repo under /docs.
    • The first step it to git create a new folder (docs_x.y.z) under docs/old_docs where x.y.z is the version number being superseded (i.e. the version of the docs currently in the repo).
    • Git move all the folders and files currently under docs to docs/old_docs/docs_x.y.z
    • Git copy the new html docs (all folders and files) to docs
      • NOTE: While the docs could be built locally, for consistency with the release docs it is strongly recommended that the release version be installed locally and the cocs copied from the install path. These can just be git copied into the repo folder.
    • Commit and push these changes
  • The documentation is also built as a PDF and the PDF link for the website also needs to be updated to the new PDF version.
    • Again, the first step is to git move the SasViewDocumentation.pdf to downloads/Old_SasViewDoucmentation/
    • The new PDF is available on the Jenkins Master Build tab of the OSX and Ubuntu builds only. NOTE: they are not currently available in any of the release builds which means they should be downloaded from Mater build immediately after last commits before tagging a release. This should be changed to add a PDF build on the release servers at some point.
    • PDF should be downloaded as SasViewDocumentation.pdf.
    • The pdf should then be git copied or git moved to the folder.
    • Commit and push changes

Final release steps

  • 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.
    • Update the github release page and remove the pre-release tag

Uploading sasmodels to pypi

sasmodels are also avaialble from pypi (sascalc should be avaialable in the future). In order to do this, one needs to checkout tagged version and then build dist in sasmodels folder: python sdist bdist_wheel Once this is done one can upload sasmodels to pypi using twine: twine upload dist/*.

Post release steps

Once the release is completely done and out, it is recommended that the version numbers in src/sas/sasview/ of master get updated to the next planned release version number so that developers testing can easily tell they are running a post release version.

Patch releases

Currently patch releases follow the same process as major releases but the cycle is usually much abbreviated.

Pre releases (alpha and beta releases)

Pre-releases follow a much less formal acceptance process but otherwise follows the same technical process - make sure to click "This is a pre-release" check box when drafting a new release on GitHub.