RE: This is a major issue - much more than a bug!!!

> On Wed, Feb 27, 2013 at 7:25 PM, John Cowan <cowan_at_mercury.ccil.org>
> wrote:
> > Bob Archer scripsit:
> >
> >> So, rule number one with feature branches, merge early and merge often.
> >
> > And rule zero is, don't use feature branches: branch for releases
> > only, developing directly on trunk.
> >
>
> The SVN dev team thinks differently? (last item)
> http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-
> practices.html
>
> -Flávio

Agreed... we basically use the branch as needed system. A feature that is too large for one developer or one commit will be a feature branch.

Also, we don't use a common trunk. We have a path for each major release of our app (which is a copy/branch) of the previous version). We find it is much easier to work this way than do everything on a "trunk" and then branch for release. So, most of our dev is done in that versions branch/path and every now and then we will create a feature branch as I said above.

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3050043

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-02-28 15:32:08 CET