From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] 3.11?
Date: Tue, 02 Sep 2008 13:51:03 +0200 [thread overview]
Message-ID: <48BD28A7.3070803@inria.fr> (raw)
In-Reply-To: <20080830213300.GA10224@annexia.org>
> I asked about 3.11 and when it would be released, and the answer at
> that time was in late August:
>
>
http://groups.google.com/group/fa.caml/tree/browse_frm/thread/15126f960406e056/531fda06c1da700e
>
> Obviously August (2008?) is slipping away. Do we have any updates on
> the status of 3.11?
We made good progress during the summer, but a bit of polish and code
review is needed before the release.
> The reason I ask is that the Fedora 10 beta deadline has slipped
> because of the security intrusion two weeks ago, which means there is
> a slim possibility of getting 3.11 into Fedora 10, if the release
> happens real soon.
I'm afraid 3.11 will not be ready in time for Fedora 10.
- Xavier Leroy
prev parent reply other threads:[~2008-09-02 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 21:33 3.11? Richard Jones
2008-09-02 11:51 ` Xavier Leroy [this message]
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=48BD28A7.3070803@inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=rich@annexia.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