Friends As part our efforts to ship a more complete and comprehensive > release notes for the next major release, we would > appreciate cooperation in not assigning Marge for MRs that > don't have a changelog and make user visible changes. If your > MR truly does not need a changelog entry, label it 'no-changelog'.
Just to add a PS to Zubin's post, he is highlighting a real change to GHC's CI system: - *In future, when you submit a merge request (MR) for GHC, you will need to provide a change-log entry (almost always)* Why? It's so that every GHC release comes with a complete list of all the changes that have been made in that release. As things stand, the release manager makes a best-efforts attempt to summarise the stream of MRs, but that person isn't necessarily familiar with the specifics and may well miss important stuff. Plus it is a painful and laborious task. It's not hard: a change-log entry is just a short file with a simple summary of the change. Details on this page <https://gitlab.haskell.org/ghc/ghc/-/wikis/contributing/changelog>. It does add a little bit of friction, but not much compared to the effort of finding and fixing the bug! This is all part of our main page on how to contribute a patch to GHC <https://gitlab.haskell.org/ghc/ghc/-/wikis/Contributing-a-Patch>. I am truly grateful to you for contributing to GHC. I mean it: GHC only flourishes because lots of generous people offer their time to make it happen. Thank you! Simon
_______________________________________________ ghc-devs mailing list -- [email protected] To unsubscribe send an email to [email protected]
