|
Procedure Name |
Steps |
|
Submit Code |
1. Make sure it compiles cleanly |
|
2. Check in via SourceForge.net CVS |
|
|
Submit artifacts or revisions for website |
1. Email to configuration manager in PDF or HTML format |
All changes to the website will be made by the configuration manager. All new documentation and revisions should be emailed to the configuration manager. They will be converted to PDF or HTML and uploaded to the website. In the configuration managers absense, the project lead may upload files.
When a new version of a document is completed, the old version will be tagged with it's creation date and moved to the archive folder. The naming convention will be: <document name>YYYY-MM-DD.<extension> to allow for easy sorting by revision dates.
Meeting minutes and agendas shall be tagged with the meeting date,
such as: MinutesYYYY-MM-DD.pdf
All documents will use upper CamelCase naming, such as: UseCaseModel.doc
|
Directory |
Description |
|
/ |
Root directory containing index.html |
|
/docs |
Documents/Artifacts, such as Requirements Specification |
|
/meetings |
Contains meeting minutes and agendas |
|
/presentations |
Contains presentation slides |
|
/archive |
Contains all old versions of documents |
|
Artifact |
Media |
Location |
Date |
Time |
Who |
|
# |
Who |
Due |
What |
|
1 |
Steven Montgomery |
11/7/2004 |
Add procedures as needed |
|
Date |
Who |
Revision
== |
| 10/01/04 |
Steven Montgomery |
Creation |
| 10/23/04 |
Matt Weinstock |
Peer review and revision, minor corrections |
Last updated: Fri, 01 Oct 2004 23:57:39 GMT