Timing of next release

[snoyberg]

Moving question from #202 (comment), which did not receive an answer.

What is the expected timing of a new release of hackage-security to Hackage? The current version of Hackage has bugs which are negatively impacting both cabal-install and Stack. See also: commercialhaskell/stack#3865

[hvr]

I intend to release this in time for the upcoming cabal-2.2 (which is intended to be released in 1-2 weeks; due to GHC 8.4 which requires cabal-2.2). There's a few other loose ends in lib:hackage-security I need to look at and I need to do test the new fallback code on AIX and Solaris (and I also don't want to rush a release only to have to push out a follow-up release a week later).

[snoyberg]

That makes sense, thank you for clarifying. We'll move ahead with pinning to a commit in Stack in the interim.

…

On Fri, Feb 16, 2018, 10:43 AM Herbert Valerio Riedel < ***@***.***> wrote: I intend to release this in time for the upcoming cabal-2.2 (which is intended to be released in 1-2 weeks; due to GHC 8.4 which requires cabal-2.2). There's a few other loose ends in lib:hackage-security I need to look at and I need to do test the new fallback code on AIX and Solaris (and I also don't want to rush a release only to have to push out a follow-up release a week later). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADBB82Ldp0amDZtJURSyCwrJxquax-Qks5tVT_GgaJpZM4SH6xU> .

[snoyberg]

Since Cabal 2.2 has been released but this hasn't, reopening to more clarification if you don't mind. The next Stack release depends on both hackage-security and Cabal 2.2, and if this isn't released to Hackage we'll need to ship with an unofficial release, leading to likely behavior mismatch with other distributions.

[hvr]

A little bit more patience; exe:cabal needs hackage-security as well, which is what I meant when I wrote "cabal-2.2" (note the capitalisation). ETA: early next week

[snoyberg]

Thanks for the update.

…

On Sun, Mar 11, 2018, 9:28 AM Herbert Valerio Riedel < ***@***.***> wrote: A little bit more patience; exe:cabal needs hackage-security as well, which is what I meant when I wrote "cabal-2.2" (note the capitalisation). ETA: early next week — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADBB76V9sGMNPaRcpRXOHUagvwBKvp3ks5tdNIvgaJpZM4SH6xU> .

[ghost]

Hasn't this been resolved via https://hackage.haskell.org/package/hackage-security-0.5.3.0?

[hvr]

@Tuncer indeed!