From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Release date for 3.11?
Date: Wed, 4 Jun 2008 17:12:52 +0100 [thread overview]
Message-ID: <20080604161252.GA16447@annexia.org> (raw)
In-Reply-To: <48457575.5030906@inria.fr>
On Tue, Jun 03, 2008 at 06:46:45PM +0200, Xavier Leroy wrote:
> > I'm sure the answer will be 'when it's ready', but is there a release
> > date (month / year / ...) for 3.11 or release candidates of 3.11?
>
> I'd like to release by late August, provided no show-stopping problems
> show up by then.
If we wanted to follow CVS more closely, eg. in our development
version, should we follow CVS head or are there other branches or tags
that we should look at? I notice someone mentioned a "ocaml311+dev"(?)
tag, but I can't find any tag like that in the CVS web interface.
Rich.
--
Richard Jones
Red Hat
prev parent reply other threads:[~2008-06-04 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 7:26 Richard Jones
2008-06-03 16:46 ` [Caml-list] " Xavier Leroy
2008-06-04 16:12 ` Richard Jones [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=20080604161252.GA16447@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
/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).