All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <George.Dunlap@eu.citrix.com>
To: xen-devel <xen-devel@lists.xenproject.org>,
	Lars Kurth <lars.kurth@xen.org>,
	Russell Pavlicek <russell.pavlicek@citrix.com>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Thu, 5 Dec 2013 16:54:10 +0000	[thread overview]
Message-ID: <CAFLBxZaVKZ2WffX2Zf822qTXX_p15uqVFpD6g8N2JfhREkBCdg@mail.gmail.com> (raw)
In-Reply-To: <CAFLBxZYvTK9BiVwi=Nt48aSRAZ_1xFY5dHNdnMVzGMtF8JUFOg@mail.gmail.com>

On Thu, Dec 5, 2013 at 4:09 PM, George Dunlap
<George.Dunlap@eu.citrix.com> wrote:
> This information will be mirrored on the Xen 4.4 Roadmap wiki page:
>  http://wiki.xen.org/wiki/Xen_Roadmap/4.4
>
> We're nearly to the completion of the code freeze, scheduled for
> tomorrow.  After the code freeze, only bug fixes and features marked
> as "blockers" will be considered.  At the moment, the only feature
> considered a blocker is experimental PVH dom0 support.
>
> In early RCs, most bug fixes will be accepted; but in later RCs, even
> bug fixes may be rejected if they risk breaking more important
> functionality than they fix.
>
> I don't think at this point every bug fix needs a blessing from me;
> committers, if there are fixes which are obviously low-risk, just go
> ahead and check them in.
>
> I was thinking that for some of our new features, it would be good to
> have a blog post describing the feature and how to test it.  This
> would both raise awareness of the feature, and hopefully get it more
> testing before the release.  We could choose a couple to focus on for
> each test day.

Lars / Russ,

We should be able to cut an RC0 sometime next week.  Do you want to
plan a test day for 16 December, and then maybe another one for 6
January?

 -George

  parent reply	other threads:[~2013-12-05 16:54 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 16:09 Xen 4.4 development update: RC0 imminent George Dunlap
2013-12-05 16:29 ` George Dunlap
2013-12-05 16:34   ` Wei Liu
2013-12-05 16:39     ` George Dunlap
2013-12-05 16:48       ` Wei Liu
2013-12-05 16:59         ` Ian Campbell
2013-12-05 17:06           ` Wei Liu
2013-12-05 17:16             ` Ian Campbell
2013-12-05 17:34               ` Wei Liu
2013-12-05 17:53                 ` George Dunlap
2013-12-05 18:03                   ` Wei Liu
2013-12-06  9:27                     ` Ian Campbell
2013-12-06 10:51                       ` Wei Liu
2013-12-05 16:39   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:41     ` George Dunlap
2013-12-05 16:42   ` Roger Pau Monné
2013-12-05 16:51     ` George Dunlap
2013-12-05 17:01       ` Lars Kurth
2013-12-05 17:04         ` George Dunlap
2013-12-05 20:06           ` Russell Pavlicek
2013-12-05 23:54             ` Sander Eikelenboom
2013-12-06  9:39             ` Lars Kurth
2013-12-06 12:14             ` George Dunlap
2013-12-05 16:59   ` David Vrabel
2013-12-05 17:05     ` George Dunlap
2013-12-05 17:40       ` Dario Faggioli
2013-12-05 17:07     ` George Dunlap
2013-12-05 17:01   ` Olaf Hering
2013-12-05 17:06     ` David Vrabel
2013-12-05 17:32   ` Dario Faggioli
2013-12-06 13:30   ` Fabio Fantoni
2013-12-05 16:34 ` Andrew Cooper
2013-12-06  9:07   ` Jan Beulich
2013-12-06 13:07     ` George Dunlap
2013-12-06 14:58       ` Jan Beulich
2013-12-05 16:54 ` George Dunlap [this message]
2013-12-16 10:50   ` Lars Kurth

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=CAFLBxZaVKZ2WffX2Zf822qTXX_p15uqVFpD6g8N2JfhREkBCdg@mail.gmail.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=lars.kurth@xen.org \
    --cc=russell.pavlicek@citrix.com \
    --cc=xen-devel@lists.xenproject.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.