-
Notifications
You must be signed in to change notification settings - Fork 132
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.6.2 #748
Comments
Thanks @nkeim for opening this issue. It was indeed my intention to charge through to a release however I don’t think I can find to finish it anytime soon. |
Bumping this for @caspervdw : Any comments on #735 and #749 ? I think they are ready to merge, and I didn't hear back from the author of #735, so if they look OK to you, I think you can just do it. I would love to do the release the next time I get a chance! (Which will be at least a few days from now.) |
Thanks for reminding me @nkeim. The two PRs are merged so please feel free to tag and release |
Release candidate looks good! I will make the actual release at the next opportunity, possibly late next week. |
All done! Failing CI tests are a GitHub issue. See #755 . |
@caspervdw Thanks for taking care of those Pandas issues! I hope I'm not being too presumptuous by creating this issue.
Major next steps (mostly following the release checklist).
Were you thinking of doing the release? I ask because since doing 0.6 and 0.6.1 in succession, I've had a pretty good, partially-automated workflow for releases, following the steps on the wiki. So I am volunteering. BUT, it's unlikely I can do much until Monday Jan 15, so if you want to charge ahead with any or all of this, please do!
The text was updated successfully, but these errors were encountered: