[haiku-development] Re: Haiku git migration status?

> Not that I want to continue something unproductive, but the A3 process
> switched me from firmly in the camp of revision numbers being important
> to the opposite opinion.
> 
> Lots of bug-fixes were being committed to trunk, but as the nightlies
> were only coming from the A3 branch, it was pretty difficult to tell if
> a particular nightly had a fix included. This led to some confusion in
> bug reports on trac IIRC. I expect the git switch will lead to more
> independent branches (I entirely missed all of Ingo's recent package
> management stuff as it wasn't showing up on the commits list) which
> might make that kind of confusion more common.

This is because the branch just lasted for too long. With git this won't 
happen anymore, as the experimental features will not be in trunk, but in 
developper branches. The result is a more stable trunk that can be made 
into a release in a week or so, without too much bug fixes involved.

-- 
Adrien.

Other related posts: