caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mehdi Dogguy <mehdi@dogguy.org>
To: Fabrice Le Fessant <fabrice@lefessant.net>,
	caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml maintenance status / community fork
Date: Tue, 06 Dec 2011 20:24:48 +0100	[thread overview]
Message-ID: <4EDE6C00.2090104@dogguy.org> (raw)
In-Reply-To: <CAHvkLrMnQ4BrA7b+HDwn_B+gUQDe+LwFS=i-e7NWcTnX0e2Y1Q@mail.gmail.com>

On 12/06/2011 05:12 PM, Fabrice Le Fessant wrote:
> On Tue, Dec 6, 2011 at 11:58 AM, Stefano Zacchiroli <zack@upsilon.cc>
> wrote:
>> On Tue, Dec 06, 2011 at 11:51:00AM +0100, Fabrice Le Fessant 
>> wrote:
>>> For the OCaml distribution itself, OCamlPro will have a
>>> different release cycle for its own version, targetting
>>> industrial users, but the
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> 
>> Meaning that the code will not be freely (as in Free Software) 
>> available?  (in case you have already decided that)
> 
> If you check on Mantis, you will see that many patches have been 
> submitted by OCamlPro for inclusion in the mainstream OCaml 
> distribution. Our goal is not to compete with INRIA's distribution, 
> but to improve it (so, everything that OCamlPro does will be 
> submitted for inclusion in the mainstream distribution), and to 
> package it more often, providing/including bug fixes faster, with a 
> high quality testing process before each release, that fits the need
>  of industrial users for stability.
> 

For example, does it mean that [1] will be sent to upstream? It is in
"For Beta-testers" section for now… but, I'm pretty sure you'll have
more testers if the patch was publicly published (reading code helps
testing). And, if yes, then do you know when?

[1] http://www.ocamlpro.com/code/2011-05-06-longval.html

(I can't check ocaml's bugtracker content right now as it appears to be
offline. Apologies if that specific patch has been _publicly_ submitted
on mantis).

Regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/

  reply	other threads:[~2011-12-06 19:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  8:25 Benedikt Meurer
2011-12-06  9:17 ` Goswin von Brederlow
2011-12-06 10:08   ` Gaius Hammond
2011-12-06  9:31 ` rixed
2011-12-06 12:10   ` Benedikt Meurer
2011-12-06  9:42 ` Kakadu
2011-12-06  9:48   ` Joel Reymont
2011-12-06 10:51   ` Fabrice Le Fessant
2011-12-06 10:58     ` Stefano Zacchiroli
2011-12-06 16:12       ` Fabrice Le Fessant
2011-12-06 19:24         ` Mehdi Dogguy [this message]
2011-12-06 10:00 ` Gerd Stolpmann
2011-12-06 12:20   ` Benedikt Meurer
2011-12-06 10:35 ` Gabriel Scherer
2011-12-06 11:31   ` Gerd Stolpmann
2011-12-06 12:34     ` Benedikt Meurer
2011-12-15 18:49     ` Jérôme Benoit
2011-12-06 13:09   ` Goswin von Brederlow
2011-12-06 22:48   ` oliver
2011-12-07  7:23     ` Adrien
2011-12-06 11:40 ` Gabriel Scherer
2011-12-06 12:02   ` Stefano Zacchiroli
2011-12-06 12:16     ` Joel Reymont
2011-12-06 12:43       ` Stefano Zacchiroli
2011-12-06 12:27   ` François Bobot
2011-12-06 13:01   ` Benedikt Meurer
2011-12-06 13:52 ` ivan chollet
2011-12-06 14:42   ` Alexandre Pilkiewicz
2011-12-06 15:10     ` Gerd Stolpmann
2011-12-06 15:14       ` Yitzhak Mandelbaum
2011-12-06 15:24         ` Pierre-Alexandre Voye
2011-12-07  9:36       ` Goswin von Brederlow
2011-12-06 22:07 ` oliver
2011-12-07  9:39   ` Goswin von Brederlow
2011-12-07 20:42     ` oliver
     [not found] <201112071100.pB7B0N8J020839@walapai.inria.fr>
2011-12-07 13:59 ` tools
2011-12-07 14:37   ` Jérémie Dimino

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=4EDE6C00.2090104@dogguy.org \
    --to=mehdi@dogguy.org \
    --cc=caml-list@inria.fr \
    --cc=fabrice@lefessant.net \
    /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).