Hi everyone, this announcement is especially relevant to you if you contribute to cabal-install.
To reduce the amount of bad surprises that we get after each release, a manual QA process is being set up so that more eyes may look at some of the more user-facing changes that are introduced in cabal-install. In addition to the incentive to add QA Notes that is being added to relevant PRs (https://github.com/haskell/cabal/pull/8886), I have created a kanban board that aggregates tickets and PRs being tagged for manual QA <https://github.com/orgs/haskell/projects/3/views/1>. The idea is that we can onboard volunteers who will compile cabal-install any time after the contribution has been merged, and will test the described workflow to see if it holds, in real-life conditions, and certainly with external factors at play that will help us gather valuable feedback on the behaviour of cabal-install. Speaking of feedback, please do not hesitate to show scepticism or support regarding this initiative. I'm always happy to be able to discuss such things between stakeholders. Cheers, Your lovely release manager, Hécate
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
