Update migration strategy #2156
Conversation
|
|
||
| **Given the challenges of external SIG coordinating with internal roadmaps, a new | ||
| process has been put in place for the core TF and Keras teams to handle migration | ||
| and deprecation of Addons components. If you believe there is a strong candidate for |
There was a problem hiding this comment.
I think the real problem here is about expecting a deprecation PR.
I think it is plausible to expect this if we have a "real" migration approach but instead it will be very hard if we have a duplicative process in the "ecosystem".
When you start to duplicate something it is hard to expect that you will care about a deprecation cause probably in the duplication act implicitly you didn't care about checking in the ecosystem.
It is not totally correlated cause there could be real cases when you are constrained to reinvent the wheel but I suppose there is a very strong relationship between the duplication behaviour and the lack of deprecation activities.
There was a problem hiding this comment.
Just to make a pratical use case:
#2004 (comment)
Description
Updates the migration strategy.
cc @dynamicwebpaige @karmel @tomerk @tanzhenyu