1HOWTO Tag Software
2==================
3
4Releases of the POSIX Test Suite will happen at defined (TBD) intervals.
5In order to get code included in the releases, the tagging scheme below
6has been created.
7
8Developer Tagging
9=================
10When the code a developer is working on is ready for a release, the developer
11should tag it with the tag:
12	posixtestsuite__source
13
14This code will then be pulled to make the official release.
15
16Note:  Before code should be considered to be ready for release, it should
17follow all HOWTOs currently created.
18
19Release Coordinator Tagging
20===========================
21The person responsible for gathering and tarring all the files for the
22official release will grab all files with the posixtestsuite__source
23tag and tag them with the tag:
24	Release__M_N_P__posixtestsuite__YYMMDD
25where M.N.P is the version number, and YYMMDD is the current date.
26
27The version numbering scheme is as follows:
28
29M = Major release.  The initial scope of the POSIX Test Suite corresponds
30to M=1.  That includes tests for all initially scoped POSIX areas (signals,
31threads, semaphores, message queues, timers).  M<1 is for releases before
32the first major release.  M>1 will happen when the scope changes.
33
34N = Minor release.  The various minor releases have yet to be determined,
35but will most likely roughly correspond to the milestones defined.
36
37P = Release number.  This is incremented each time a new release is made.
38Restarts at 0 for each new Major/Minor combination.
39
40Contributors:	rolla.n.selbak REMOVE-THIS AT intel DOT com
41		geoffrey.r.gustafson REMOVE-THIS AT intel DOT com
42		julie.n.fleischer REMOVE-THIS AT intel DOT com
43