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

Next release, 0.8 #1059

Open
1 of 8 tasks
meooow25 opened this issue Oct 31, 2024 · 5 comments
Open
1 of 8 tasks

Next release, 0.8 #1059

meooow25 opened this issue Oct 31, 2024 · 5 comments

Comments

@meooow25
Copy link
Contributor

meooow25 commented Oct 31, 2024

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:

@Bodigrim
Copy link
Contributor

Bodigrim commented Nov 1, 2024

It's expensive to bump major version of containers, hundreds and thousands of packages would have to update. Please consider sticking to 0.7.*.

There is an upcoming release of GHC 9.12 very shortly, do you aim to release containers before that? As with any boot library, clients hardly ever use a release unless it is bundled with GHC.

@meooow25
Copy link
Contributor Author

meooow25 commented Nov 1, 2024

It's expensive to bump major version of containers, hundreds and thousands of packages would have to update. Please consider sticking to 0.7.*.

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.

There is an upcoming release of GHC 9.12 very shortly, do you aim to release containers before that? As with any boot library, clients hardly ever use a release unless it is bundled with GHC.

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.

@flip111
Copy link

flip111 commented Nov 17, 2024

GHC 9.12 is sticking to 0.7

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?

@treeowl
Copy link
Contributor

treeowl commented Nov 17, 2024

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.

@meooow25
Copy link
Contributor Author

meooow25 commented Nov 18, 2024

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.

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

No branches or pull requests

4 participants