<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>Thinking about this, it seems like the root cause of the problem is that the relationship between GHC and the core libraries is awkwardly caught between two different models.</div><div><br></div><div>In one model, the libraries are part of GHC, so the library maintainers are part of the GHC release team, that happen to be assigned these particular GHC features. If one member of the team can't work on their GHC feature for whatever reason, another member can step in.</div><div><br></div><div>In the other model, the libraries are dependencies of GHC. GHC can make requests upstream to the libraries, but will have to wait or work around any issues in the mean time.</div><div><br></div><div>-- Ashley</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>