This could get complex.
I suggest we don't let it.
The CVS manual always insists that communication is the key
to the whole thing which is why I created the coders alias.
Suggested Rules and Procedures:
Rule 1 - Game only runs on tagged code.
Fix required to @version so that it shows the tag
Rule 2 - netmud.running sym link to netmud-release_00x
Keep previous netmud binary (minimum).
Procedure for coding:
We could either do it with tagged branches so that we
can fix branches while coders work on the head. Ick
for the moment I think. Suggest that tested fixes
and extensions are added to the head.
You have a bug/feature that needs fixing/adding.
1. Email the coders list with what you are going to do.
2. Get the latest code out.
3. Make your changes. Test changes locally or on
one of the Ugly servers. Do not check code in
to the CVS while you are developing. Take
local daily copies if you need backups.
If anyone else runs the whole cycle while you
are developing then you need to cvs update,
check your code and test it with their fixes
in as well before you move on.
4. Once you are ready for your change to go live
(or just be added to the repository) then email
the coder alias to indicate that you will be updating.
At this stage the code should compile, run and
have been tested.
5. If this is to be a code release then add that information
to the tag_list file (in the repository). If it
is not then just add the broad changes to the tag
list, ready for next version.
6. Check in your code (you may need to update first).
7. If a release tag head code with release number.
8. Email the coder alias that you have finished and
with details of your changes.
9. If a release then use the uglymug account to
checkout the code. Build on game machine. Move
binary to run directory using netmud-release_00x
and remake sym link. If urgent restart the game
with new binary. Alter motd.txt
4-8 should really be an 'atomic' operation on the CVS.
Until someone has said that they have completed
their submission then no-one else should be playing
with the CVS.
Things not to do:
- Don't check in code while you are developing. This
would prevent someone making an urgent fix before
you are ready.
- Don't not have backups of your code since it
is not in CVS until it is complete.
--
----------------------------------------------------------------------
re...@re... www.reaperman.org +44 7976 696 407
----------------------------------------------------------------------
|
