summaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorUlf Magnusson <ulfalizer@gmail.com>2019-04-30 21:47:08 +0200
committerUlf Magnusson <ulfalizer@gmail.com>2019-04-30 22:36:58 +0200
commit9cd7a1932321c9b2ddbacde018740a824cd4ad9e (patch)
treee568f14454129d64ed1ed0787e3952d8c64f26ad /README.rst
parent4fed39d9271ceb68be4157ab3f96a45b94f77dc0 (diff)
Make 11.0.0 releasev11.0.0
Simplifies the filename calculation for .old files, in commit 4fed39d ("Never prepend '.' to $KCONFIG_CONFIG.old"). This makes it reliable to refer to the backup file as $KCONFIG_CONFIG.old in scripts. This is a backwards-incompatible change when $KCONFIG_CONFIG is set to a filename that does not start with a '.', so the major version is increased. Note that $KCONFIG_CONFIG is usually set to <some path>/.config, so few people should be affected.
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst9
1 files changed, 5 insertions, 4 deletions
diff --git a/README.rst b/README.rst
index 617699c..a51585c 100644
--- a/README.rst
+++ b/README.rst
@@ -93,19 +93,20 @@ available in the Python 2 version of the standard ``curses`` module.
that your ``PATH`` includes the directory where the executables end up. You can
list the installed files with ``pip(3) show -f kconfiglib``.
-All releases have a corresponding tag in the git repository, e.g. ``v10.51.0``
+All releases have a corresponding tag in the git repository, e.g. ``v11.0.0``
(the latest version).
`Semantic versioning <http://semver.org/>`_ is used. There's been
-eight small changes (`1 <https://github.com/ulfalizer/Kconfiglib/commit/e8b4ecb6ff6ccc1c7be0818314fbccda2ef2b2ee>`_,
+nine small changes (`1 <https://github.com/ulfalizer/Kconfiglib/commit/e8b4ecb6ff6ccc1c7be0818314fbccda2ef2b2ee>`_,
`2 <https://github.com/ulfalizer/Kconfiglib/commit/db633015a4d7b0ba1e882f665e191f350932b2af>`_,
`3 <https://github.com/ulfalizer/Kconfiglib/commit/8983f7eb297dd614faf0beee3129559bc8ba338e>`_,
`4 <https://github.com/ulfalizer/Kconfiglib/commit/cbf32e29a130d22bc734b7778e6304ac9df2a3e8>`_,
`5 <https://github.com/ulfalizer/Kconfiglib/commit/eb6c21a9b33a2d6e2bed9882d4f930d0cab2f03b>`_,
`6 <https://github.com/ulfalizer/Kconfiglib/commit/c19fc11355b13d75d97286402c7a933fb23d3b70>`_,
`7 <https://github.com/ulfalizer/Kconfiglib/commit/7a428aa415606820a44291f475248b08e3952c4b>`_,
-`8 <https://github.com/ulfalizer/Kconfiglib/commit/f247ddf618ad29718e5efd3e69f8baf75d4d347b>`_)
-to the behavior of the API, which is why the major version is at 10 rather than
+`8 <https://github.com/ulfalizer/Kconfiglib/commit/f247ddf618ad29718e5efd3e69f8baf75d4d347b>`_,
+`9 <https://github.com/ulfalizer/Kconfiglib/commit/4fed39d9271ceb68be4157ab3f96a45b94f77dc0>`_)
+to the behavior of the API, which is why the major version is at 11 rather than
2. I do major version bumps for all behavior changes, even tiny ones, and most of these were
fixes for baby issues in the early days of the Kconfiglib 2 API.