-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Clarify checkpoint deprecation message #4640
Clarify checkpoint deprecation message #4640
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4640 +/- ##
=======================================
+ Coverage 90% 93% +3%
=======================================
Files 117 117
Lines 9011 9011
=======================================
+ Hits 8134 8384 +250
+ Misses 877 627 -250 |
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.
thanks @edenlightning
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.
so it shall be 1.1 milestone, right?
Co-authored-by: Adrian Wälchli <aedu.waelchli@gmail.com>
I don't think so. This is not a feature. Why shouldn't it be in 1.0.7? |
then the msg does not fit as you say deprecate in 1.1 but you want to release it before 1.1... in such case, we shall rephrase it as deprecated in 1.0.7 and removed in 1.2 |
Well this is already in 1.0.5? #4336 If so I guess it should be 1.0.5. Altough maybe not super elegant to add deprecations is patch releases :0 |
Make the deprecation message of checkpoint_callback arg clearer. Follow up to #4461