All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: Xen 4.5 Development Update (GA slip by a week)
Date: Tue, 6 Jan 2015 10:11:33 -0500	[thread overview]
Message-ID: <20150106151133.GD7773@l.oracle.com> (raw)
In-Reply-To: <21675.62431.917500.191502@mariner.uk.xensource.com>

On Tue, Jan 06, 2015 at 02:40:31PM +0000, Ian Jackson wrote:
> (CC list replaced by just the list.)
> 
> konrad.wilk@oracle.com writes ("Xen 4.5 Development Update (GA slip by a week)"):
> > <==== WE ARE HERE ===>
> >  Release Date: Jan 14th.
> 
> There are two remaining dates left unspecified in your mail:
> 
>  * When do we branch for 4.5 ?  I think we should do this right away
>    so that we can set up osstest to have a working push gate for 4.5
>    by the time of the release.

I concur. Would you be OK doing that?


> 
>    This will work best with coordination with all committers to avoid
>    stuff appearing on staging after staging-4.5 is created.

Um, not following you. I think we want people to put patches in staging,
just not 4.5 material?


> 
>    The implication of branching of course is that 4.6-unstable becomes
>    open for business.

Right.
> 
>  * What is the last commit deadline for 4.5 ?
> 
>    We need time to wait for a test push, discover a possible problem,
>    and perhaps revert.  A week would be best, but maybe a bit less

How long do those 'test push' take?
>    would be OK.
> 
> Ian.

  reply	other threads:[~2015-01-06 15:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 20:08 Xen 4.5 Development Update (GA slip by a week) konrad.wilk
2015-01-06  8:58 ` Sander Eikelenboom
2015-01-06 11:43 ` Ian Campbell
2015-01-06 14:32   ` Konrad Rzeszutek Wilk
2015-01-06 14:36     ` Ian Jackson
2015-01-06 14:40 ` Ian Jackson
2015-01-06 15:11   ` Konrad Rzeszutek Wilk [this message]
2015-01-06 15:31     ` Ian Jackson
2015-01-06 16:01       ` Konrad Rzeszutek Wilk
2015-01-07 11:12         ` Olaf Hering
2015-01-06 15:11 ` Lars Kurth
2015-01-06 15:16   ` Konrad Rzeszutek Wilk
2015-01-08 19:30     ` Xen 4.5 Development Update (GA slip by a week), GA slip + 1 day Konrad Rzeszutek Wilk
2015-01-09 13:51       ` Lars Kurth
     [not found]         ` <54AFE358.60901@linaro.org>
2015-01-09 14:20           ` Julien Grall
2015-01-09 18:30         ` Konrad Rzeszutek Wilk
2015-01-12 11:36           ` Lars Kurth
2015-01-06 15:28   ` Xen 4.5 Development Update (GA slip by a week) Ian Campbell
2015-01-06 18:08     ` Suriyan Ramasami
2015-01-06 18:51       ` Lars Kurth
2015-01-06 18:54         ` Suriyan Ramasami
2015-01-06 20:23           ` Suriyan Ramasami
2015-01-07  9:53             ` Ian Campbell
2015-01-06 16:27   ` Xen 4.5 final commit deadline: end of Wednesday 7th January Ian Jackson
2015-01-06 17:24 ` Xen 4.5 Development Update (GA slip by a week) - reviewing experimental/preview tags Lars Kurth
2015-01-06 17:59   ` Konrad Rzeszutek Wilk
2015-01-06 18:57   ` Jan Beulich
2015-01-06 19:05     ` Andrew Cooper
2015-01-20  9:00 ` Xen 4.5 Development Update (GA slip by a week) Jan Beulich
2015-01-20 10:35   ` Ian Campbell
2015-01-20 10:46     ` Jan Beulich
2015-01-20 17:10   ` Lars Kurth
2015-01-20 19:07   ` Konrad Rzeszutek Wilk

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=20150106151133.GD7773@l.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Jackson@eu.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.