From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: alex@baretta.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Possible bug in module and class?
Date: Tue, 22 Oct 2002 11:16:42 +0900 [thread overview]
Message-ID: <20021022111642R.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <3DB3F02B.6070401@baretta.com>
From: Alessandro Baretta <alex@baretta.com>
> I'm using O'Caml in an industrial project. Of course, I'd
> like to make sure that I give my customers the most stable
> environment possible. As more and more bugs are found and
> fixed in the CVS version, the temptation to upgrade from the
> official distribution becomes stronger. But is the CVS
> version usually more or less buggy than the official distro?
There is no official guideline that I know, but considering other
problems like binary compatibility, switching to a CVS version can
always create trouble. Personally I would not suggest doing that for
an industrial project, except maybe if the deadline is more than 9
month ahead (i.e. you are reasonnably sure that a new release will be
available by that time).
On the upside, you can profit immediately from bug fixes, and
avoid preemptively bugs that would break your code in an upcoming
release. From this point of view, if you're a very active user, maybe
having the CVS version around for testing can be useful.
Concerning whether there are more or less bugs in the CVS versions,
like for all projects I would say this goes in cycles.
Typically, just after a release people do not immediately introduce
new features, and many bug reports come in, so that for a while the
number of bugs is actually going down. Then you may get a big change
and it suddenly goes up, then down again thanks to benevolent CVS
testers.
Since there is no strict rule about when to commit (except code
freezes just before releases), it is very hard to tell what is the
current situation.
My personnal feeling that the CVS version of a few days ago is
more stable than 3.06, but then I don't test all parts of the
compiler.
Last thing, for people who might be tempted to use the CVS version:
please do not release code requiring the CVS version to run. Forcing
it on other people may break their own programs. But this is just
classical advice I believe.
Cheers,
Jacques Garrigue
-------------------
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 prev parent reply other threads:[~2002-10-22 2:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 20:16 Bow-Yaw Wang
2002-10-21 6:26 ` Jacques Garrigue
2002-10-21 12:16 ` Alessandro Baretta
2002-10-21 12:32 ` Luc Maranget
2002-10-21 12:51 ` Alessandro Baretta
2002-10-22 2:16 ` Jacques Garrigue [this message]
2002-10-22 4:35 ` [Caml-list] Camlp4 pretty print comments Quetzalcoatl Bradley
2002-10-22 11:15 ` Daniel de Rauglaudre
2002-10-22 12:40 ` Sven Luther
2002-10-22 13:18 ` Stefano Zacchiroli
2002-10-22 13:44 ` Maxence Guesdon
2002-10-22 14:21 ` Daniel de Rauglaudre
2002-10-21 21:00 ` [Caml-list] Possible bug in module and class? Bow-Yaw Wang
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=20021022111642R.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=alex@baretta.com \
--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).