Merge pull request #57425 from tensorflow/vinila21-patch-1

vinila21 · web-flow · commit f5411e998c29 · 2022-08-24T12:09:24.000-07:00
Moving deprecation section
diff --git a/RELEASE.md b/RELEASE.md
@@ -9,6 +9,19 @@
     *   Both seeded and unseeded initializers will always generate the same values every time they are called (for a given variable shape). For unseeded initializers (`seed=None`), a random seed will be created and assigned at initializer creation (different initializer instances get different seeds).
     *   An unseeded initializer will raise a warning if it is reused (called) multiple times. This is because it would produce the same values each time, which may not be intended.
 
+
+## Deprecations
+
+*   The C++ `tensorflow::Code` and `tensorflow::Status` will become aliases of respectively `absl::StatusCode` and `absl::Status` in some future release.
+    *   Use `tensorflow::OkStatus()` instead of `tensorflow::Status::OK()`.
+    *   Stop constructing `Status` objects from `tensorflow::error::Code`.
+    *   One MUST NOT access `tensorflow::errors::Code` fields. Accessing `tensorflow::error::Code` fields is fine.
+        *   Use the constructors such as `tensorflow::errors:InvalidArgument` to create status using an error  code without accessing it.
+        *   Use the free functions such as `tensorflow::errors::IsInvalidArgument` if needed.
+        *   In the last resort, use e.g.`static_cast<tensorflow::errors::Code>(error::Code::INVALID_ARGUMENT)` or `static_cast<int>(code)` for comparisons.
+*   `tensorflow::StatusOr` will also become in the future alias to `absl::StatusOr`, so use `StatusOr::value` instead of `StatusOr::ConsumeValueOrDie`.
+
+
 ## Major Features and Improvements
 
 *   `tf.lite`:
@@ -87,18 +100,6 @@
 * `tf.random`
     * Added `tf.random.experimental.stateless_shuffle`, a stateless version of `tf.random.shuffle`.
 
-## Deprecations
-
-*   The C++ `tensorflow::Code` and `tensorflow::Status` will become aliases of respectively `absl::StatusCode` and `absl::Status` in some future release.
-    *   Use `tensorflow::OkStatus()` instead of `tensorflow::Status::OK()`.
-    *   Stop constructing `Status` objects from `tensorflow::error::Code`.
-    *   One MUST NOT access `tensorflow::errors::Code` fields. Accessing `tensorflow::error::Code` fields is fine.
-        *   Use the constructors such as `tensorflow::errors:InvalidArgument` to create status using an error  code without accessing it.
-        *   Use the free functions such as `tensorflow::errors::IsInvalidArgument` if needed.
-        *   In the last resort, use e.g.`static_cast<tensorflow::errors::Code>(error::Code::INVALID_ARGUMENT)` or `static_cast<int>(code)` for comparisons.
-*   `tensorflow::StatusOr` will also become in the future alias to `absl::StatusOr`, so use `StatusOr::value` instead of `StatusOr::ConsumeValueOrDie`.
-
-
 
 ## Thanks to our Contributors
 
