From mboxrd@z Thu Jan 1 00:00:00 1970 From: Don Slutz Subject: Re: preparing for 4.2.3 and 4.1.6 Date: Fri, 12 Jul 2013 08:52:47 -0400 Message-ID: <51DFFC1F.9080308@terremark.com> References: <51DFDEC602000078000E460C@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uxcwh-0004c7-E1 for xen-devel@lists.xenproject.org; Fri, 12 Jul 2013 12:59:35 +0000 In-Reply-To: <51DFDEC602000078000E460C@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel , Ian Jackson , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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