Addons 1.x Roadmap

[seanpmorgan]

Opening this to start discussion on what core issues we need to address before considering bumping the major version of Addons to 1.x. There is no requirement to do this within any timeline, and if we feel that the repository is not ready then it is my strong belief that it's better to stay as a 0.x given the implied semantics of a semver increase.

Requirements:

• Remove all private TF APIs as seen in the allow lists of source_contron_tests Remove all elements from allowlists in source_code_test.py #1735
• Make optimizer wrappers consistant Make API for custom optimizer wrappers more consistent  #2187
• Ensure serialization compatibility for all Addons. Standardize all optimizer serialization checks #1747 addresses the optimizers.
• Unify any duplication functions across the ecosystem. As Wrong Implementation for 'random_cutout' #2384 mentions if there is duplication we should try our best to unify them
• Monitor the health of our maintainers. PR prototype Codeowners latest activity #2024

Nice to Haves:

• Unified sub-package testing Unified Sub-package Testing #992
• Align typing with exported TF types Align Typing with Exported TF Types #1997

We should update this list accordingly with any other requirements / nice to haves.

[seanpmorgan]

TensorFlow Addons is transitioning to a minimal maintenance and release mode. New features will not be added to this repository. For more information, please see our public messaging on this decision:
TensorFlow Addons Wind Down

Please consider sending feature requests / contributions to other repositories in the TF community with a similar charters to TFA:
Keras
Keras-CV
Keras-NLP