[Chandler-dev] How we develop post Preview : SVN topology

[Philippe Bossut]

Hi again,

One thing I forgot to ask: the counter point to creating lots of 
branches under SVN is that they are hard to work with/manage. Since most 
devs will have 2 branches now, this is something to ponder.

In the past year though, some of you (Morgen, Jeffrey, Andi, Grant) have 
had experience with developing on branches and developed a set of "best 
practices" to make it work (daily trunk merge for instance).

Would be great if you guys could share these experience here for the 
benefit of all so that everyone understand what developing with branches 
on SVN is all about.

Cheers,
- Philippe

Grant Baillie wrote:
>
> There's an s3 here:
>
> - Stable trunk (i.e. 0.7.x work) + per-feature (and/or per-developer) 
> branches. This is essentially how twisted does things IIRC.
>
> Personally, I don't have a particularly strong opinion about this 
> choice. For example, no-one is singing the praises of s2, but I'd be 
> fine with it. (Using SVK, it's not a big deal to merge properly 
> between branches. My pattern is to make local branches often anyway).
>
> --Grant