-
Notifications
You must be signed in to change notification settings - Fork 301
Update to 0.23.1 to prepare a release #1593
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
Conversation
Since we removed IgniteDataset which is a major change after 0.23.0, technically it qualifies another minor release instead of a 0.23.1 patch release. (And we need a fix for TF 2.8, see 1591). Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yongtang since the minor release is quite immediate, people might not have planned for the ignite deprecation (just in case if someone is using it). Shall we restore ignite and just release a patch version instead? We can remove ignite later. WDYT?
@kvignesh1420 The PR has been updated. Also please see #1594 for revert of ignite removal. |
Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
09d27a8
to
afd583d
Compare
@kvignesh1420 PR has been updated. Please take a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @yongtang
Binary candidates:
|
Since we removed IgniteDataset which is a major change after
0.23.0, technically it qualifies another minor release instead
of a 0.23.1 patch release. (And we need a fix for TF 2.8, see #1591).
Signed-off-by: Yong Tang yong.tang.github@outlook.com