From: "AL13N" <alien@rmail.be>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
M A Young <m.a.young@durham.ac.uk>
Subject: Re: preparing for 4.3.1
Date: Wed, 9 Oct 2013 13:19:23 +0200 [thread overview]
Message-ID: <583e5e745935f301334727500c8e2e2f.squirrel@mail.rmail.be> (raw)
In-Reply-To: <5255388B02000078000F9E68@nat28.tlf.novell.com>
>>>> On 09.10.13 at 07:50, AL13N <alien@rmail.be> wrote:
>> Op dinsdag 8 oktober 2013 22:23:32 schreef M A Young:
>>> On Tue, 8 Oct 2013, Andrew Cooper wrote:
>>> > 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
>>> You might get the full version in time for your freeze. According to
>>> http://xenbits.xen.org/xsa/ there are 5 security updates due for
>>> release
>>> tomorrow, which might be all the full version is waiting for.
>>>
>>> Michael Young
>>
>> ah, i didn't think 4.3.1 would have these patches in...
>>
>> but if it's been unchanged the last 7 days, does this mean the 3 or so
>> patches
>> spoken of, in this thread, aren't included?
>
> I think I said quite clearly in the RC1 announcement that RC2
> will need to wait for IanJ's return, so that the tools side can be
> taken care of (where I think we had a couple of additional
> backport requests).
ah, ic, by this you mean that the rc1 is a tag and is not actually
released as a tarball... ( or it is, and i've missed it? )
next prev parent reply other threads:[~2013-10-09 11:19 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
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 [this message]
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=583e5e745935f301334727500c8e2e2f.squirrel@mail.rmail.be \
--to=alien@rmail.be \
--cc=JBeulich@suse.com \
--cc=m.a.young@durham.ac.uk \
--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).