Re: Branching for V2.2

> And traditionally we have always used for the development and
> potentially
> 'breaking' changes. Personally I would prefer to keep doing it this
> way. I
> really dislike branch handling in svn and would prefer to have as
> little as possible
> to do with it.

I'm quite in a hurry here because there are some users that are waiting
for my changes.

Ideally, I would create a Git public repository mirroring the CS one and
would start using it for personal or unfinished changes. But I'm afraid
the mirroring process between the two repositories is a bit complex to
manage and I don't have currently the time to work around that.

So, I'll probably create a 'makehuman' branch in the CS tree, and merge
it back in trunk as soon as V2.2 is created.

Is it OK?


------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk