Version Control Policy
Version History
Version | Date | Status & changes | Expression identifiers |
V1.0 | 2007-10-21 | Release | PILIN/ BH93VNQH hdl:102.100.272/SBH93VNQH |
To cite the latest version of this work use http://resolver.net.au/hdl/102.100.272/KD633VNQH
To cite this version of this work, use http://resolver.net.au/hdl/102.100.272/SBH93VNQH
1 Purpose/Issue
This policy specifies a numbering system necessary to track the changes that occur in a “thing” throughout the “thing’s” development and subsequent revisions during the course of the PILIN project.
2 Background
Version control allows:
One version to be distinguished from any previous and subsequent versions
Identification of the most current version of the “thing”
“Things” can go through various iterations before being approved for release.
3 Scope
This policy is for use by PILIN team members.
This policy applies to “things” as defined in the Identifier Association Policy for the PILIN Project v1.01 1 Identifier Association Policy for the PILIN Project v1.0
4 Policy Statement
In the first instance, “things” will be given a draft version control number. Once a “thing” has been approved for release, it is given a version control number.
Version control numbering will be used with things that cross the PILIN curation boundary.
Once a document goes to version 1.0 and crosses the PILIN curatorial boundary, the draft version history may be deprecated for public viewing.
Draft “things” will start at v0.1 to reflect their draft status. Once a “thing” has been approved for release, the number converts to v1.0
The version control numbering will be used as follows:
First draft | V0.1 |
Second draft | V0.2 |
Subsequent drafts | V0.3….etc |
First release (approved) | v1.0 |
Minor amendment | v1.1 |
Second minor amendment | v1.2 |
Evaluation Review Release | v2.0 |
Minor Amendment | v2.1 |
Second minor amendment | v2.2 |
5 Example
An example of this policy is:
Version Control Policy for the PILIN Project
Version History
Version | Date | Status & changes | Expression identifiers |
V0.1 | 2007-07-05 | Initial release | PILIN/??? hdl:102.100.272/TBA |
V0.2 | 2007-07-06 | Includes Drafts | PILIN/??? hdl:102.100.272/TBA |
6 Definitions
The PILIN curation boundary is defined by who has knowledge about PILIN things. Things inside the PILIN curation boundary are only known to members of the PILIN project team. Things outside the curation boundary are known to both the PILIN team and entities outside the PILIN team2 2 Identifier Association Policy for the PILIN Project v1.0
A minor amendment consists of changes to punctuation or spelling.
A major amendment consists of major content addition or deletion, including changes to heading
7 Appendix
Identifier Association Policy for the PILIN Project v1.0,
hdl:hdl:102.100.272/3SYFCJ3QH
http://resolver.net.au/hdl/102.100.272/3SYFCJ3QH
Copyright © Monash University
This work is licensed under the Creative Commons Attribution-Share Alike 2.5 Australia License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/2.5/au/ |
This work was created as part of the PILIN project. The PILIN project is funded by the Australian Commonwealth Department of Education, Science and Training, (DEST) under the Systemic Infrastructure Initiative (SII) as part of the Commonwealth Government’s Backing Australia’s Ability – An Innovation Action Plan for the Future (BAA) under the ARROW Project.
1 Identifier Association Policy for the PILIN Project v1.0
2 Identifier Association Policy for the PILIN Project v1.0
