Re: Subversion tagging

Byron Brummer wrote:
> Your model makes the assumption that anything checked in by
> a developer automatically "works" and thus anything else
> can be piled on top and keep going forward. In the real
> world even if the change *does* work *exactly* as everyone
> intended, there are a ton of other reasons it may need to
> get pulled back. The design team didn't like out it looked
> when they finally saw it, the legal department has an issue
> with it, some contract that was in the works failed to go
> through and it legally *can't* be put in production yet (or
> maybe ever, but ya don't know). Etc, etc.

Maybe it shouldn't have been checked in yet, if the relevant parties
hadn't approved it. What I would do in this contrived example is to
send the diff to the parties who need to approve it, and if it gets
through, then commit it.

Daniel

-- 
Daniel Noll
Nuix Pty Ltd
Suite 79, 89 Jones St, Ultimo NSW 2007, Australia    Ph: +61 2 9280 0699
Web: http://nuix.com/                               Fax: +61 2 9212 6902
This message is intended only for the named recipient. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
message or attachment is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org