Hi,
It's getting to be about the time to start thinking about the 0.11.0
release. 0.10.0 was released on March 2nd so following with the 6 month
release cycle, that would put 0.11.0 at September 2nd.
Based on the experiences with the stable releases, here's what I'd
recommend:
o On July 15th, fork master -> stable-0.11
o Change version to 0.10.90
o Release qemu-0.11.0-rc1
o Release additional -rcN releases every 1-2 weeks
o Introduce a new maintainer for stable-0.10 (via git pulls)
o At least 1 week before release, hopefully we'll have the final -rcN
that we can then declare 0.11.0.
I think we should really try hard to make these dates. I only have a
few things that I would like to see happen before forking stable-0.11.
Namely:
o Setup qemu.org infrastructure (git hosting, wiki)
o Setup qemu bug tracker (see next mail)
o Include all ROM source code in tree via git submodules. This is a
major headache for distributors and I think it's important to resolve
before our next release.
o Disable kqemu by default. The intention is _not_ to remove kqemu
support. Enabling kqemu by default causes a few unpleasant side effects
including errors if -m is greater than 1/2 of the host physical memory.
I don't expect the qdev conversion will be complete by 0.11. I think we
should try to get as much of the invasive changes as possible in to make
stable-0.11 as maintainable as possible. However, I think it would be a
mistake to gate the release on qdev.
--
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
