From: Andrew Cooper <andrew.cooper3@citrix.com>
To: AL13N <alien@rmail.be>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: preparing for 4.3.1
Date: Tue, 8 Oct 2013 22:06:05 +0100 [thread overview]
Message-ID: <525473BD.9050604@citrix.com> (raw)
In-Reply-To: <3945349.SZpJraS940@localhost>
On 08/10/2013 21:42, AL13N wrote:
> Op vrijdag 27 september 2013 11:07:24 schreef Jan Beulich:
>> Aiming at a release later in October (before Xen Summit I would
>> hope), I'd like to cut RC1 next week.
>>
>> Please indicate any bug fixes that so far may have been missed
>> in the backports already done.
> any ETA on this rc1? i'd like to have 4.3.1 on Mageia, but i kindof need an
> rc1 before version freeze next week...
rc1 has been tagged in the tree for 7 days now.
http://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=refs/heads/staging-4.3
~Andrew
next prev parent reply other threads:[~2013-10-08 21:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 10:07 preparing for 4.3.1 Jan Beulich
2013-09-27 10:35 ` Andrew Cooper
2013-09-27 10:41 ` Ian Campbell
2013-09-27 10:45 ` Andrew Cooper
2013-09-27 11:45 ` Jan Beulich
2013-09-27 11:17 ` Dario Faggioli
2013-09-27 11:49 ` Jan Beulich
2013-09-27 13:26 ` Dario Faggioli
2013-09-28 11:50 ` Pasi Kärkkäinen
2013-09-30 6:30 ` Jan Beulich
2013-10-11 18:07 ` Ian Jackson
2013-10-11 18:11 ` Pasi Kärkkäinen
2013-10-08 20:42 ` AL13N
2013-10-08 21:06 ` Andrew Cooper [this message]
2013-10-08 21:23 ` M A Young
2013-10-09 5:50 ` AL13N
2013-10-09 7:46 ` M A Young
2013-10-09 9:05 ` Jan Beulich
2013-10-09 11:19 ` AL13N
2013-10-09 11:41 ` Jan Beulich
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=525473BD.9050604@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=alien@rmail.be \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--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).