From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Status of 3.0.2?
Date: Tue, 11 Apr 2006 13:02:38 -0500 [thread overview]
Message-ID: <443BEF3E.5040308@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA211@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> I'm fine with a release date of "when it's ready" but I'm a
>> bit confused with the status of 3.0.2. Has it been released
>> already? There are tarballs labeled 3.0.2 on the Cambridge
>> site and there was a 3_0_2_release tag applied a bit ago.
>> There's also a fair bit of churn in both trees that seems to
>> suggest we may be passed the 3.0.2 freeze.
>>
>> I'd greatly appreciate if you could clarify where we're at in
>> the release process.
>>
>
> I'm afraid there have been delays building the various RPMs (not for any
> technical reasons, but due to a flu outbreak). Since more people use the
> RPMs rather than the source or binary install tar balls, it seemed daft
> to announce the release on the mailing lists and update the web pages.
> The 3.0.2 src and tar balls are up at the usual places for anyone that
> wants to grab them. We hope to get 3.0.2-1 RPMs up in he next 24h and
> officially announce the release.
>
Thanks for the explanation!
Regards,
Anthony Liguori
> Ian
>
next prev parent reply other threads:[~2006-04-11 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 16:35 Status of 3.0.2? Ian Pratt
2006-04-11 18:02 ` Anthony Liguori [this message]
2006-04-11 18:23 ` Itamar Reis Peixoto
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 15:02 Anthony Liguori
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=443BEF3E.5040308@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.