Quality Management:Quality manual/Work instructions/Release Note: Difference between revisions

From PMISwiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
!Under development!
The release not below is used in all projects governed by [http://vteam.dk Virtual Team A/S].
 


==Release Note==
==Release Note==
Line 7: Line 6:
* Date of release
* Date of release
* Name of responsible release engineer
* Name of responsible release engineer
* Release category: Describe the target for the release e.g.: Development, Alpha, Beta, Production, Error correction]
* Release category: Describe the target for the release e.g.: Bi-weekly development, Alpha, Beta, Production, Error correction].
* Changes in release: with references to development requirements and/or bug trace references.
* Changes in release: with references to development requirements and/or bug trace references.
* Dependencies: E.g. if special database version is needed or special configuration is needed.
* Dependencies: E.g. if special database version is needed or special configuration is needed.
Line 24: Line 23:
================================================================================
================================================================================
Date: <date>
Date: <date>
Release category: Development [Options: Development, Alpha, Beta, Production, Error correction]
Release category: [Options: Bi-weekly development, Alpha, Beta, Production, Error correction]
Release engineer: <Name>
Release engineer: <Name>
================================================================================
================================================================================

Revision as of 13:44, 13 January 2012

The release not below is used in all projects governed by Virtual Team A/S.

Release Note

All software releases must have a release note. The format below may be used. The release note must at least have the following informations stated:

  • Project name
  • Date of release
  • Name of responsible release engineer
  • Release category: Describe the target for the release e.g.: Bi-weekly development, Alpha, Beta, Production, Error correction].
  • Changes in release: with references to development requirements and/or bug trace references.
  • Dependencies: E.g. if special database version is needed or special configuration is needed.
  • Test requirements: Information about what tests has been executed and what remains
  • Known issues.
  • Target for next release: Reference to development requirements and/or bug trace references.


Excample of release note are shown below:

File: releasenote.txt
QA ref.: http://pmis.biz/wiki/QM:Quality_manual/Work_instructions/Release_Note


                    RELEASE NOTE - <project name> project
================================================================================
Date: <date>
Release category: [Options: Bi-weekly development, Alpha, Beta, Production, Error correction]
Release engineer: <Name>
================================================================================
Changes in this release:
<Reference> <Short description>

================================================================================
Dependencies:


================================================================================
Test requirements:

================================================================================
Known issues:


Target for next release:

================================================================================
END of note.

Document History

Version Date Author Status Purpose of update
1 25 Aug 2011 PSA Draft New document
2 13 Jan 2012 PSA Final Text review and minor corrections