> From: Adrian St. John=20
>=20
Forgot a bit. I'm quoting the entire lot again so that we've got
a single email with the entire release procedure.
> In your development CVS directory (whichever machine you're working
> on, its all the same...):
>=20
> Before committing any code:
>=20
> 1. cvs update (make sure you've got the latest changes)
> 1a. If no changes then go to step 2.
> 1b. Go through the build & testing phase again, to make sure nothing
> breaks.
>=20
> 2. Update 'tag_list' with a summary of what you've done.
> If you're making a formal release, put the release information
> in as well.
>=20
> 3. cvs commit
>=20
> 4. cvs tag um1_XXX
>=20
> To build a release for uglymug:
>=20
> 5. ssh something.uglymug.org.uk
> 6. su uglymug
> 7. cd ~uglymug/ugly/CVS/UglyCODE
> 8. cvs update -r um1_XXX
> 9. make clean (the dependancies aren't correct yet!)
> 10. make
> 11. mv netmud ../../netmud_XXX
> 12. cd ../..
> 13. rm netmud
> 14. ln -s netmud_XXX netmud
15. Email ug...@ug... with the following:
a. Reason for release (important bug fix, I felt like it, etc.)
b. The details from tag_list
16. (If someone can explain exactly how to do it)
Make an official SourceForge release.
Adrian.
|
