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

[skip ci] Upgrade GHC to 8.8.4 #1204

Merged
merged 30 commits into from
Sep 28, 2020
Merged

[skip ci] Upgrade GHC to 8.8.4 #1204

merged 30 commits into from
Sep 28, 2020

Conversation

akshaymankar
Copy link
Member

@akshaymankar akshaymankar commented Sep 14, 2020

@akshaymankar akshaymankar changed the title [skip ci] Upgrade GHC to 8.8.3 [skip ci] Upgrade GHC to 8.8.4 Sep 21, 2020
@akshaymankar akshaymankar marked this pull request as ready for review September 21, 2020 09:44
@akshaymankar
Copy link
Member Author

Copy link
Member

@jschaul jschaul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good.

Two things:

  1. can the dependencies be based on merged commits, rather than hanging branches that may disappear by accident?

Special pipeline here: https://bridge-ie-concourse.zinfra.io/teams/main/pipelines/wire-server-ghc88.

  1. can the ubuntu-based Docker image also be tested with ghc-8.8? The pipeline seems to include an ubuntu image as well; however I cannot find the pipeline code that was used to create this pipeline anywhere. Please link.

stack.yaml Outdated Show resolved Hide resolved
stack.yaml Outdated
@@ -64,7 +64,7 @@ extra-deps:
# a version > 1.0.0 of wai-middleware-prometheus is available
# (required: https://github.com/fimad/prometheus-haskell/pull/45)
- git: https://github.com/wireapp/saml2-web-sso
commit: 687d9ac8ac2994aff8436189c6ecce29faad8500 # master (May 18, 2020)
commit: be04baaffb92ff64d8e1d9f400ec45849d754faf # akshaymankar/ghc-8.8 (Aug 21, 2020)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The various forks should have a reference to a stable branch, not a PR branch which will be deleted after merging the PR. Perhaps before merging this PR; merge the upstream ones and use a stable branch commit identifier?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is the only one we control. I created PR here: wireapp/saml2-web-sso#66
No other branches will get deleted on merge, I have set the option to not delete it in Gitlab. For github forks we don't need to worry as github only deletes branches in the same repo.

I suspect some of the upstream maintainers aren't maintaining the packages very actively, so it might take very long. So, I think it is fine to refer to these packages in their forks.

@akshaymankar akshaymankar merged commit fab4983 into develop Sep 28, 2020
@akshaymankar akshaymankar deleted the akshaymankar/ghc-8.8 branch September 28, 2020 11:46
@jschaul jschaul mentioned this pull request Oct 5, 2020
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.

2 participants