Skip to content
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

Merged
merged 2 commits into from
Apr 11, 2024
Merged

Conversation

alt-romes
Copy link
Collaborator

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 #9866

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 fendor merged commit 8e971f5 into haskell:master Apr 11, 2024
53 checks passed
@Mikolaj
Copy link
Member

Mikolaj commented Apr 11, 2024

@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, merge [edit: rather, set the delay_passed label by hand] and prepare for a discussion and a possible revert later on. If you want to wait even less, announce in the Matrix channel, PM interested parties (that would be @philderbeast in this case), etc. I hope that sounds fair?

@fendor
Copy link
Collaborator

fendor commented Apr 11, 2024

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.

@philderbeast
Copy link
Collaborator

I'm good with this change, moving where the -Werror goes.

@Kleidukos
Copy link
Member

@Mergifyio backport 3.12

Copy link
Contributor

mergify bot commented May 16, 2024

backport 3.12

✅ Backports have been created

mergify bot added a commit that referenced this pull request May 20, 2024
Only use -Werror in validate (backport #9867)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

-Werror being used always, not only on validate
6 participants