From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrVak-0000TL-39 for qemu-devel@nongnu.org; Thu, 11 Aug 2011 09:46:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QrVah-0005e5-Sy for qemu-devel@nongnu.org; Thu, 11 Aug 2011 09:46:34 -0400 Received: from e4.ny.us.ibm.com ([32.97.182.144]:57270) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrVah-0005dU-Oq for qemu-devel@nongnu.org; Thu, 11 Aug 2011 09:46:31 -0400 Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e4.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7BDNNr2020618 for ; Thu, 11 Aug 2011 09:23:23 -0400 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7BDkGZV3076128 for ; Thu, 11 Aug 2011 09:46:16 -0400 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7BDkFHD032277 for ; Thu, 11 Aug 2011 10:46:16 -0300 Message-ID: <4E43DD21.9030907@us.ibm.com> Date: Thu, 11 Aug 2011 08:46:09 -0500 From: Anthony Liguori MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [RFC] Planning for 1.0 (and freezing the master branch) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel , Kevin Wolf Cc: Stefan Hajnoczi , "Michael S. Tsirkin" , Marcelo Tosatti , "Justin M. Forbes" , Blue Swirl , Avi Kivity , "Edgar E. Iglesias" , Aurelien Jarno , Gerd Hoffmann Hi, I've posted an initial proposal for the 1.0 release on the wiki[1]. The release would be targeted for December 1st. Unlike previous releases, I'm proposing that instead of forking master into a stable branch and releasing from there, we stop taking features into master and all work on stablizing master. Historically, we forked stable for the releases simply because it was the least intrusive way to get us on a somewhat reasonable release schedule. I think especially since we're targeting a 1.0, we're ready to get a bit more serious about releases. I see the following advantages in using master for releases: 1) All maintainers are participating in the process which means releases are much less likely to be delayed due to lack of time from a single person. 2) Everyone (contributors) are forced to focus on stability which should improve the release's quality. 3) Feature development can still happen in maintainers trees. I think this is an important step to moving to a merge-window based development model which I think will be our best way to scale long term. Obviously, this will only work well if all the maintainers participate so I'd really like to hear what everyone thinks about this. [1] http://wiki.qemu.org/Planning/1.0 Regards, Anthony Liguori