From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] CVS tracking and 3.08 testing
Date: Thu, 1 Jul 2004 15:41:08 +0200 [thread overview]
Message-ID: <20040701134108.GA29861@yquem.inria.fr> (raw)
To all OCaml users who track the CVS or are willing to beta-test:
We are progressing towards a release of OCaml 3.08, and at the same
time experimenting with a two-branch development model, one branch for
short-term bug fixes and the other for longer-term developments.
If this model turns out to work well, we hope it will make it easier
for users to benefit from bug fixes between major releases, and speed
up the release process.
Users who track the CVS sources from camlcvs.inria.fr are encouraged
to switch to the current release branch, which is labeled "release308".
This is the branch where we currently do bug fixes before release 3.08
and where we'll do post-release bug fixes if needed. It is currently
more up-to date than the main branch, which is the development branch,
and will remain so for a couple of months at least. To switch your
CVS checked-out sources to the release branch, just do
cvs update -r release308
Users who are willing to beta-test the upcoming 3.08 release should
also get the sources from the "release308" branch of the CVS:
cvs -d ":pserver:anoncvs@camlcvs.inria.fr:/caml" checkout -r release308 ocaml
Now is a very good time to test and report bugs.
Thanks for your cooperation,
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2004-07-01 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 13:41 Xavier Leroy [this message]
2004-07-01 14:12 ` skaller
2004-07-01 15:40 ` Xavier Leroy
2004-07-09 18:14 ` Benjamin Geer
2004-07-01 16:58 ` Markus Mottl
2004-07-07 23:51 ` Aleksey Nogin
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=20040701134108.GA29861@yquem.inria.fr \
--to=xavier.leroy@inria.fr \
--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).