[GHC DevOps Group] Release policies

[Boespflug, Mathieu]

Hi Mikhail,

I'm seeing

"GHC 8.2.2 includes Cabal 2.0.1.0.
GHC 8.2.1 includes Cabal 2.0.0.2.
GHC 8.0.2 includes Cabal 1.24.2.0.
GHC 8.0.1 includes Cabal 1.24.0.0.
GHC 7.10.3 includes Cabal 1.22.5.0.

2.0.1.0 November 2017
2.0.0.2 August 2017
1.24.2.0 December 2016
1.24.1.0 October 2016
1.24.0.0 May 2016"

At https://www.haskell.org/cabal/download.html. Clearly the timeline on
that page should be fixed then. But thanks for pointers re the actual Cabal
timeline.

July 22th (according to GHC download page): GHC-8.2.1... July 24th
(according to Hackage): Cabal-2.0.0.2...  Surely it's fair to afford
downstream tool authors more than *minus* 2 days of lead time to adapt?

Best,

Mathieu

On 13 December 2017 at 23:38, Mikhail Glushenkov <
mikhail.glushenkov at gmail.com> wrote:

> Hi Mathieu,
>
> On 13 December 2017 at 22:03, Boespflug, Mathieu <m at tweag.io> wrote:
> > * But actually if we look at their respective release notes, GHC 8.2.1
> was
> > relased in July 2017, even though the Cabal website claims that
> > Cabal-2.0.0.2 was released in August 2017 (see
> > https://www.haskell.org/cabal/download.html). So it looks like GHC
> didn't
> > just not give enough lead time about an upstream dependency it shipped
> with,
> > it shipped with an unreleased version of Cabal!
>
> If you look at
>
> http://hackage.haskell.org/package/Cabal-2.0.0.2 and
> http://hackage.haskell.org/package/cabal-install-2.0.0.0
>
> you'll see that Cabal-2.0.0.2 was uploaded to Hackage on Jul 24 2017,
> at the time of GHC 8.2.1 release, while cabal-install-2.0.0.0 was
> released in August, which is also when the 2.0 release was announced.
> This explains the discrepancy. Cabal-2.0.0.2 is the same version that
> ships with GHC 8.2.1.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devops-group/attachments/20171213/f3843b78/attachment.html>