All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>, Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"Justin M. Forbes" <jmforbes@linuxtx.org>,
	Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [RFC] Planning for 1.0 (and freezing the master branch)
Date: Thu, 11 Aug 2011 08:46:09 -0500	[thread overview]
Message-ID: <4E43DD21.9030907@us.ibm.com> (raw)

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

             reply	other threads:[~2011-08-11 13:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 13:46 Anthony Liguori [this message]
2011-08-11 17:30 ` [Qemu-devel] [RFC] Planning for 1.0 (and freezing the master branch) Blue Swirl
2011-08-11 18:21   ` Anthony Liguori
2011-08-11 21:54     ` Gerd Hoffmann
2011-08-12 20:46       ` Blue Swirl
2011-08-14 13:46         ` Anthony Liguori
2011-08-14 19:30           ` Blue Swirl
2011-08-15 17:59             ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E43DD21.9030907@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=jmforbes@linuxtx.org \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.