@@ -41,27 +41,8 @@ you're using any deprecated features and update your code accordingly.
4141By default, deprecation log messages are enabled at the `WARN` level.
4242
4343. Review the breaking changes for each product you use
44- and make the necessary changes so your code is compatible with {version}:
45- +
46- --
47- ** {beats-ref}/breaking-changes.html[Beats {version} breaking changes]
48- ** {apm-server-ref}/breaking-changes.html[APM Server {version} breaking changes]
49- ** {ref}/breaking-changes.html[Elasticsearch {version} breaking changes]
50- ** {hadoop-ref}/breaking-changes.html[Elasticsearch Hadoop {version} breaking changes]
51- ** {kibana-ref}/breaking-changes.html[Kibana {version} breaking changes]
52- ** {logstash-ref}/breaking-changes.html[Logstash {version} breaking changes]
53-
54- [IMPORTANT]
55- ===============================
56-
57- * If you're upgrading from 2.n, make sure you check the breaking changes from
58- 2.n to 5.n, as well as from 5.n to 6.n!
59- * If you are using {ml} {dfeeds} that contain discontinued search or query
60- domain specific language (DSL), the upgrade will fail. In 5.6.5 and later, the
61- Upgrade Assistant provides information about which {dfeeds} need to be updated.
62-
63- ===============================
64- --
44+ and make the necessary changes so your code is compatible with {version}. See
45+ <<elastic-stack-breaking-changes>>.
6546
6647. {ref}/docs-reindex.html[Reindex] or delete any indices created on 2.n. We recommend
6748upgrading to the most recent 5.6 and using the {xpack} Reindex Helper to reindex 2.n indices.
0 commit comments