On Thu, Sep 1, 2011 at 11:25 AM, Brendan Flanagan
<brendan.flanagan_at_wegobeyond.co.uk> wrote:
>
> They support and develop enhancements to a purchased product (they don't
> have the source for the purchased product, only their enhancements).
>
> They want "trunk" to reflect the current Production Release of their
> enhancements only. They intend creating a branch called "Development" that
> the small number of developers will use day to day - i.e. they will add new
> enhancements, change existing code etc.
The nature of the product may make this unlikely, but what happens
when/if they need to concurrently support and fix bugs in more than
one release version - that is, if either the base product branches, or
all of their customers can't or won't upgrade to their latest at the
same time? While subversion itself doesn't really care about the
directory names, if you release from branches it is obvious that you
can have several active concurrently, but you normally only ever have
one trunk.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2011-09-01 20:00:53 CEST