On Sat, Mar 15, 2008 at 10:20 PM, Chris <shef31_at_yahoo.com> wrote:
> I don't think that the best answer is to implement a delete function in
> a repository. A better answer is to have a decent workflow system so
> that changes can get reviewed before they get committed.
>
> There are probably multiple good ways to implement this. One that I have
> in mind is to have three repositories. The first is for rough drafts:
> developers should check their code into it frequently whether the code
> works or not. Developers promote code from the first to the second when
> they think their code is ready for review. A team lead promotes the code
> from the second to the third "production" repository only after it has
> gone through review and all unit tests.
How is this different than having (in 1 repository):
/employees
/reviewed
/production
?
Bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-15 22:50:02 CET