PSRCHIVE Administration Guide

Releasing a Distribution

Upload the distribution file to the SourceForge File Release System (FRS) by running the script 
Management/release.csh

Update the development trunk to reflect that it is post release. In the top-level directory 

git checkout master
then edit configure.in; e.g. 
AC_INIT([PSRCHIVE],[2020-01-10+],[psrchive-developers@lists.sourceforge.net])

Update the following files: 

web/download.shtml
web/changes/index.shtml
web/changes/release-<yyyy-mm>.shtml
Documentation/psrchive.dox
where "<yyyy-mm>" is the version series number. When creating the release notes, it is useful to update the Bugs and Feature Requests Trackers as follows:
  • Visit Update artifact groups for: Feature Requests and scroll down to "Add a new artifact group" with the Group name "release <yyyy-mm>"
  • Visit Tracker: Feature Requests filtered on "Status: Closed" and "Group: next release" then "Check All" and do a "Mass Update" to set "Group: release <yyyy-mm>". (It might also be a good idea to check for any stragglers in "Group: No Group".)
  • Change the filter to "Group: release <yyyy-mm>" then click "Filter" then "Permalink" and cut-and-paste the URL into the release notes.
  • Visit Update artifact groups for: Bugs and scroll down to "Add a new artifact group" with the Group name "release <yyyy-mm>"
  • Visit Tracker: Bugs filtered on "Status: Closed" and "Group: next release" then "Check All" and do a "Mass Update" to set "Group: release <yyyy-mm>". (Again, double-check "Group: No Group".)
  • Change the filter to "Group: release <yyyy-mm>" then click "Filter" then "Permalink" and cut-and-paste the URL into the release notes.

Finally, update the web pages.