-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only use -Werror in validate #9867
Conversation
Reverts a change that made `-Werror` be applied when building in tree Cabal, even when just developing. Puts `-Werror` back in the `cabal.project.validate` validation project. Fixes haskell#9866
@fendor, FYI, the merging process has changed since you made numerous contributions to cabal last time. It's now described in https://github.com/haskell/cabal/blob/master/CONTRIBUTING.md#github-pull-request-conventions Setting the merge label would ensure mergify rebases and runs CI, if needed, so we'd avoid the non-linear history that sneaked in. This also incurs a 2 day delay, which I understand you wanted to avoid, given that devs are inconvenienced by this unintended change continuously. The informal process for avoiding the delay, as people on the Matrix channel would tell you, is to announce the intention in the ticket, ask for objections and wait for a few hours. If there are objections, escalate (e.g., on the Matrix channel), if no objections, |
I am terribly sorry, this was unintentionally against policy and sincerely apologise. I should have read the conventions more carefully, and will do so before I try to merge a PR next time. |
I'm good with this change, moving where the |
@Mergifyio backport 3.12 |
✅ Backports have been created
|
Only use -Werror in validate (backport #9867)
Reverts a change that made
-Werror
be applied when building in tree Cabal, even when just developing. Puts-Werror
back in thecabal.project.validate
validation project.Fixes #9866