CVM Release Process

From SCECpedia
Revision as of 19:24, 26 October 2010 by Patrices (talk | contribs)
Jump to navigationJump to search

Finalizing the Release

Testing

Code Freeze

Review

Release Authority

Assign Release Tag

Release tags will have the format: YY.MM.RR

where:

  • YY: Two digit year
  • MM: Two digit month
  • RR: Mid-month revision id, starting at 1.


Package Products

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-t-cvm-YY.MM.RR.tgz: Package containing CVM-H
  • cvm-t-awt-YY.MM.RR.tgz: Package containing cvmtest
  • cvm-t-evt-YY.MM.RR.tgz: Package containing cvm2mesh, viz-cvm


User Community Notification

Communication with the user community is accomplished with an email list (cvm-t@usc.edu) with public subscription.


Software Defects

Community Reported Defects

Open Trac ticket.


Defects in a Release Candidate

Open Trac ticket. Possibly delay release if a critical defect.


Defects in an Existing Release

A notification is posted to the email subscription list announcing that a defect has been found and assigned a Trac ticket number. When a new release is prepared that addresses the ticket, a notification is sent to the email list.