Mercurial > hg-old > index.cgi

comparison README.MAINT @ 107:69ead2e61763

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Added start of a manual and updated maintainer docs to mention generated documentation
author lost
date Wed, 28 Jan 2009 05:02:44 +0000
parents a8a83ccffafd
children
comparison
equal deleted inserted replaced
106:f643e2ff0008 107:69ead2e61763
3 Before a release is made, a branch for that release must be made. Within 3 Before a release is made, a branch for that release must be made. Within
4 that branch, all files that will be distributed with the particular release 4 that branch, all files that will be distributed with the particular release
5 must be generated and added to the repository on that branch. Once the 5 must be generated and added to the repository on that branch. Once the
6 release is deemed stable and ready for release, the release tag should 6 release is deemed stable and ready for release, the release tag should
7 be generated from the head of that particular branch. Thus all release 7 be generated from the head of that particular branch. Thus all release
8 series will have the autotool generated files in the repository. 8 series will have the autotool generated files in the repository as well
9 as any other generated files intended to be distributed.
9 10
10 Any branch not directly intended to be a release need not include the 11 Any branch not directly intended to be a release need not include the
11 autotool generated files. 12 generated files.
12 13
13 The trunk development stream must not include the autotool generated files 14 The trunk development stream must not include the autotool generated files
14 as these are likely to change rapidly and it can cause a great deal of 15 as these are likely to change rapidly and it can cause a great deal of
15 confusion for little gain. 16 confusion for little gain. Also, the main trunk need not contain such
17 things as generated documentation files for the same reason.
16 18
17 By including the generated files in the release branches, it is possible 19 By including the generated files in the release branches, it is possible
18 to replicate any problems users of the package may have, including if it 20 to replicate any problems users of the package may have, including if it
19 is due to problems with the autotools themselves. 21 is due to problems with the autotools themselves.
20 22