-
Notifications
You must be signed in to change notification settings - Fork 67
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
Release v0.5 #342
Comments
Yes, this is still an important fix, imo. I think the plan you've suggested on those issues sounds appropriate. |
Awesome @nkeim! Thank you for taking the time to do this.
About my PR #320: all the work is basically done. It is just about properly documenting it in the release notes. Should I add it to #345 ? |
That's right. |
Hi @nkeim I just wanted to check in with you: what is the status of this? I think most of the points are done? Do you think we're ready for a release? |
Yes, I think we are ready to go! Sorry I haven't been able to spend much time on this in the past few weeks. I put a draft of the release instructions in the wiki, based on the process for the most recent trackpy release. @rbnvrw do you want to take the lead on this? I'll have some time to help next week but probably not enough to make sure it happens. |
Update: v0.5 is available on PyPI! I am still waiting for the conda-forge bot to act on this. I’m headed to bed and if it hasn’t happened by morning, I’ll take care of it manually. Stay tuned… |
I think we're done! The conda-forge package is built and should be in the channel momentarily. Thanks especially to @GenevieveBuckley , @tacaswell , @jakirkham , @rbnvrw , and @caspervdw for their assistance. Please let me know if anything looks amiss! This wiki page is based on the trackpy instructions and will hopefully let any maintainer carry out a release in the future. |
Thanks @nkeim! 😄 |
Yes, thanks! |
Awesome, thank you @nkeim 🥇 |
Thanks for getting this done @nkeim! |
This is great, thank you! |
pims v0.4.1 was released in 2017. Support for some formats, especially still images, continues to work great in that release, but there have been many improvements, bug fixes, and high-profile API changes since then, most notably a fix for PyAV support.
I'm creating this thread to help us (maintainers and contributors) decide what minimally needs to be done, and what decisions must be made before we can proceed with a release. Actually doing a release and documenting the procedure again will make it easier to do minor releases as more work is done.
Here's what I see as the key steps:
There are other PRs that are worth attention but are probably not ready for a timely release:
open
handleslist
s correctly #316 is likewise worthwhile but needs some work. I suggest we leave it out.Note that I am not (yet) volunteering to do this release! I just want us to start by getting organized. Please comment on this plan — what am I missing?
The text was updated successfully, but these errors were encountered: