On Friday 16 March 2007 18:58, Luca Barbato wrote: > Jason Stubbs wrote: > > That's not entirely true. The main trouble with refactoring portage code > > is that there is no defined public API and so even the littlest changes > > are likely to break things in gentoolkit and several of the portage gui > > front end packages. > > What about branching, doing the dirty stuff and let others fix their code?
I've worked on a branch in the past as has Brian and a lot of the code that went into 2.1.0 was done in a seperate branch. However, a lot of bugs that got fixed in the release branch never got fixed in the development branches and so switching wasn't really viable. For 2.1.0, a lot of the work that was done ended up being completely redone in the release branch. In hindsight, if the team had have worked together as a team on a dev branch and only critical bug fixes went into the release branch while the dev branch was being readied it would have worked. Proper coordination would be needed but I guess it still could... -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list
