From: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
To: Damien Doligez <damien.doligez@inria.fr>,
David Allsopp <dra-news@metastack.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 4.04.0+beta1
Date: Fri, 12 Aug 2016 10:58:01 +0000 [thread overview]
Message-ID: <CAHvkLrPfqBWL-L4HYMHX5CBMVAtAv7PBbAbpyHUAWRey5a5Sqg@mail.gmail.com> (raw)
In-Reply-To: <8E48ABE1-F29A-4F24-816A-636F57717335@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Actually, OPAM is supposed to follow Debian versioning conventions, to the
best of my knowledge. However, it does not really matter for compilers,
since you always specify the version to create the switch, but it might
become a problem in the future, with compilers as packages.
I also think that following a "standard" versioning system (such as the
Debian one) is a win, for the future, even if it would break compatibility
for a short while. Maybe we could decide to switch for the next release
(4.05) ?
--Fabrice
On Fri, Aug 12, 2016 at 12:48 PM Damien Doligez <damien.doligez@inria.fr>
wrote:
>
> > On 2016-08-11, at 18:28, David Allsopp <dra-news@metastack.com> wrote:
> >
> > Wouldn't it only ever break it for alpha/beta/rc releases, though? Might
> that be a price worth paying (next time)?
>
> Breaking beta releases is a very big deal: a broken beta is a beta that
> nobody will test. Moreover, OPAM does not implement the convention you are
> suggesting, so it would do more harm than good.
>
> -- Damien
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 1930 bytes --]
next prev parent reply other threads:[~2016-08-12 10:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 13:15 Damien Doligez
2016-08-09 14:24 ` Goswin von Brederlow
2016-08-11 15:10 ` Damien Doligez
2016-08-11 16:28 ` David Allsopp
2016-08-12 10:47 ` Damien Doligez
2016-08-12 10:58 ` Fabrice Le Fessant [this message]
2016-08-12 12:09 ` Damien Doligez
2016-08-12 12:23 ` Daniel Bünzli
2016-08-12 12:25 ` Grégoire Henry
2016-08-12 12:50 ` David Allsopp
2016-08-16 12:37 ` Damien Doligez
2016-08-16 12:44 ` Gabriel Scherer
2016-08-16 12:54 ` David Allsopp
2016-08-26 14:00 ` Louis Gesbert
2016-09-05 9:24 ` Goswin von Brederlow
2016-08-12 12:46 ` David Allsopp
2016-08-12 14:56 ` [Caml-list] Debian's version-numbering convention Hendrik Boom
2016-08-12 15:57 ` David Allsopp
2016-08-12 16:06 ` Hendrik Boom
2016-08-09 16:06 ` [Caml-list] OCaml 4.04.0+beta1 Mohamed Iguernlala
2016-08-10 16:42 ` Mohamed Iguernlala
2016-08-10 16:46 ` Anil Madhavapeddy
2016-08-12 10:09 ` Fabrice Le Fessant
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=CAHvkLrPfqBWL-L4HYMHX5CBMVAtAv7PBbAbpyHUAWRey5a5Sqg@mail.gmail.com \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@inria.fr \
--cc=damien.doligez@inria.fr \
--cc=dra-news@metastack.com \
/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