On Thu, 2010-12-02 at 16:06 -0600, Brian Jackson wrote: > On Monday, November 29, 2010 11:42:49 am Anthony Liguori wrote: > > Hi, > > > > 0.13 was a mess of a release (largely due to my lack of time) and I'd > > like to get us back onto a predictable schedule. > > > > Here's what I propose: > > > > 12/6 - fork off stable-0.14 tree; simultaneously release qemu-0.14.0-rc0 > > > Have you considered a frozen master style release like other projects use? > (Linux kernel, etc.) > > Every project I follow that does this "branch stable keep master moving" > release thing has terrible releases every time. Patches don't make it back > into stable,etc... Basically a lot of the same stuff we saw for 0.13. > >
Being fimilar with the kernel development process but not fimilar with pre qemu-kvm.git development process, I would tend to agree with you here.. Aside from that question, the one thing that is really useful in the kernel development world is having an automated process to CC sta...@kernel.org in order to signal that a bugfix commit from 'master' should be propigated down into stable trees and/or branches works very well. This really simplfies the bug backport process, compared to say each needing to do this by hand across a number of old stable versions. This is how Greg-KH and kernel subsystem maintainers do things, and the system works quite well with Greg tracking a handful of rolling stable releases. I am not sure if Anthony already has such an automated system in place for QEMU yet, but I think it would really be helpful for propigating master bugfixes back into stable code. Best, --nab
