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

Timeline for V2 #14

Closed
jacoscaz opened this issue Nov 14, 2024 · 6 comments
Closed

Timeline for V2 #14

jacoscaz opened this issue Nov 14, 2024 · 6 comments

Comments

@jacoscaz
Copy link

Hi! Is there any timeframe for the upgrade of this package to abstract-level@2.x, such as what recently happened with classic-level and memory-level?

This is by no means an attempt to pressure anyone into any kind of commitment nor a request for anyone to put in the necessary work. I'm simply wondering whether the upgrade is already in someone's todo list or whether it's still up for grab with no known plan to work on it for the foreseeable future.

Thanks again for all the wonderful work @vweevers and all maintainers!

@vweevers
Copy link
Member

I started on it a while back but I ended up yak shaving (e.g. fixing bugs in the test runner rather than any code here) and that messed with my motivation. I'll get back on that horse (or yak) in December. Shouldn't take long.

@jacoscaz
Copy link
Author

@vweevers thank you for both the fast feedback and for taking on V2! I was about to close this issue but then figured it might be useful to others looking for the same thing. Feel free to close it, though, if you believe otherwise.

Once again, no rush meant or implied. As a downstream consumer, I'm very grateful for all the work happening in the /Level organization.

@vweevers
Copy link
Member

#16

@jacoscaz
Copy link
Author

jacoscaz commented Dec 1, 2024

I'll get back on that horse (or yak) in December.

I'm very impressed by the accuracy of this estimate. Thank you so much @vweevers ! I'll start updating quadstore to abstract-level@2.x later in the week and will report back.

vweevers added a commit that referenced this issue Dec 1, 2024
@vweevers
Copy link
Member

vweevers commented Dec 1, 2024

Released 2.0.0.

@vweevers vweevers closed this as completed Dec 1, 2024
@jacoscaz
Copy link
Author

jacoscaz commented Dec 2, 2024

Upgrading on my end turned out to be much much much simpler than expected. Performance not only did not worsen but actually improved slightly! Thanks again @vweevers!

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

2 participants