caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Louis Gesbert <louis.gesbert@ocamlpro.com>
To: caml-list@inria.fr, Mehdi Dogguy <mehdi@dogguy.org>
Subject: Re: [Caml-list] [ANN] OPAM 1.2.0
Date: Fri, 24 Oct 2014 17:24:55 +0900	[thread overview]
Message-ID: <1919725.JXBnejpNnf@agaric> (raw)
In-Reply-To: <40127c451511cbd61121e98fb9bca1f3@dogguy.org>

Indeed, 1.2.0-rc4 has been promoted to 1.2.0 ; the sources are identical, and no upgrade is required if you were already on RC4.

Release is shown on https://github.com/ocaml/opam/releases, but latest, latest-test, rc4 and 1.2.0 being on the same commit, github orders them in its own way (and displays the date of the commit as date of the release, which is kind of wrong).

Sorry for the confusion. And thanks a lot for the packaging efforts !

Le vendredi 24 octobre 2014, 10:06:13 Mehdi Dogguy a écrit :
> Le 2014-10-24 07:55, Louis Gesbert a écrit :
> > We're very proud to announce the final release of OPAM 1.2.0
> > 
> > This is a big step after 1.1, with lots of new features and a huge
> > effort put into improving the ease of use, output and error handling.
> > Read the full announcement at
> > 
> >     http://opam.ocaml.org/blog/opam-1-2-0-release
> > 
> 
> On https://github.com/ocaml/opam/tags, I see that rc4 and the final
> release are made from the same commit. Is that correct? IOW, for those
> whose use rc4, do they have to upgrade to the final release? The 
> release
> is also not mentioned on https://github.com/ocaml/opam/releases. So
> maybe I picked up the wrong tarball.
> 
> Regards,
> 
> 


  reply	other threads:[~2014-10-24  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  5:55 Louis Gesbert
2014-10-24  8:06 ` Mehdi Dogguy
2014-10-24  8:24   ` Louis Gesbert [this message]
2014-10-24  8:29     ` Mehdi Dogguy

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=1919725.JXBnejpNnf@agaric \
    --to=louis.gesbert@ocamlpro.com \
    --cc=caml-list@inria.fr \
    --cc=mehdi@dogguy.org \
    /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).