difx:release
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
difx:release [2017/10/19 00:45] adamdeller |
difx:release [2020/09/14 23:36] geoffcrew |
||
|---|---|---|---|
| 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. | * In between major releases, minor releases are made on an as-needed basis. | ||
| - | == How to do a minor release == | + | === How to do a minor release |
| * Test your change in trunk | * Test your change in trunk | ||
| * Test your change in master-tags/ | * Test your change in master-tags/ | ||
| * Update the ChangeLog(s) and update package version requirements if needed | * Update the ChangeLog(s) and update package version requirements if needed | ||
| - | * Email difx-developers and announce the intention to make a new minor release, and request | + | |
| + | | ||
| + | * Request | ||
| + | * Indicate timeline and community requirements (with respect to schedule) | ||
| * After testing is complete: | * After testing is complete: | ||
| * svn copy master-tags/ | * svn copy master-tags/ | ||
| + | * update the setup.bash and setup.csh with the new DIFX_VERSION identifier | ||
| * Compile test the new tag | * Compile test the new tag | ||
| * Update [[news]] and [[installation]] with the new version number | * Update [[news]] and [[installation]] with the new version number | ||
| + | * Update [[difx2.0tonow]] with major changes | ||
| * email difx-users and announce the new release | * email difx-users and announce the new release | ||
| + | * update the versions section of the userguide (// | ||
| - | == 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 42: | ||
| - 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 | + | - Run through |
| - | | + | |
| A script, current for DiFX-2.4, is below. | A script, current for DiFX-2.4, is below. | ||
difx/release.txt · Last modified: 2021/09/15 17:26 by janwagner
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
