[docs] Commented out 2.20.3 (#22282)

* removed 2.20.3 * removed from stable
yugabyte · May 6, 2024 · 787ce95 · 787ce95
1 parent eb9e3da
commit 787ce95
Show file tree

Hide file tree

Showing 6 changed files with 14 additions and 10 deletions.
diff --git a/docs/content/preview/reference/configuration/operating-systems.md b/docs/content/preview/reference/configuration/operating-systems.md
@@ -27,7 +27,7 @@ Unless otherwise noted, operating systems are supported by all supported version
 | Oracle Linux 8         | {{<icon/yes>}} |                | |
 | Red Hat Enterprise Linux 7 | {{<icon/yes>}} |      | Deprecated in v2.20.0; not supported in v2.21.0.0 release and [upcoming release series](../../../releases/#upcoming-release-series) |
 | Red Hat Enterprise Linux 8 | {{<icon/yes>}} |      | Recommended for production |
-| Red Hat Enterprise Linux&nbsp;9.3 | {{<icon/yes>}} |  | v2.20.3 and later<br>Recommended for production |
+<!-- | Red Hat Enterprise Linux&nbsp;9.3 | {{<icon/yes>}} |  | v2.20.3 and later<br>Recommended for production | -->
 | SUSE Linux Enterprise Server 15 SP5 | {{<icon/yes>}} |     | {{<badge/ea>}} |
 | Ubuntu 18        | {{<icon/yes>}} | {{<icon/yes>}} | Deprecated in v2.20.0; not supported in v2.21.0.0 release and [upcoming release series](../../../releases/#upcoming-release-series) |
 | Ubuntu 20        | {{<icon/yes>}} | {{<icon/yes>}} |       |

diff --git a/docs/content/preview/releases/yba-releases/v2.20.md b/docs/content/preview/releases/yba-releases/v2.20.md
@@ -55,7 +55,7 @@ For more information, see [#20827](https://github.com/yugabyte/yugabyte-db/issue
 
 {{< /warning >}}
 
-## v2.20.3.0 - April 9, 2024 {#v2.20.3.0}
+<!-- ## v2.20.3.0 - April 9, 2024 {#v2.20.3.0}
 
 **Build:** `2.20.3.0-b68`
 
@@ -161,7 +161,7 @@ For more information, see [#20827](https://github.com/yugabyte/yugabyte-db/issue
 * Upgrades the yba-installer to PostgreSQL version 14.11. PLAT-12878
 * Corrects the retrieval of autoflags from the target universe, ensuring tserver autoflags, not master autoflags, are compared during backup procedures. PLAT-13161
 * Prevents universe chain upgrade failure from 2.0 to 2.18 and 2.20 by ensuring the clock-script doesn't run during yb-process start command if it's not present or executable. PLAT-13444
-* Prevents 'Edit Universe' modal from wrongly displaying master placement as 'Place Masters on the same nodes as T-Servers' for a dedicated universe, providing accurate universe creation details. PLAT-13445
+* Prevents 'Edit Universe' modal from wrongly displaying master placement as 'Place Masters on the same nodes as T-Servers' for a dedicated universe, providing accurate universe creation details. PLAT-13445 -->
 
 ## v2.20.2.2 - April 1, 2024 {#v2.20.2.2}
 

diff --git a/docs/content/preview/releases/ybdb-releases/v2.20.md b/docs/content/preview/releases/ybdb-releases/v2.20.md
@@ -37,7 +37,7 @@ For an RSS feed of all release series to track the latest product updates, point
 
 {{< /warning >}}
 
-## v2.20.3.0 - April 9, 2024 {#v2.20.3.0}
+<!-- ## v2.20.3.0 - April 9, 2024 {#v2.20.3.0}
 
 **Build:** `2.20.3.0-b68`
 
@@ -155,7 +155,7 @@ docker pull yugabytedb/yugabyte:2.20.3.0-b68
 #### Other
 
 * Updates the condition for HT lease reporting to ensure accurate leaderless tablet detection in RF-1 setup, preventing false alarms. {{<issue 20919>}}
-* Reduces disruptions by throttling the master process log messages related to "tablet server has a pending delete" into 20-second intervals. {{<issue 19331>}}
+* Reduces disruptions by throttling the master process log messages related to "tablet server has a pending delete" into 20-second intervals. {{<issue 19331>}} -->
 
 
 ## v2.20.2.2 - April 1, 2024 {#v2.20.2.2}

diff --git a/...ontent/preview/yugabyte-platform/manage-deployments/upgrade-software-install.md b/...ontent/preview/yugabyte-platform/manage-deployments/upgrade-software-install.md
@@ -14,7 +14,8 @@ type: docs
 
 YugabyteDB is a distributed database that can be installed on multiple nodes. Upgrades happen in-place with minimal impact on availability and performance. This is achieved using a rolling upgrade, where each node is upgraded one at a time. YugabyteDB [automatically re-balances](../../../explore/linear-scalability/data-distribution/) the universe as nodes are taken down and brought back up during the upgrade.
 
-If you have issues after upgrading a universe, you can roll back in-place and restore the universe to its state before the upgrade. Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later.
+If you have issues after upgrading a universe, you can roll back in-place and restore the universe to its state before the upgrade.
+<!-- Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later. -->
 
 ## View and import releases
 
@@ -54,7 +55,8 @@ You upgrade a universe in the following phases:
 
 - Upgrade - Update the nodes in the universe to the new database version.
 - Monitor - Evaluate the performance and functioning of the new version.
-- Rollback - If you encounter any issues while monitoring the universe, you have the option to roll back in-place and restore the universe to its state before the upgrade. (Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later.)
+- Rollback - If you encounter any issues while monitoring the universe, you have the option to roll back in-place and restore the universe to its state before the upgrade.
+<!-- (Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later.) -->
 - Finalize - Depending on the changes included in the upgrade, you may need to finalize the upgrade to make the upgrade permanent. The system will tell you if this step is necessary. After finalizing, you can no longer roll back.
 
 ### Perform the upgrade

diff --git a/docs/content/stable/reference/configuration/operating-systems.md b/docs/content/stable/reference/configuration/operating-systems.md
@@ -27,7 +27,7 @@ Unless otherwise noted, operating systems are supported by all supported version
 | Oracle 8         | {{<icon/yes>}} |                | |
 | Red Hat Enterprise Linux 7 | {{<icon/yes>}} |      |       |
 | Red Hat Enterprise Linux 8 | {{<icon/yes>}} |      | Recommended for production |
-| Red Hat Enterprise Linux&nbsp;9.3 | {{<icon/yes>}} |  | v2.20.3 and later<br>Recommended for production |
+<!-- | Red Hat Enterprise Linux&nbsp;9.3 | {{<icon/yes>}} |  | v2.20.3 and later<br>Recommended for production | -->
 | SUSE Linux Enterprise Server 15 SP5 | {{<icon/yes>}} |     | {{<badge/ea>}} |
 | Ubuntu 18        | {{<icon/yes>}} | {{<icon/yes>}} | Deprecated in v2.20.0 |
 | Ubuntu 20        | {{<icon/yes>}} | {{<icon/yes>}} |       |

diff --git a/...content/stable/yugabyte-platform/manage-deployments/upgrade-software-install.md b/...content/stable/yugabyte-platform/manage-deployments/upgrade-software-install.md
@@ -14,7 +14,8 @@ type: docs
 
 YugabyteDB is a distributed database that can be installed on multiple nodes. Upgrades happen in-place with minimal impact on availability and performance. This is achieved using a rolling upgrade, where each node is upgraded one at a time. YugabyteDB [automatically re-balances](../../../explore/linear-scalability/data-distribution/) the universe as nodes are taken down and brought back up during the upgrade.
 
-If you have issues after upgrading a universe, you can roll back in-place and restore the universe to its state before the upgrade. Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later.
+If you have issues after upgrading a universe, you can roll back in-place and restore the universe to its state before the upgrade.
+<!-- Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later. -->
 
 ## View and import releases
 
@@ -54,7 +55,8 @@ You upgrade a universe in the following phases:
 
 - Upgrade - Update the nodes in the universe to the new database version.
 - Monitor - Evaluate the performance and functioning of the new version.
-- Rollback - If you encounter any issues while monitoring the universe, you have the option to roll back in-place and restore the universe to its state before the upgrade. (Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later.)
+- Rollback - If you encounter any issues while monitoring the universe, you have the option to roll back in-place and restore the universe to its state before the upgrade.
+<!-- (Roll back is available for universes being upgraded from YugabyteDB version 2.20.3 and later.) -->
 - Finalize - Depending on the changes included in the upgrade, you may need to finalize the upgrade to make the upgrade permanent. The system will tell you if this step is necessary. After finalizing, you can no longer roll back.
 
 ### Perform the upgrade