Staging is dead; long lives the trunk!

The repository has been reorganized.

I am in the process of changing the access permissions.  Access will
work as follows:

All will now have access to create and modify branches in
$SVN/[project]/branches which will serve as a shared area for
multi-developer work.

Trunk access will be granted to senior developers (as was the case for
staging before.

The goal is to permanently keep the trunk in stable (and releasable)
state.  As errors/mistakes do happen, broken trunks will be moved into
the branch directory ($SVN/[project]/branches/broken-trunk-2005-03-15)
and the trunk will be reverted to the last known stable state.  This
will allow anybody to help work on fixing broken trunks, while allowing
continuing development on the stable code base (reverted trunk).

Tags creation, in the $SVN/[project]/tags section will remain restricted
to lead developers.

Of course, primary development is kept in private sandboxes, and every
developer can continue creating private tags in
$SVN/developers/[name]/tags .

I hope this model will simplify shared work, when needed, in the
branches area.  I do think that this repository layout reflects more
accurately the development model that we have actually followed in the
last year and a half.  The staging/bugfree/trunk layers were a failed
experiment; they did not work out as expected.  On the other hand, the
sandbox model has proved to be very effective at allowing parallel,
undisturbing work.

So, from now on, if you have been tracking staging, you should start
tracking the trunk.  "svn co" of staging will fail.  I do ask for the
collaboration of all to help updating the wiki pages documentation
appropriately.  http://sablevm.org/wiki

Have fun, and thanks in advance for your help with the wiki pages!

Etienne

--
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

_______________________________________________
SableVM-devel mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCNxLHjyrJi4rH84gRAqRYAJ9IgKt7GoNwTfFyugmYvX2q8tofogCeKwHV
iWLbEXVXzUS745PhUmsO/M8=
=ZPBK
-----END PGP SIGNATURE-----