-
Notifications
You must be signed in to change notification settings - Fork 178
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
Next release, 0.8 #1059
Comments
It's expensive to bump major version of There is an upcoming release of GHC 9.12 very shortly, do you aim to release |
We have breaking changes so we do need a major version bump. The changes aren't drastic (at least in the public API), but they are still breaking changes.
GHC 9.12 is sticking to 0.7 (GHC #25123), which is fine. Anyway, the release is not happening right now. This is just to get the ball rolling and track what we want to include, we can decide the time of release once these issues are resolved. |
I'm not sure but i have the feeling they put that version number there because it was the latest version available. Perhaps it would be nice to have a new containers version together with a new major ghc versions because at that point several things have to be upgraded anyway. Though i can understand it would perhaps be too short notice. Would it go into ghc 9.14 then? or a point release of 9.12? |
I don't think a point release is likely to take a major release of containers. If we want to get a major release in, now is probably the last time. |
Yes, 0.8 should make it into 9.14. Even if it's not too late for 9.12, I don't see a good reason to rush the release. A new major release means other core libraries also need to update to accept the new containers, which is a lot of work. Another thing I want to make sure is that we include all the breaking changes we want to at once, so we don't need another major release in the near future. |
It's been a while since 0.7 and we've accumulated commits, should we start preparing for a release?
Pending things I'd like to see done/fixed for 0.8:
The text was updated successfully, but these errors were encountered: