On Tue, May 05, 2009 at 04:15:03PM +0100, Carlos Valiente wrote: > > > Applied to the 'next' branch. Thanks! > > Thanks, Iustin. If I submit more patches, should I be working on 'next' > instead? > > I think this patch in particular should go to 'master' as well: It's > really annoying to run 'ganeti-watcher' under cron without it.
So, the git migration and organization is something that we didn't discuss on the public list (unfortunately). Basically, we're aiming to make 2.0.0 with only the absolute required patches. Once that is done, the 'next' branch will be merged to master and start QA and be released as 2.0.1. So: master will become 2.0.0; next will become 2.0.1 soon afterwards. But non-absolutely-needed patches will not go right now on master. As for this patch, it can go on master indeed. Does this make sense? iustin
