Take the 2-minute tour ×  Let's say your team is working on 10
features/fixes for a sprint. At the end of the sprint, there are
one or two things that the product owner does not accept. But,
they would really like the other 8 or 9 to be released.  How do
you handle this? Using subversion, what would be the best
methodology to manage a sprint with the possibility that this
could happen?  share|improve this question You are so screwed
... hginit.com –  Job Aug 4 '11 at 4:00 not yet :) It hasn't
happened yet. I'm trying to anticipate and prepare for if/when
it does. –  Amy Anuszewski Aug 4 '11 at 13:24 add comment  4
Answers  up vote 3 down vote accepted  Subversion is going to be
the killer for you.  I was going to say put each feature in its
own branch and merge the branches to produce the release
candidate. Then if the customer decides to pull one or more
features you can re-merge excluding the branches of the rejected
features.  This will not be a trivial exercise with Subversion
however as its' branch mergi