All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Delaying -rc0?
Date: Mon, 02 Mar 2015 13:33:23 +0100	[thread overview]
Message-ID: <54F45893.5080802@redhat.com> (raw)

Looks like there are still a few pull requests pending, and Peter is on
vacation.  Should we really enter hard feature freeze tomorrow?  The 2.3
planning page in the end never got out the "draft" state.

A possible alternative schedule could be:

2015-03-10 	Tag v2.3.0-rc0
2015-03-17 	Tag v2.3.0-rc1
2015-03-24 	Tag v2.3.0-rc2
2015-03-31 	Tag v2.3.0-rc3
2015-04-03 	Tag v2.3.0      (or -rc4, with release on April 7th)

In this case maintainers should still try not to post new non-bugfix
pull requests for the coming week, while the pending ones are sorted out.

Paolo

             reply	other threads:[~2015-03-02 12:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 12:33 Paolo Bonzini [this message]
2015-03-02 12:44 ` [Qemu-devel] Delaying -rc0? Peter Maydell
2015-03-02 13:11   ` Paolo Bonzini
2015-03-03 13:12     ` Marcel Apfelbaum
2015-03-03 13:57       ` Paolo Bonzini
2015-03-03 14:57         ` Gerd Hoffmann
2015-03-03 15:07         ` Marcel Apfelbaum
2015-03-03 15:14           ` Peter Maydell
2015-03-04  7:27             ` Markus Armbruster
2015-03-04 12:13               ` Gerd Hoffmann
2015-03-04 12:19                 ` Michael S. Tsirkin
2015-03-04 12:26             ` Michael S. Tsirkin
2015-03-04 16:48               ` Markus Armbruster
2015-03-04 17:20                 ` Michael S. Tsirkin
2015-03-04 12:08           ` Gerd Hoffmann
2015-03-02 21:42 ` Stefan Hajnoczi
2015-03-03 13:37 ` Michael S. Tsirkin
2015-03-04  7:27   ` Markus Armbruster

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=54F45893.5080802@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.