Squeak VM CVS guidelines (obsolete)
Last updated at 6:00 pm UTC on 24 October 2006
This is now obsolete. We now use SubVersion instead.
A page on use of SubVersion is needed to replace this information. See Getting source using the SubVersion repository for a start. The remains of this page have been mangled to cut out the obvious junk and leeve in parts that might still be useful.
Please do help out with more details, specific information about the Squeak VM source tree should of course also be added.
First thing
If you are interested in helping out developing the Squeak VM ports you should:
- Read these Swiki pages, especially VMMaker. It really contains essential information to avoid that you make a fool of yourself! :-)
- Join the vm-dev mailinglist . You subscribe to it by sending an email to: vm-dev-subscribe@discuss.squeakfoundation.org
Summary
I have tried to summarize the most important here in a bullet list:
- We have designated Squeak VM port maintainers that are the only ones permitted to commit on the trunk. This is VERY IMPORTANT! If someone else commits on the trunk he/she will be forced to write class comments for all uncommented classes in the image! :-)
- All other developers work on branches.
- We use a vouching scheme to give out commit permission to developers. Note that this still does not give a developer permission to commit on the trunk!.
- We have rules for tags and how we handle branches. Tags tend to become many when using branches and we want them to follow naming rules and some scope rules to avoid confusion.
{Does any of the above still make sense for subversion?}
