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

Bump base, lens and possibly others for GHC 9.10.1 #60

Closed
wolfgangwalther opened this issue Jun 2, 2024 · 6 comments · Fixed by #61
Closed

Bump base, lens and possibly others for GHC 9.10.1 #60

wolfgangwalther opened this issue Jun 2, 2024 · 6 comments · Fixed by #61

Comments

@wolfgangwalther
Copy link

No description provided.

@ysangkok
Copy link

ysangkok commented Jul 3, 2024

@phadej This should now be unblocked, if it was blocked because of a missing cabal-install-3.12 release.

@phadej
Copy link
Owner

phadej commented Jul 3, 2024

it wasn't

@ysangkok
Copy link

ysangkok commented Jul 3, 2024

Just for curiosity, is there another blocker?

@phadej
Copy link
Owner

phadej commented Jul 3, 2024

I'm not aware of any.

I do my best to update libraries I wrote & maintain. I do that in some not-very-deterministic order, but it will happen eventually. Pinging me won't make me do that faster nor change the order.

And I don't really need help in bounds bumping. I'd need to give up maintainership completely, so I don't need to worry about the library ever again. For most libraries I wouldn't, as I care about them enough. But insert-ordered-containers isn't a library I use anywhere myself anymore, so I'd be more than happy to transfer ownership to someone else.

@ysangkok
Copy link

ysangkok commented Jul 3, 2024

Pinging @maksbotan or @swamp-agr, maybe they would be interested, since this package seems to be mostly used because it is a dependency of swagger2 and openapi3.

Do you want to transfer ownership to just a single person, or wouldn't you mind to have multiple people added? If you look at e.g. Servant, it has accrued a large amount of Hackage maintainers over time. Not sure if I like that model, because it can mean that nobody feels responsible, but OTOH it doesn't seem to be abused. So you could argue that it makes it easier to avoid the package takeover process, since it is more likely that there is somebody available to hand over the maintainer bit.

@phadej
Copy link
Owner

phadej commented Jul 3, 2024

Do you want to transfer ownership to just a single person, or wouldn't you mind to have multiple people added?

The keyword is transfer (it implies I'm not involved anymore), what happens after should not be my worry.

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 a pull request may close this issue.

3 participants