CVM Release Process - Revision history

Patrices at 17:08, 2 September 2011

2011-09-02T17:08:29Z

Patrices at 17:06, 2 September 2011

2011-09-02T17:06:05Z

Maechlin at 19:27, 1 September 2011

2011-09-01T19:27:51Z

Patrices at 19:38, 28 February 2011

2011-02-28T19:38:53Z

Patrices at 20:43, 25 February 2011

2011-02-25T20:43:30Z

Maechlin: moved CVM-T Release Process to CVM Release Process: Include other CVM's in process

2010-12-10T16:15:38Z

moved CVM-T Release Process to CVM Release Process: Include other CVM's in process

Patrices at 17:58, 3 November 2010

2010-11-03T17:58:46Z

Patrices at 18:57, 29 October 2010

2010-10-29T18:57:20Z

Patrices at 18:54, 29 October 2010

2010-10-29T18:54:40Z

Patrices at 18:40, 29 October 2010

2010-10-29T18:40:23Z

@@ Line 51: / Line 51: @@
 === Package Products ===
-The following packages will be posted for download at (TBD):
+The following packages will be posted for download at hypocenter:
 *cvm<name>-YY.MM.RR.tar.gz: Installation package containing CVM model and query software
@@ Line 127: / Line 127: @@
 == End User License ==
-TBD, end user license agreement to be inserted into LICENSE.TXT in root directory of cvmtest, cvm2mesh, and, viz-cvm. Will cvmh use its existing Harvard license?
+TBD. End user license agreement to be inserted into LICENSE.TXT in root directory of software distribution.

@@ Line 5: / Line 5: @@
 === Target Dates ===
-New versions of CVM-T will be issued on a quarterly basis, beginning Dec 1, 2010 (10.12.0). This is a nominal schedule in that there will be no new releases if no changes have been made, and releases may be delayed to fix problems or perform additional testing.
+New versions of a CVM will be issued on a quarterly basis, beginning Dec 1, 2010 (10.12.0). This is a nominal schedule in that there will be no new releases if no changes have been made, and releases may be delayed to fix problems or perform additional testing.
 === Testing ===
-The CVM-H release candidate will be submitted to the Automated Test Framework where it will be evaluated in a number of unit and acceptance tests. The primary acceptance test involves a goodness of fit (GoF) evaluation for the 2008 Chino Hills earthquake. The release candidate passes the testing when the following criteria are met:
+The CVM release candidate will be submitted to the Automated Test Framework where it will be evaluated in a number of unit and acceptance tests. At this point the software will be feature complete; no additional features or enhancements are expected to be developed. The software distribution will be assigned a release tag of format YY.MM.RR_RC, where:
-* CVM-H and cvm2mesh are successfully built
+* YY.MM.RR: Prospective release identifier according to above format
-* All CVM-H unit tests pass
+* RC : Release candidate flag
 * cvm2mesh is successfully able to extract a Chino Hills 100m mesh
 * The SCEC Broadband GoF bias for all periods in the range 1s-10s is less than or equal to the GoF bias computed in the previous release. In other words, the goodness of fit of Chino Hills synthetics versus observed is expected to improve from release to release.
 If tests fail or problems are found, they will be corrected and the tests re-run until all tests pass.
 === Scientific/Technical Review ===
-Scientific review of ATF simulation results and horizontal/profile plots for correctness, along with technical review of code and software usage. A period of one week following a code freeze is allocated to this review activity. The review team makes a recommendation of either to proceed with the release, or hold in order to perform more tests or changes.
+Scientific review of ATF simulation results and horizontal/profile plots for correctness, along with technical review of code and software usage. A period of one week following a code freeze is allocated to this review activity. The review team makes a recommendation of either to proceed with the release, or hold in order to perform more tests or changes. At the end of the review, a full code freeze is enacted for any additional changes (other than release ID assignment).
@@ Line 36: / Line 38: @@
 === Assign Release Tag ===
-where:
+An official release tag is assigned to the release candidate. Official release tags will have the format YY.MM.RR, where:
 * YY: Two digit year
@@ Line 45: / Line 46: @@
-Release candidate tags will have the format: YY.MM.RR_RC#.
+The appropriate file(s) in version control are updated with this tag. The software is then recompiled and re-tested with unit tests to ensure that the tag update was successful.
@@ Line 57: / Line 53: @@
 The following packages will be posted for download at (TBD):
-*cvm-t-system-YY.MM.RR.tgz: Comprehensive package containing CVM-H, cvmtest, cvm2mesh, and viz-cvm.
+*cvm<name>-YY.MM.RR.tar.gz: Installation package containing CVM model and query software
-*cvm-t-cvm-YY.MM.RR.tgz: Package containing CVM-H
+*cvm<name>-YY.MM.RR.tar.gz.md5: md5 checksum

@@ Line 104: / Line 104: @@
 | Kim Olsen
 | UCSD
 |-
 | Scott Callaghan

@@ Line 36: / Line 36: @@
 === Assign Release Tag ===
-A release tag is assigned to the release candidates and official releases. Official release tags will have the format: rel_YY.MM.RR.
+A release tag is assigned to the release candidates and official releases. Official release tags will have the format: YY.MM.RR.
 where:
@@ Line 45: / Line 45: @@
-Release candidate tags will have the format: rc_YY.MM.RR_RC#.
+Release candidate tags will have the format: YY.MM.RR_RC#.
 where:
 * YY.MM.RR: Prospective release identifier according to above format
-* # : Release candidate id, starting at 0
+* RC# : Release candidate id, starting at 0

@@ Line 36: / Line 36: @@
 === Assign Release Tag ===
-A release tag is assigned to the release candidate. Release tags will have the format: YY.MM.RR
+A release tag is assigned to the release candidates and official releases. Official release tags will have the format: rel_YY.MM.RR.
 where:
@@ Line 42: / Line 42: @@
 * YY: Two digit year
 * MM: Two digit month
-* RR: Mid-month revision id, starting at 0.
+* RR: Mid-month revision id, starting at 0

← Older revision	Revision as of 16:15, 10 December 2010
(No difference)

← Older revision		Revision as of 17:58, 3 November 2010
Line 56:		Line 56:

	=== User Community Notification ===		=== User Community Notification ===
−	Communication with the user community is accomplished with an email list (~~cvm~~-t@usc.edu) with public subscription. Once the product packages have been publicly posted, a notification is sent to this email lists with release notes and information where to get the new version.	+	Communication with the user community is accomplished with an email list (CVM-T-ANNOUNCE@usc.edu) with public subscription. Once the product packages have been publicly posted, a notification is sent to this email lists with release notes and information where to get the new version.

← Older revision		Revision as of 18:54, 29 October 2010
Line 27:		Line 27:
	=== Scientific/Technical Review ===		=== Scientific/Technical Review ===

−	Scientific review of ~~AWT~~ simulation results and horizontal/profile plots for correctness, along with technical review of code and software usage. A period of one week following a code freeze is allocated to this review activity. The review team makes a recommendation of either to proceed with the release, or hold in order to perform more tests or changes.	+	Scientific review of ATF simulation results and horizontal/profile plots for correctness, along with technical review of code and software usage. A period of one week following a code freeze is allocated to this review activity. The review team makes a recommendation of either to proceed with the release, or hold in order to perform more tests or changes.

@@ Line 5: / Line 5: @@
 === Target Dates ===
-New versions of CVM-T will be issued on a quarterly basis, beginning Dec 1, 2010 (10.12.1). This is a nominal schedule in that there will be no new releases if no changes have been made, and releases may be delayed to fix problems or perform additional testing.
+New versions of CVM-T will be issued on a quarterly basis, beginning Dec 1, 2010 (10.12.0). This is a nominal schedule in that there will be no new releases if no changes have been made, and releases may be delayed to fix problems or perform additional testing.
@@ Line 15: / Line 15: @@
 * All CVM-H unit tests pass
 * cvm2mesh is successfully able to extract a Chino Hills 100m mesh
-* The SCEC Broadband GoF bias for all periods in the range 1s-10s is less than or equal to the GoF bias computed in the previous release. In other words, the goodness of fit of Chino Hills synthetics versus observed must improve from release to release.
+* The SCEC Broadband GoF bias for all periods in the range 1s-10s is less than or equal to the GoF bias computed in the previous release. In other words, the goodness of fit of Chino Hills synthetics versus observed is expected to improve from release to release.
 If tests fail or problems are found, they will be corrected and the tests re-run until all tests pass.
@@ Line 25: / Line 25: @@
-=== Scientific Review ===
+=== Scientific/Technical Review ===
-Scientific review of AWT simulation results and horizontal/profile plots for correctness. A period of one week following a code freeze is allocated to this review activity. The review team makes a recommendation of either to proceed with the release, or hold in order to perform more tests or changes.
+Scientific review of AWT simulation results and horizontal/profile plots for correctness, along with technical review of code and software usage. A period of one week following a code freeze is allocated to this review activity. The review team makes a recommendation of either to proceed with the release, or hold in order to perform more tests or changes.
 === Release Authority ===
-The release authority examines the test results and the recommendation of the scientific reviewers and makes the decision whether or not to proceed with the new release. A one week period is allocated for this activity.
+The release authority examines the test results and the recommendation of the scientific and technical reviewers and makes the decision whether or not to proceed with the new release. A one week period is allocated for this activity.
@@ Line 42: / Line 42: @@
 * YY: Two digit year
 * MM: Two digit month
-* RR: Mid-month revision id, starting at 1.
+* RR: Mid-month revision id, starting at 0.
@@ Line 78: / Line 78: @@
-== Scientific Review Team ==
+== Scientific/Technical Review Team ==
 {| class="wikitable" | border="1"
@@ Line 96: / Line 96: @@
 | Kim Olsen
 | UCSD
 |}