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 20:34:51 +0200	[thread overview]
Message-ID: <20160711183451.GA20894@notk.org> (raw)
In-Reply-To: <A709E778398F4B03846974981DE06DA0@erratique.ch>

On Mon, Jul 11, 2016, Daniel Bünzli wrote:
> Le lundi, 11 juillet 2016 à 10:48, Adrien Nader a écrit :
> > 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.
> 
> Sure, but what strikes me is that people feel that supporting the OCaml version distributed by mainstream system packagers is important.  
> 
> I see the later as being a medium to distribute end-user application that are installable by the same package system not as a medium that is useful to support the working OCaml programmer.

I see it as important because things get a bit sad if your code never
reaches end-users.
If you look around, you'll see that many large-ish projects have shifted
to time-based releases. That said, I don't like calling them
"time-based" because the approach is more to limit the scope and avoid
schedule slips by having a clear and simple measurement (time left
before the given day) that is also known in advance.

Of course, with time-based releases, it is also possible to synchronize
in order to always release right after distros freeze. The idea is
rather to take them into account because getting stable and
reasonably-recent software to users is really. Releasing stable versions
is a time-consuming work not matter the topic and I don't find it sane
to not take them into account.

-- 
Adrien Nader

  reply	other threads:[~2016-07-11 18:34 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
2016-07-11 10:28               ` Daniel Bünzli
2016-07-11 18:34                 ` Adrien Nader [this message]
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=20160711183451.GA20894@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).