Bumped the version.

CHANGES.rst

@@ -1,3 +1,9 @@
+Revision 7.1.0, released on Sep 11, 2024
+----------------------------------------
+
+- Removed pyasn1.compat dependency.
+- Switched to async DNS resolver.
+
 Revision 7.0.3, released on Aug 26, 2024
 ----------------------------------------
 
@@ -50,6 +56,11 @@ Revision 7.0.1, released on Aug 24, 2024
 
 - Cherry-picked many minor fixes from etingof/master branch.
 
+Revision 6.2.6, released on Sep 11, 2024
+----------------------------------------
+
+- Removed pyasn1.compat dependency. A helper release to enable migration.
+
 Revision 6.2.5, released on Aug 10, 2024
 ----------------------------------------
 
@@ -82,8 +93,13 @@ Revision 6.2.0, released on Jul 12, 2024
 
 - Retired temporary sync API.
 
-Revision 6.1.3, released on July 16, 2024
------------------------------------------
+Revision 6.1.4, released on Sep 11, 2024
+----------------------------------------
+
+- Removed pyasn1.compat dependency. A helper release to enable migration.
+
+Revision 6.1.3, released on Jul 16, 2024
+----------------------------------------
 
 - Removed package postfix. A helper release to enable migration.
 

docs/source/conf.py

@@ -65,9 +65,9 @@
 # built documents.
 #
 # The short X.Y version.
-version = "7.0"
+version = "7.1"
 # The full version, including alpha/beta/rc tags.
-release = "7.0.3"
+release = "7.1.0"
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

docs/source/index.rst

@@ -19,7 +19,7 @@ multilingual capabilities, remote configuration and other features.
 PySNMP implementation closely follows intricate system details and features
 bringing most possible power and flexibility to its users.
 
-Current PySNMP stable version is 7.0. It runs with Python 3.8+
+Current PySNMP stable version is 7.1. It runs with Python 3.8+
 and is recommended for new applications as well as for migration from
 older, now obsolete, PySNMP releases. All site documentation and
 examples are written for the 6.0 and later versions in mind.

docs/source/upgrade.rst

@@ -6,7 +6,7 @@ Upgrade to 6.x/7.x Releases
 .. toctree::
    :maxdepth: 2
 
-This article provides information on how to upgrade to the latest 6.x/7.0
+This article provides information on how to upgrade to the latest 6.x/7.x
 releases from old releases such as 4.x and 5.x.
 
 .. note::
@@ -169,11 +169,11 @@ above.
 
 .. important::
 
-   We only published 6.1.3 release, and we are not planning to publish any
-   more 6.1 releases. The 6.1.3 release was published to ensure smooth
+   We only published releases >=6.1.3, and we are not planning to publish
+   any more 6.1 releases. Those releases were published to ensure smooth
    transition for users who are still using the 4.x/5.x/6.0 releases.
 
-   We consider the 6.1.3 release as a stepping stone to the 6.2 releases,
+   We consider those releases as a stepping stone to the 6.2 releases,
    so please don't stay with them for long.
 
 Upgrade to 6.2 Releases
@@ -184,7 +184,7 @@ we decided to remove it from 6.2 release.
 
 .. important::
 
-   We published release >=6.2.2, and we are not planning to publish any
+   We published releases >=6.2.2, and we are not planning to publish any
    older 6.2 releases. The new 6.2 releases were published to ensure smooth
    transition for users who are still using the 4.x/5.x/6.0/6.1 releases.
 
@@ -201,6 +201,13 @@ standards in 7.0 release.
    releases should carefully review the changes and adjust their code
    accordingly.
 
+Upgrade to 7.1 Releases
+-----------------------
+
+Switching to async DNS resolver forced us to make some changes to the API,
+so instead of using simply ``UdpTransportTarget()`` now you need to call
+```await UdpTransportTarget.create()``.
+
 Important Changes
 -----------------
 
@@ -229,6 +236,9 @@ We were hoping the new sync API would be stable enough to meet the quality
 expectation, but it turned out to be the opposite. So we decided to remove
 it from 6.2 release.
 
+You might copy the sync wrappers from 6.1 release and use them in your code
+if you still need them.
+
 RFC3414 Compliance
 ++++++++++++++++++