-
Notifications
You must be signed in to change notification settings - Fork 125
RLS: 0.2.0 #74
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
Comments
Sure. I can try to make a release. I've opened a new issue to track the recent build failures. Note: This not a regression in |
@jreback I'm stuck at step |
@parthea you should be good to go to upload to PyPi (then trigger conda-forge). pls check docs after as well. Note that we want travis to be passing before releases. you can xfail these tests until they are fixed / worked around. These were very recently working. So it is odd. |
I restarted the builds on travis and now the 0.2.0 release is passing https://travis-ci.org/pydata/pandas-gbq/builds/256746482 . I'll submit a separate PR to xfail the intermittent test while we look into issue #75. I've published 0.2.0 on PyPi and submitted a pull request on conda-forge. Please take a look. While reviewing the 0.2.0 docs, I noticed that the change log in the docs has a formatting error which has been fixed on master in 0b25a6b. Should I fix the formatting error in the docs for the 0.2.0 release, and delete and re-create the 0.2.0 tag? |
just push a new commit to fix docs you can NEVER change a release tag |
thanks @parthea let's xfail those flakey tests until fixed. |
if you want to send out a release note to the mailing this would be great (completely optional here), something like this: (and then put a link in the wiki): https://github.com/pandas-dev/pandas/wiki/Release-Checklist |
@parthea can you do this release?
whatsnew needs updating to the date of the release and otherwise follow the release-procedure.
also some things failing which :<
https://travis-ci.org/pydata/pandas-gbq/builds/256434923
The text was updated successfully, but these errors were encountered: