caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
Cc: John Prevost <j.prevost@cs.cmu.edu>, Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] bug-fix branches
Date: Tue, 30 Jul 2002 16:11:29 +0200	[thread overview]
Message-ID: <20020730161129.A27941@pauillac.inria.fr> (raw)
In-Reply-To: <20020730083751.GA1041@iliana>; from luther@dpt-info.u-strasbg.fr on Tue, Jul 30, 2002 at 10:37:51AM +0200

> Xavier, don't you think it would be a good time for going with a dual cvs
> branch scheme or something like that, where you have a released branch
> (3.05, and bugfix releases : 3.05.1, 3.05.2, etc) and a development
> branch (which will become 3.06).

The need for this isn't apparent yet: we haven't yet encountered a
situation where a show-stopper bug appears, but the main CVS branch is
far from a releasable state.  One reason for this is that major
evolutions of the system, e.g. polymorphic methods or dynamic loading
of C libraries, are carried on separate branches, and merged back only
when they are in a usable state.  

> In this case, will you revert all your changes and reapply after having
> released the bugfix version, hurry the developpment so you can ship the
> new version fixing the bug, or just let the bug stay until the next
> version is released ?

If that happens, we'll do what works best, and that might very well be
a bugfix branch.  But, frankly, this is our internal "cuisine", and I
don't see why you and other users should care.

- 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


  reply	other threads:[~2002-07-30 14:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 12:45 [Caml-list] OCaml 3.05 released Xavier Leroy
2002-07-29 14:36 ` Nicolas Cannasse
2002-07-30  0:46 ` Shawn Wagner
2002-07-30  3:50 ` Scott J.
2002-07-30  7:34   ` John Prevost
2002-07-30  7:46   ` [Caml-list] Serious typechecking error involving new polymorphism (crash) John Prevost
2002-07-30  7:58     ` Xavier Leroy
2002-07-30  8:22       ` John Prevost
2002-07-30  8:47         ` Xavier Leroy
2002-07-30  8:37       ` Sven LUTHER
2002-07-30 14:11         ` Xavier Leroy [this message]
2002-07-30 16:15           ` [Caml-list] bug-fix branches Sven LUTHER
2002-08-01  9:37           ` [Caml-list] 3.05 and future 3.06 binary compatibility ? root
2002-08-01 12:09             ` [Caml-list] " Xavier Leroy
2002-08-01 15:56               ` Sven LUTHER
2002-08-08  8:37               ` Sven LUTHER
2002-08-09 12:25                 ` Xavier Leroy
2002-08-09 13:16                   ` Sven LUTHER
2002-07-30  7:51   ` [Caml-list] OCaml 3.05 released Dmitry Bely
2002-07-30 15:01     ` Scott J.
2002-07-30 15:11       ` Dmitry Bely
2002-08-02  5:31   ` Jacques Garrigue
2002-08-02 11:15     ` Tim Freeman
2002-07-30  7:48 ` [Caml-list] Record with one non mutable filed Christophe Raffalli
2002-07-30 11:49 ` [Caml-list] OCaml 3.05 released Yaron M. Minsky

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=20020730161129.A27941@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=j.prevost@cs.cmu.edu \
    --cc=luther@dpt-info.u-strasbg.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).