For what it's worth, Cabal is now recommending that migration information
be included in PRs' changelog entries.
On Thu, Dec 5, 2024 at 4:40 AM Teofil Camarasu
Hi folks,
With GHC 9.12 around the corner, I just wanted to give folks a gentle nudge to continue filling out the 9.12 migration guide https://gitlab.haskell.org/ghc/ghc/-/wikis/migration/9.12.
Ideally we would have an entry for each change that can break user code. And each entry would explain: - what the change is - what error messages caused by the change look like - how users can fix their code
Though if you are aware of a breaking change and don't have the time to fill out a full entry, a stub is also appreciated and I (or someone else) can try to fill out the rest.
I was also wondering if we should better integrate the migration guide into our processes. Maybe it should be mentioned in the MR template, so entries are added as part of the MR flow? I think that's the point when folks have stuff paged in and have the most context, but I also don't want to add extra hoops to jump through. Any thoughts?
Cheers, Teo _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
-- brandon s allbery kf8nh allbery.b@gmail.com