On Monday 24 May 2004 3:59 am, Daniel F Garcia wrote:
> I was having a think today, that in an open source project there may
> be more of a need to review changes before they go into the
> repository. This is because there are a large number of developers,
> each of whom have their own needs and agendas.
> Is there a view to add some sort of approval facility into subversion
> where a commit goes into some queue and waits for approval ?
Most of the other replies I've seen talk about using transactions,
modifying subversion to specially support this, etc. Those are probably
cool, clean ways to do it.
However, if you're willing to work with the current system, you can get
mostly the same results by using branches. The basic idea would be to
let each user or group apply their changes to a branch that they have
control over; the person/group doing the approval could then pull
changesets out of this branch and apply them to the mainline as they
are approved, or else ignore them. So basically, a branch for either
each task, or a branch for each user, whichever way makes more sense.
Of course, you can do much more complex things....
It's kind of academic, but this
<http://www.cmcrossroads.com/bradapp/acme/branching/> place has a lot
of good ideas of have to use branching to accomplish quite a lot of
things, pretty much tool independant (although I think it was written
with Perforce in mind, which I have never used).
Wesley J. Landaker <firstname.lastname@example.org>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2
Received on Tue May 25 00:44:22 2004
- application/pgp-signature attachment: signature