Hi,
This is the correct method to do this. Please implement this
for 0.0.18. Consider:
The developers make changes, and upload to CVS for 0.0.18 as
usual. When a release is indicated (the master programmer, namely
Culus, gives the high sign), then the release co-ordinate (Che_Fox,
at the moment) add in the changelog:
______________________________________________________________________
apt (0.0.18) experimental; urgency=low
* foo changed in bar.cc
* baz changes undone.
______________________________________________________________________
Nothing is released yet. Now come the two releases.
The release cordinator add the changelog
______________________________________________________________________
apt (0.0.18.0bo) experimental; urgency=low
* Release for bo
apt (0.0.18) experimental; urgency=low
* foo changed in bar.cc
* baz changes undone.
______________________________________________________________________
And release;
______________________________________________________________________
apt (0.0.18.1) experimental; urgency=low
* Release for Hamm
apt (0.0.18.0bo) experimental; urgency=low
* Release for bo
apt (0.0.18) experimental; urgency=low
* foo changed in bar.cc
* baz changes undone.
______________________________________________________________________
And release. The release numbers are your freinds.
Manoj
--
Economy is of itself a great revenue. -- Cicero
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
