CVS access policy, branching/tagging, code review, etc.
Tue, 02 Mar 2004 10:29:22 -0800
Content-Type: text/plain; charset=us-ascii
Around 14 o'clock on Mar 2, Egbert Eich wrote:
> For releases there should be a release branch. This should be off
> limit for everyone except the people who are involved in the release
Hmm. I'd rather see the release done on HEAD; otherwise, there's work to
be done to make HEAD current after the release, which seems error prone.
That presumes that most commits during a release process will be focused
on the release, which seems sensible for me, but may not be right for
Perhaps a 'shared' branch could be formed for people who want to ignore
the release and just keep working?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.3.1 11/28/2001
-----END PGP SIGNATURE-----