Commit 86d3e9eb by Wenzel Jakob

begin working towards a future v2.6.1 patch release

parent 59a2ac27
...@@ -6,6 +6,11 @@ Changelog ...@@ -6,6 +6,11 @@ Changelog
Starting with version 1.8.0, pybind11 releases use a `semantic versioning Starting with version 1.8.0, pybind11 releases use a `semantic versioning
<http://semver.org>`_ policy. <http://semver.org>`_ policy.
v2.6.1 (TBA, not yet released)
------------------------------
* Details to follow here
v2.6.0 (Oct 21, 2020) v2.6.0 (Oct 21, 2020)
--------------------- ---------------------
......
...@@ -53,7 +53,7 @@ To release a new version of pybind11: ...@@ -53,7 +53,7 @@ To release a new version of pybind11:
- Get back to work - Get back to work
- Make sure you are on master, not somewhere else: ``git checkout master`` - Make sure you are on master, not somewhere else: ``git checkout master``
- Update version macros in ``include/pybind11/common.h`` (set PATCH to - Update version macros in ``include/pybind11/detail/common.h`` (set PATCH to
``0.dev1`` and increment MINOR). ``0.dev1`` and increment MINOR).
- Update ``_version.py`` to match - Update ``_version.py`` to match
- Add a plot for in-development updates in ``docs/changelog.rst``. - Add a plot for in-development updates in ``docs/changelog.rst``.
......
...@@ -11,7 +11,7 @@ ...@@ -11,7 +11,7 @@
#define PYBIND11_VERSION_MAJOR 2 #define PYBIND11_VERSION_MAJOR 2
#define PYBIND11_VERSION_MINOR 6 #define PYBIND11_VERSION_MINOR 6
#define PYBIND11_VERSION_PATCH 0 #define PYBIND11_VERSION_PATCH 1.dev1
#define PYBIND11_NAMESPACE_BEGIN(name) namespace name { #define PYBIND11_NAMESPACE_BEGIN(name) namespace name {
#define PYBIND11_NAMESPACE_END(name) } #define PYBIND11_NAMESPACE_END(name) }
......
...@@ -8,5 +8,5 @@ def _to_int(s): ...@@ -8,5 +8,5 @@ def _to_int(s):
return s return s
__version__ = "2.6.0" __version__ = "2.6.1.dev1"
version_info = tuple(_to_int(s) for s in __version__.split(".")) version_info = tuple(_to_int(s) for s in __version__.split("."))
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment