From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id SAA32278; Tue, 30 Jul 2002 18:37:24 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id SAA32418 for ; Tue, 30 Jul 2002 18:37:23 +0200 (MET DST) Received: from mel-rto2.wanadoo.fr (smtp-out-2.wanadoo.fr [193.252.19.254]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id g6UGbM909274; Tue, 30 Jul 2002 18:37:22 +0200 (MET DST) Received: from mel-rta10.wanadoo.fr (193.252.19.193) by mel-rto2.wanadoo.fr (6.5.007) id 3D1838B60125849F; Tue, 30 Jul 2002 18:37:21 +0200 Received: from iliana (80.9.197.176) by mel-rta10.wanadoo.fr (6.5.007) id 3D2A791600A6DBC8; Tue, 30 Jul 2002 18:37:21 +0200 Received: from luther by iliana with local (Exim 3.35 #1 (Debian)) id 17ZZea-0000Bg-00; Tue, 30 Jul 2002 18:15:20 +0200 Date: Tue, 30 Jul 2002 18:15:10 +0200 To: Xavier Leroy Cc: Sven LUTHER , John Prevost , Caml-list Subject: Re: [Caml-list] bug-fix branches Message-ID: <20020730161510.GA713@iliana> References: <20020729144527.A30919@pauillac.inria.fr> <000f01c2377c$36263060$2097fea9@janxp> <86vg6xlktk.fsf_-_@laurelin.dementia.org> <20020730095833.B6564@pauillac.inria.fr> <20020730083751.GA1041@iliana> <20020730161129.A27941@pauillac.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020730161129.A27941@pauillac.inria.fr> User-Agent: Mutt/1.4i From: Sven LUTHER Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On Tue, Jul 30, 2002 at 04:11:29PM +0200, Xavier Leroy wrote: > > 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. Ok, i didn't know that. > > 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. Because it is easier to simply get a cvs version out of the bugfix branch than having to look at the current cvs branch and extract from it a bugfix patch, which may, or may not easily apply to the current released version. You know i did this for the powerpc fix for 3.04, and this doesn't apply so much to big errors, which are often discovered early and were you do a bugfix release, but for smaller problems for which you don't necessarily think they would need a bugfix release. Anyway, i was just asking, and i didn't know about the separate branches for major evolutions, i guess this means that it will always be easy to get a patch i need out of cvs and apply it to the released version. But then, i know that you don't like for distributors to have versions of ocaml which differ from the official releases, and having minor patch number would help in identifying what the user is running exactly, without having to remember that he is running debian and that i had to apply this or that patch. Anyway, i was just asking, if you feel it is your internal "cuisine" and we should not meddle with it, i will understand. Friendly, Sven Luther ------------------- 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