### Avoiding permanent beta

From Kubernetes 1.20 onwards, SIG Architecture will implement a new policy to transition all REST APIs out of beta within nine months. The idea behind the new policy is to avoid features staying in beta for a long time. Once a new API enters beta, it will have nine months to either:

 - reach GA, and deprecate the beta, or
 - have a new beta version _(and deprecate the previous beta)_.

For details on best practices with 2.0, see
[the Effective 2.0 guide](https://www.tensorflow.org/beta/guide/effective_tf2)

For information on upgrading your existing TensorFlow 1.x models, please refer
to our
[Upgrade](https://medium.com/tensorflow/upgrading-your-code-to-tensorflow-2-0-f72c3a4d83b5)
and [Migration](https://www.tensorflow.org/beta/guide/migration_guide) guides.
We have also released a collection of

337B          ; mapped                 ; 5E73 6210     # 1.1  SQUARE ERA NAME HEISEI
337C          ; mapped                 ; 662D 548C     # 1.1  SQUARE ERA NAME SYOUWA
337D          ; mapped                 ; 5927 6B63     # 1.1  SQUARE ERA NAME TAISYOU
337E          ; mapped                 ; 660E 6CBB     # 1.1  SQUARE ERA NAME MEIZI
337F          ; mapped                 ; 682A 5F0F 4F1A 793E #1.1 SQUARE CORPORATION

is **compatibility** with Pydantic v1 and v2, to make sure your current apps keep working. Later there will be more focus on refactors, correctness, code improvements, and then **performance** improvements. Some third-party early beta testers that ran benchmarks on the beta releases of FastAPI reported improvements of **2x - 3x**. Which is not bad for just doing `pip install --upgrade fastapi pydantic`. This was not an official benchmark and I didn't check it myself, but it's a good sign.

###...