Login | Register
My pages Projects Community openCollabNet

Discussions > users [DISABLED] > RE: Troubled by a strategy that has developers creating feature branches from latest release rather than trunk

subversion
Discussion topic

There will be a brief maintenance window every Friday at 17:00 Pacific.
For further details, see CollabNet's maintenance and upgrade policy.

Back to topic list

RE: Troubled by a strategy that has developers creating feature branches from latest release rather than trunk

Author "Erik Hemdal" <erik at comprehensivepower dot com>
Full name "Erik Hemdal" <erik at comprehensivepower dot com>
Date 2009-03-17 14:14:13 PDT
Message This private reply apparently did not make it to the list.

> -----Original Message-----
> From: Brett Stahlman [mailto:smoochpappy at gmail dot com]
> Sent: Tuesday, March 17, 2009 2:46 PM
> To: Erik Hemdal
> Subject: Re: Troubled by a strategy that has developers
. . . .
> It seems to me that the code would be traceable to the
> preceding release with either approach. The bigger issue to
> me is the ugliness of the merges.
>

Yes, it would. I was thinking about the case where code gets imported from
somewhere, which is a problem I've had to deal with in the past. That's not
the same thing as starting from somewhere like a tag.

The nastier issue is the merge, because you are kind of deliberately not
letting SVN merge tracking help you out. And you don't get full value from
developer testing if they are not taking changes from trunk into account. I
think you are correct on all those points.

> > If there is a hard business requirement for the proposed plan, then
> > you won't be able to adopt the "Subversion Way".  But the
> stated need
> > might not be the real need.  There might be other needs that no one
> > has thought of. The proposed solution might not be the only one.
>
> I'm pretty sure no such business case exists. As you may have
> been pointing out above, however, the Subversion model does
> provide traceability to the preceding release, regardless of
> whether developers create their branches from the latest
> release or the trunk.

There may be some other reason then. Maybe members of the team have been
burned by merge and build problems in the past or by the series of
annoyances that David mentioned. But there's some reason -- valid or
invalid -- why people are suggesting the model. Try to understand that
point of view. Whatever the result, I think that a solution that everyone
embraces is the one you want. Just be ready to make adjustments based on
experience.

>
>. . . .
> >
> > Good luck, and I hope this helps.
>
> Thanks. I appreciate your response.
> Brett Stahlman
>

« Previous message in topic | 1 of 1 | Next message in topic »

Messages

Show all messages in topic

Subject
Author
Full name
Date posted
+
RE: Troubled by a strategy that has developers creating feature branches from latest release rather than trunk "Erik Hemdal" <erik at comprehensivepower dot com> "Erik Hemdal" <erik at comprehensivepower dot com> 2009-03-17 14:14:13 PDT
Messages per page: