[GHC DevOps Group] Making GHC's fast release cadence work

[David Terei]

Ben, Everyone,

Great timing! I noticed this the other day for the pretty library that I
maintain. For me, the best solution would be to find a new maintainer. I
can post on the general ghc/haskell mailing lists for someone who's
interested, or if the core GHC team or anyone here could take this on
please let me know.

I've not been involved in the Haskell/GHC communities for a while now and
sadly I don't see that changing anytime soon. My work on pretty is limited
to life-support, I don't have the time to review and accept any code
changes beyond trivial ones.

Cheers,
David

On Mon, 1 Jul 2019 at 10:22, Ben Gamari <ben at well-typed.com> wrote:

> Hi everyone,
>
> GHC's core libraries are a critical part of the Haskell ecosystem. I
> want to thank you for overseeing the maintenance of this infrastructure.
>
> However, for the last three weeks the release candidate for GHC 8.8.1
> has been ready aside from releases of a couple of our core libraries.
>
> Naturally, delays like this make it hard for GHC to maintain its faster
> release cycle. At the same time, we do not want this cadence to impose
> an undue burden on our core library maintainers.
>
> How do you think we might speed up this process?
>
> For instance, perhaps the GHC release manager could pick up
> some of the "boring parts" of core library maintenance limited to:
>
>  * Version bound bumps
>
>  * Changes of CPP conditionals to accommodate changes in the
>    compiler and other core libraries
>
>  * Changelog entries to describe these releases
>
>  * Uploading these releases or revisions to Hackage
>
> Of course, this would merely be an offer to maintainers; this would be
> GHC's way of carrying some of the burden that our release process
> imposes.
>
> In general, I am interested in a discussion on how to make this faster
> release pace work. Ideas?
>
> Cheers,
>
> - Ben
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devops-group/attachments/20190701/a2448dd9/attachment.html>