-
-
Notifications
You must be signed in to change notification settings - Fork 356
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
v2.19.0 release? #891
Comments
cc @dlqqq |
@krassowski (cc @jtpio @3coins) Thank you for calling this out! Yes, it has been a while since the last release, and I am also eager to provide users with these new features & bug fixes. I was planning to cut a release yesterday but got sick. Since it's generally good practice to avoid cutting releases on a Friday, let's plan for the next release to occur on Monday, July 15. This way, we'll be available from Monday onwards to cut patches if necessary. I would also like to close out #865 (and possibly #864 as well) before releasing. |
I agree with not releasing on Fridays! What do you think about an alpha today though? |
hey sorry to intrude, but could we sneak #856 in the next release as well? it is becoming a bit of a blocker. |
@michaelchia No problem! I've opened #897, which will be merged before the next release. |
v2.19.0 is released on PyPI! Working on the Conda Forge release now, which should be done within 8 hours. |
v2.19.0 is released on Conda Forge 🎉 |
Problem
Since the 2.18.1 release a couple of exciting new features were merged:
And even more bug fixes:
refreshCompleterState
on each render #875/learn
after change of embedding model #870-h/--help
#878It would be nice to have a new release or at least a new alpha to test things.
I see that the
2.19.0
milestone is past due by 3 days and still has six pending issues - do we want to wait for them or ship what is already there?Proposed Solution
Cut a new alpha.
Before the final version I would suggest considering fixing:
Additional context
v2.18.1
was released three weeks agoThe text was updated successfully, but these errors were encountered: