All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [RFC] 1.0 release schedule adjustment (spreading out RCs)
Date: Thu, 06 Oct 2011 10:26:48 -0500	[thread overview]
Message-ID: <4E8DC8B8.5010809@us.ibm.com> (raw)

Hi,

I'm trying to map out the 1.1 release using the same formula as the 1.0 release. 
  To make things work a bit better, I'd like to adjust the -rc schedule a bit. 
Namely:

| 2011-11-01
| Freeze master
|-
| 2011-11-04  ->   2011-11-07
| Tag qemu-1.0-rc1
|-
| 2011-11-11  ->   2011-11-14
| Tag qemu-1.0-rc2
|-
| 2011-11-18  ->   2011-11-21
| Tag qemu-1.0-rc3
|-
| 2011-11-23  ->   2011-11-28
| Tag qemu-1.0-rc4
|-
| 2011-12-01
| Tag qemu-1.0

I had squashed things originally because of the US Thanksgiving holiday on the 
25th but realistically, the 28th is no better than the 23rd.  This spreads out 
the -rcs a bit more evenly.

Any thoughts/objections?

Regards,

Anthony Liguori

             reply	other threads:[~2011-10-06 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 15:26 Anthony Liguori [this message]
2011-10-08 10:23 ` [Qemu-devel] [RFC] 1.0 release schedule adjustment (spreading out RCs) Blue Swirl

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=4E8DC8B8.5010809@us.ibm.com \
    --to=aliguori@us.ibm.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.