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 bound for vector-binary-instances #181

Closed
athas opened this issue Oct 2, 2018 · 4 comments
Closed

Bump base bound for vector-binary-instances #181

athas opened this issue Oct 2, 2018 · 4 comments

Comments

@athas
Copy link

athas commented Oct 2, 2018

Could a revision be added to http://hackage.haskell.org/package/vector-binary-instances-0.2.4 that bumps the base bound from <4.12 to <4.13? I have verified that it builds with 4.12. Upstream issue.

@RyanGlScott
Copy link

There is now a vector-binary-instances-2.5 on Hackage which supports base-4.12.

@athas
Copy link
Author

athas commented Oct 3, 2018

Yes, thanks for that! I guess bumping the older versions is redundant now.

@athas athas closed this as completed Oct 3, 2018
@hvr
Copy link
Contributor

hvr commented Oct 3, 2018

@bgamari @RyanGlScott next time please be more careful and avoid making unnecessary releases when a revision would have been more appropriate; see http://hdiff.luite.com/cgit/vector-binary-instances/diff?id=0.2.5&id2=0.2.4

@bgamari
Copy link

bgamari commented Oct 14, 2018

This was wholly my fault. I could have sworn there were testsuite changes in that release but it seems there weren't.

However, I do wonder whether there is some way to improve the ergonomics of revisions. hackage-cli is a start, but it makes revisions feel very much like a second-class citizen, forcing maintainers to have two completely separate workflows for revisions and releases (e.g., see https://github.com/bgamari/hs-maintainer-tools). As long as this is the case it seems like there will naturally be a gravitation towards the more powerful of the two; afterall, humans are fallible and, at times, lazy.

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