@@ -21,46 +21,22 @@ application to upgrade your driver to a new version.
21
21
22
22
Before you upgrade, perform the following actions:
23
23
24
- - Ensure the new version is compatible with the MongoDB server versions
24
+ - Ensure the new version is compatible with the {+mdb- server} versions
25
25
your application connects to and the Java Runtime Environment (JRE) your
26
26
application runs on. See the :ref:`Java Compatibility <java-compatibility-tables>`
27
27
page for this information.
28
28
- Address any breaking changes between the current version of the driver
29
29
your application is using and your planned upgrade version in the
30
- section on :ref:`Breaking Changes <java-breaking-changes>` below.
30
+ :ref:`Breaking Changes <java-breaking-changes>` section. To learn
31
+ more about the {+mdb-server+} release compatibility changes, see the
32
+ :ref:`<java-server-release-changes>` section.
31
33
32
34
.. tip::
33
35
34
36
To minimize the amount of changes your application may require when
35
37
upgrading driver versions in the future, use the
36
38
:ref:`{+stable-api+} <stable-api-java>`.
37
39
38
- .. _java-server-release-changes:
39
-
40
- Server Release Compatibility Changes
41
- ------------------------------------
42
-
43
- A server release compatibility change is a modification
44
- to the {+driver-long+} that discontinues support for a set of
45
- MongoDB server versions.
46
-
47
- To learn more about end-of-life MongoDB products,
48
- see the `Legacy Support Policy <https://www.mongodb.com/support-policy/legacy>`__.
49
-
50
- .. _java-server-release-change-v4.8:
51
-
52
- Version 4.8 Server Release Support Changes
53
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
54
-
55
- - The v4.8 driver drops support for MongoDB v3.4 and earlier.
56
- To use the v4.8 driver, your MongoDB server must be v3.6 or later. To learn
57
- how to upgrade your MongoDB server to v3.6, follow the link corresponding
58
- to your MongoDB configuration:
59
-
60
- - :ref:`<3.6-upgrade-replica-set>`
61
- - :ref:`<3.6-upgrade-standalone>`
62
- - :ref:`<3.6-upgrade-sharded-cluster>`
63
-
64
40
.. _java-breaking-changes:
65
41
66
42
Breaking Changes
@@ -76,6 +52,14 @@ changes between the current and upgrade versions. For example, if you
76
52
are upgrading the driver from v4.0 to v4.5, address all breaking changes from
77
53
the version after v4.0 including any listed under v4.5.
78
54
55
+ .. _java-breaking-changes-v4.8:
56
+
57
+ Version 4.8 Breaking Changes
58
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
59
+
60
+ - The driver ends support for connecting to {+mdb-server+} versions v3.4 and
61
+ earlier. To learn more about this change, see the :ref:`<java-server-release-change-v4.8>`
62
+ section.
79
63
80
64
.. _java-breaking-changes-v4.7:
81
65
@@ -148,3 +132,31 @@ Version 4.0 Breaking Changes
148
132
any classes that link to the driver against this version or later to ensure
149
133
that they continue to work.
150
134
135
+ .. _java-server-release-changes:
136
+
137
+ Server Release Compatibility Changes
138
+ ------------------------------------
139
+
140
+ A server release compatibility change is a modification
141
+ to the {+driver-long+} that discontinues support for a set of
142
+ {+mdb-server+} versions.
143
+
144
+ The driver discontinues support for a {+mdb-server+} version after it reaches
145
+ end-of-life (EOL).
146
+
147
+ To learn more about the MongoDB support for EOL products,
148
+ see the `Legacy Support Policy <https://www.mongodb.com/support-policy/legacy>`__.
149
+
150
+ .. _java-server-release-change-v4.8:
151
+
152
+ Version 4.8 Server Release Support Changes
153
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
154
+
155
+ - The v4.8 driver drops support for {+mdb-server+} v3.4 and earlier.
156
+ To use the v4.8 driver, your {+mdb-server+} must be v3.6 or later. To learn
157
+ how to upgrade your {+mdb-server+} to v3.6, follow the link that corresponds
158
+ to your MongoDB deployment configuration:
159
+
160
+ - :ref:`<3.6-upgrade-replica-set>`
161
+ - :ref:`<3.6-upgrade-standalone>`
162
+ - :ref:`<3.6-upgrade-sharded-cluster>`
0 commit comments