caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, caml-list@inria.fr
Subject: Re: [Caml-list] About contributions to the Standard Library
Date: Mon, 11 Jul 2016 11:48:32 +0200	[thread overview]
Message-ID: <20160711094832.GA13615@notk.org> (raw)
In-Reply-To: <583E8E2B027F438686B3428432F20F17@erratique.ch>

On Mon, Jul 11, 2016, Daniel Bünzli wrote:
> Le lundi, 11 juillet 2016 à 09:55, Goswin von Brederlow a écrit :
> > I think the time is better spend of releasing ocaml more frequently than making
> > more work by splitting compiler and stdlib.
> 
> […]
> 
> > 3) is a big reason for me. Or if not stable then at least testing.
> > There is also Ubuntu and others with long term releases where versions
> > can remain lower than would be good.
> 
> […]  
> 
> If 3) is important to you then releasing ocaml more frequently won't change anything to the problem.  
> 
> One of the big problem and reason I have not been able to simply always targeting the latest I naturally need to implement a package is *precisely* because of distributions lagging far behind from the current released version — 4.01 was released almost three years ago and that's what we have in debian stable.  

And this is why there are time-based releases of software projects which
moreover try to align with the schedule of distributions for their
stable versions. For debian oldstable, the OCaml release arrived only a
few weeks, at most months, late; I wouldn't blame Debian for not going
with something that was known to not be very stable.

-- 
Adrien Nader

  reply	other threads:[~2016-07-11  9:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 11:56 Damien Doligez
2016-06-21 15:48 ` Gabriel Scherer
2016-06-21 15:54   ` [Caml-list] About "precise (formal) things that can be said about properties of certain interfaces" David MENTRE
2016-06-21 19:11     ` Gabriel Scherer
2016-06-21 20:06       ` Jesper Louis Andersen
2016-06-22 15:33   ` [Caml-list] About contributions to the Standard Library Junsong Li
2016-06-22 21:31   ` Alain Frisch
2016-07-07 10:26   ` Daniel Bünzli
2016-07-08 14:01     ` Alain Frisch
2016-07-08 14:37       ` Daniel Bünzli
2016-07-11  8:55         ` Goswin von Brederlow
2016-07-11  9:43           ` Daniel Bünzli
2016-07-11  9:48             ` Adrien Nader [this message]
2016-07-11 10:28               ` Daniel Bünzli
2016-07-11 18:34                 ` Adrien Nader
2016-07-11 20:36                   ` Daniel Bünzli
2016-07-11  9:49             ` Goswin von Brederlow
2016-07-12 18:32           ` Ian Zimmerman
2016-07-12 19:01             ` Gabriel Scherer
2016-07-12 21:26               ` Ian Zimmerman
2016-07-12 22:35                 ` Gabriel Scherer
2016-07-12 23:20                   ` Ian Zimmerman
2016-06-27  9:09 ` Goswin von Brederlow
2016-06-27 11:19   ` Gerd Stolpmann
2016-06-27 13:21     ` Gabriel Scherer
2016-06-30 11:08       ` Goswin von Brederlow
2016-06-30 15:52         ` Gabriel Scherer
2016-06-30 10:59     ` Goswin von Brederlow

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=20160711094832.GA13615@notk.org \
    --to=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --cc=goswin-v-b@web.de \
    /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).