Branched and non-branched work flows?

Hi everyone,

I have a situation here where one developer prefers avoiding branching
code (from release version 1 of software to v2), when possible because
he finds branches a time-waste, due to workflow overhead when trying
to make the same change to both the released v1 and the unreleased v2.

And another developer prefers branching code from v1 to v2 ahead of
time, "just in case", that something will change, and because he
prefers to "think about" the two versions as separate code bases.

The situation for both developers (working on the same product), is
that right now there are no branched files or files we can for sure
foresee that it will need branching. In fact for all the work I can
forsee that there will be no need to branch any files. The only
problem we can forsee are having to disable features for v2 that
shouldn't be accessed yet from v1.

So... what's the best way to go ahead? Assuming we want fast
development times.

1) Branch the code anyhow, and make the workflow slower for developer 1?

2) Revert to non-branched mode, because it's faster and we have no
need for any file to be branched, and tell developer 2 that he is
being "precious" with his way of seeing things?

3) Something else? Can we have both branched and non-branched working
directorys? Or is that simply an impossible thing?

The situation is that both developers are pretty firmly "dug in" to
their way of working and convincing either to change their way of
working may be harder than finding something that works for both.

Ideas anyone? feel free to give your opinions even if it's not so much
"here is a technical solution" but more "well here is a personal
solution to get one (or both) to have a different attitude."

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2357659

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-01 20:40:10 CEST