User Tools

Site Tools


difx:release

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
difx:release [2017/10/19 00:45]
adamdeller
difx:release [2017/10/19 00:46] (current)
adamdeller
Line 1: Line 1:
  
-=== The DiFX Release Process ===+==== The DiFX Release Process ​====
  
 The guidelines here are not strict and may change version to version, but document the typical process used in releasing a new DiFX version. The guidelines here are not strict and may change version to version, but document the typical process used in releasing a new DiFX version.
  
-== General principles ==+=== General principles ​===
  
   * We aim for a major release every ~12 months   * We aim for a major release every ~12 months
   * In between major releases, minor releases are made on an as-needed basis. ​ Minor releases should really only be for bugfixes or very minor feature additions.   * In between major releases, minor releases are made on an as-needed basis. ​ Minor releases should really only be for bugfixes or very minor feature additions.
  
-== How to do a minor release ==+=== How to do a minor release ​===
  
   * Test your change in trunk   * Test your change in trunk
Line 21: Line 21:
     * email difx-users and announce the new release     * email difx-users and announce the new release
  
-== How to do a major release+=== How to do a major release ​===
  
   - Upon nearing feature completeness or some other indicator that a release is due, somebody should email the DiFX Developers email list, encouraging a quick wrap-up of current developments for the upcoming release.   - Upon nearing feature completeness or some other indicator that a release is due, somebody should email the DiFX Developers email list, encouraging a quick wrap-up of current developments for the upcoming release.
Line 36: Line 36:
     - Go back to the trunk version of each package and bump the version (usually in configure.ac) and note this in the ChangeLog.     - Go back to the trunk version of each package and bump the version (usually in configure.ac) and note this in the ChangeLog.
     - Recommit the trunk version.     - Recommit the trunk version.
-  - Announce to the DiFX Users mailing list that the new version is ready, including a copy of release ​notes. +  - Run through ​the minor release ​procedure to create DiFX-2.X.1/ from your new DiFX-2.X/ tag.
-  ​Edit the [[news]] page of the wiki with the release date+
  
 A script, current for DiFX-2.4, is below. ​ For future versions change ''​NEW_VERSION''​ and check for package completeness. A script, current for DiFX-2.4, is below. ​ For future versions change ''​NEW_VERSION''​ and check for package completeness.
difx/release.txt · Last modified: 2017/10/19 00:46 by adamdeller