I'm not surprised you don't find much in the agile literature on this
topic.

Branches are a form of waste and the goal is to eliminate them, to
move to a single code stream, whose most recently released version is
the only supported version, which is forcibly pushed to all
installations on every release, with releases happening as frequently
as possible (ideally, one release per feature/defect).

All of which is made a lot simpler with SaaS.

Regards,

John A. De Goes
N-BRAIN, Inc.
http://www.n-brain.net
[n minds are better than n-1]

On Apr 16, 2008, at 1:51 AM, Michael Dubakov wrote:

> I think this question is not highlighted in books, articles and
> blogs. I did not find any
> comprehensive article. However the problem is pretty common. Team
> developing main
> release line (v.2), support release (v.1.x) line and future release
> line (v.3) in parallel. What do
> you think about that? How that should be handled in a single team?
>
> Starting point may be this post
>
>
http://www.targetprocess.com/blog/2008/04/should-we-have-parallel-releases-and.h\
tml
>
>
>



[Non-text portions of this message have been removed]