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

tensorflow-io 0.8.0 release #459

Closed
6 tasks done
BryanCutler opened this issue Aug 27, 2019 · 9 comments · Fixed by #472
Closed
6 tasks done

tensorflow-io 0.8.0 release #459

BryanCutler opened this issue Aug 27, 2019 · 9 comments · Fixed by #472

Comments

@BryanCutler
Copy link
Member

BryanCutler commented Aug 27, 2019

This is to start the planning for the release of 0.8.0 for tensorflow-io.

Here is the list of items for 0.8.0:

  • Fix test errors in tf-nightly failure cases #431
  • Update the version in setup.py
  • Update README.md to add additional supported ops since 0.7.0
  • Update RELEASE.md to capture 0.8.0 changes and version compatibility.
  • Push *.whl files to PyPI.org, including macOS package.
  • Release R package to CRAN (optionally).

/cc @yongtang @terrytangyuan @dmitrievanthony

@BryanCutler
Copy link
Member Author

Just wanted to get the discussion started for timing. I know there are lots of changes going in right now with the new IOTensor ops, and also the upcoming release of TensorFlow 1.15.0. It would be good to get down what is left to do so we can make a 0.8.0 release soon after TF 1.15.0 is out.

@yongtang
Copy link
Member

yongtang commented Sep 8, 2019

Created a branch R0.8, and PR #470 as a working-in-progress. The tensorflow==1.15.0 was supposed to be rebased last month though it looks like there is some delay. So we may have to wait.

In the meantime, we are switching master and nightly build to use tensorflow==2.0.0rc0, but keep R0.8 branch to use tf-nightly (latest version was from 08/21).

@yongtang
Copy link
Member

The new PR is in #472

@BryanCutler
Copy link
Member Author

I think we need to fix the test errors in #431 before release also

@yongtang
Copy link
Member

As tensorflow/tensorflow#33263 has been merged, I expect that TensorFlow 1.15.0 to be released in a couple of days (Monday or Tuesday).

We are good with PR #472 and is pretty ready for our v0.8.0 release.

@yongtang
Copy link
Member

yongtang commented Oct 17, 2019

All tests pass now. The candidate wheel files for 0.8.0 release are located in (Note build number 1990):

https://www.dropbox.com/home/Apps/tensorflow-io-nightly/release/1990/wheelhouse

Will do some testing, if everything is fine, will label v0.8.0 release then push to PyPI.org (likely this afternoon).

@BryanCutler
Copy link
Member Author

great, thanks for all your hard work @yongtang !

@yongtang
Copy link
Member

Tested on Ubuntu 16.04 and 18.04, all works fine (python 2.7, 3.5, 3.6, 3.7). Below are the related wheel files:

5a4a70ad39e3147b20ac40b5c22dca9064f350e70774bd93e4a343e1b65617e4  tensorflow_io-0.8.0-cp27-cp27m-macosx_10_13_x86_64.whl
45ba91020b248181181ffa7d218e91791baef35e92936a78a4c6f4e5da5684e5  tensorflow_io-0.8.0-cp27-cp27mu-manylinux2010_x86_64.whl
f7bbccf9c06e8492f68808e5699c90134c984b165535ae5084e1a78d9942a51c  tensorflow_io-0.8.0-cp35-cp35m-macosx_10_13_x86_64.whl
adde23454f41608b2fc95fe4a1846958c9b7edd86f90b94085d0cc832556a36c  tensorflow_io-0.8.0-cp35-cp35m-manylinux2010_x86_64.whl
c4f99500ef3cdb6e4eeab8ccb7817a03c8bb001f6aa3d03e49e26efae64aacd8  tensorflow_io-0.8.0-cp36-cp36m-macosx_10_13_x86_64.whl
373d42c239d9da1b316062f647aea308e1360765a20a29f14c6fc63a3ee90340  tensorflow_io-0.8.0-cp36-cp36m-manylinux2010_x86_64.whl
521e248b03256f16b33297c3e2aba54462215bf42a80a98a1c258f699d983130  tensorflow_io-0.8.0-cp37-cp37m-manylinux2010_x86_64.whl

@yongtang
Copy link
Member

Version 0.8.0 released:
https://github.com/tensorflow/io/releases/tag/v0.8.0

https://pypi.org/project/tensorflow-io/0.8.0/

👍 🎉 🎆 , thanks all!

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

Successfully merging a pull request may close this issue.

2 participants