openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #01549
Re: Feature Freeze status
On Mon, Mar 28, 2011 at 1:38 PM, Justin Santa Barbara
<justin@xxxxxxxxxxxx> wrote:
> No objection to a discussion during the summit, but I've been able to watch
> all of these branches and others evolve here:
> https://code.launchpad.net/nova
> For example, when I wanted to add VNC support because my system wouldn't
> boot, it was easy for me to look at the vnc_console branch and get the
> libvirt XML magic from there. If I was feeling brave, I could have grabbed
> the whole branch and merged it into my tree. That feels _very_ open to me.
Rubbish. Open development means knowing the general directions and
specifications that people are working on by open discussions, open
blueprints/specs, and active communication between teams. I can go to
github and see how many people "forked this" (ugh.). That doesn't give
me any clue as to what people are attempting to do with the code in
the long term.
The problem we've been having revolves around the fact that we have
dozens of developers working on Nova, with no real guidance as to the
long-term direction of the project, and teams just doing whatever the
heck they want to, without ML discussion and blueprints, and then
expecting people to just merge branches a few days before feature
freeze.
> <jaypipes_troll> Just another benefit of bazaar being a centralized version
> control system, I guess </jaypipes_troll>
I don't know what the heck you are talking about.
-jay
Follow ups
References