From: Don Slutz <dslutz@verizon.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: preparing for 4.2.3 and 4.1.6
Date: Fri, 12 Jul 2013 08:52:47 -0400 [thread overview]
Message-ID: <51DFFC1F.9080308@terremark.com> (raw)
In-Reply-To: <51DFDEC602000078000E460C@nat28.tlf.novell.com>
On 07/12/13 04:47, Jan Beulich wrote:
> Aiming at a release some time in August, I'd like to cut RC1-s by
> Thursday next week (as I'll be on a two week vacation starting
> Friday).
>
> Please indicate any bug fixes that so far may have been missed
> in the backports already done. A few fixes are currently stuck in
> master's staging branch (or pending to make it there) - these
> don't need to be named explicitly, I'm already planning to pull over
> the hypervisor ones as soon as they get out of staging. To my
> knowledge there hasn't been a run through tools side backports
> yet - whether that's a sign of there not being much to backport
> (apart from security fixes which are already there) I can't tell.
>
> Please note that according to the current plans and with 4.3
> having got released, 4.1.6 is expected to be the last
> Xenproject.org release of the 4.1 series.
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
I think it is important to get the bug fix:
*[PATCH] libxl_json: Fix backport of JSON_BOOL to 4.2.2
*http://www.gossamer-threads.com/lists/xen/devel/289420 into 4.2.3
Into 4.2.3. The code does not exist at 4.1
-Don Slutz
next prev parent reply other threads:[~2013-07-12 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 8:47 preparing for 4.2.3 and 4.1.6 Jan Beulich
2013-07-12 9:17 ` Ian Murray
2013-07-12 9:22 ` Jan Beulich
2013-07-12 9:30 ` Ian Murray
2013-07-12 10:05 ` Lars Kurth
2013-07-12 10:22 ` Jan Beulich
2013-07-12 11:18 ` Lars Kurth
2013-07-12 13:13 ` Ian Murray
2013-07-12 12:52 ` Don Slutz [this message]
2013-07-12 13:06 ` Ian Jackson
2013-07-12 13:53 ` Konrad Rzeszutek Wilk
2013-07-15 17:33 ` Stefano Stabellini
2013-07-17 11:03 ` Ian Jackson
2013-07-15 12:35 ` Daniel Kiper
2013-07-15 12:48 ` Jan Beulich
2013-07-17 11:37 ` Ian Jackson
2013-07-17 11:37 ` Ian Jackson
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=51DFFC1F.9080308@terremark.com \
--to=dslutz@verizon.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).