File 5453-Document-what-will-become-mandatory-in-OTP-26.patch of Package erlang

From 079a439af48797a3517e3d52a0a8edcaf93c9f64 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= <bjorn@erlang.org>
Date: Mon, 21 Jun 2021 09:47:22 +0200
Subject: [PATCH 3/3] Document what will become mandatory in OTP 26

This information is copied with edits from "Schedule for Removal"
page.
---
 .../upcoming_incompatibilities.xml            | 28 +++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/system/doc/general_info/upcoming_incompatibilities.xml b/system/doc/general_info/upcoming_incompatibilities.xml
index 7ee52b9c72..02b9c35bda 100644
--- a/system/doc/general_info/upcoming_incompatibilities.xml
+++ b/system/doc/general_info/upcoming_incompatibilities.xml
@@ -65,4 +65,32 @@
       </taglist>
     </section>
   </section>
+
+  <section>
+    <title>OTP 26</title>
+    <section>
+      <title>The distribution flag DFLAG_V4_NC will become mandatory</title>
+      <p>As of OTP 26, the distribution flag <seeguide
+      marker="erts:erl_dist_protocol#DFLAG_V4_NC">DFLAG_V4_NC</seeguide>
+      will become mandatory. If you implement the Erlang distribution
+      protocol yourself, you will need to implement support for
+      <c>DFLAG_V4_NC</c> in order to communicate with Erlang nodes
+      running OTP 26.</p>
+    </section>
+
+    <section>
+      <title>The new link protocol will become mandatory</title>
+      <p>
+	As of OTP 26, the <seeguide
+	marker="erts:erl_dist_protocol#new_link_protocol">new link
+	protocol</seeguide> will become mandatory. That is, Erlang
+	nodes will then refuse to connect to nodes not implementing
+	the new link protocol. If you implement the Erlang
+	distribution yourself, you are, however, encouraged to
+	implement the new link protocol as soon as possible since the
+	old protocol can cause links to enter an inconsistent state.
+      </p>
+    </section>
+
+  </section>
 </chapter>
-- 
2.26.2