<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>So for the time library, these are my current understandings:</div><div><br></div><div>1. GHC will use the "ghc" branch of the source code, which I generally keep matched to the latest version of the library in Hackage.</div><div><br></div><div>2. If GHC HQ (or anyone) has a problem with the library, they will create an issue (or possibly a PR) in the library GitHub.</div><div><br></div><div>3. As the maintainer, I will fix library issues that block GHC releases (possibly with the help of GHC HQ).</div><div></div><div><br></div><div>4. If there are no issues that need to be fixed, library releases and GHC releases do not need to be synchronised.</div><div><br></div><div>-- Ashley Yakeley</div><div><br></div><div>On Mon, 2019-07-01 at 13:22 -0400, Ben Gamari wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hi everyone,</div><div><br></div><div>GHC's core libraries are a critical part of the Haskell ecosystem. I</div><div>want to thank you for overseeing the maintenance of this infrastructure.</div><div><br></div><div>However, for the last three weeks the release candidate for GHC 8.8.1</div><div>has been ready aside from releases of a couple of our core libraries.</div><div><br></div><div>Naturally, delays like this make it hard for GHC to maintain its faster</div><div>release cycle. At the same time, we do not want this cadence to impose</div><div>an undue burden on our core library maintainers.</div><div><br></div><div>How do you think we might speed up this process?</div><div><br></div><div>For instance, perhaps the GHC release manager could pick up</div><div>some of the "boring parts" of core library maintenance limited to:</div><div><br></div><div> * Version bound bumps</div><div><br></div><div> * Changes of CPP conditionals to accommodate changes in the</div><div> compiler and other core libraries</div><div><br></div><div> * Changelog entries to describe these releases</div><div><br></div><div> * Uploading these releases or revisions to Hackage</div><div><br></div><div>Of course, this would merely be an offer to maintainers; this would be</div><div>GHC's way of carrying some of the burden that our release process</div><div>imposes.</div><div><br></div><div>In general, I am interested in a discussion on how to make this faster</div><div>release pace work. Ideas?</div><div><br></div><div>Cheers,</div><div><br></div><div>- Ben</div><div><br></div></blockquote></body></html>