>>>>> "Jeroen" == Jeroen Budts <[EMAIL PROTECTED]> writes:
Jeroen> How do other projects do this?
I haven't done it yet, but I've thought about it a bit, and came to
the conclusion that I would have two branches, one I control and one
that all the developers could access. For projects where I'm
undisputed "owner", the branches are named "official-beta" (mine) and
"bleeding-edge" (open). For more democratically organized projects,
they'd be "official-beta" (open) and "steves-choice" (mine).
Note that darcs makes it easy to maintain your public branch, you just
pull and say "no" to anything that looks worrisome. Instead you test
it in a separate branch (which is what you would do anyway, right? so
it's not part of the "maintenance cost" of the published branch). And
it's at worst linear in how long you've been away.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
