aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2022-04-29 16:55:25 -0700
committerSean Whitton <spwhitton@spwhitton.name>2022-04-29 16:55:25 -0700
commitced6aa80e71c20b60dc1a802e3f664669db14bd3 (patch)
tree2237a5218ece613a0a8d542019257154d1aa1d18 /doc
parent76774b9f37d4bd7b94147b7c1eb02d6528a8c7f7 (diff)
downloadconsfigurator-ced6aa80e71c20b60dc1a802e3f664669db14bd3.tar.gz
update news.rst for 1.0.0 release
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'doc')
-rw-r--r--doc/news.rst8
1 files changed, 2 insertions, 6 deletions
diff --git a/doc/news.rst b/doc/news.rst
index 5a498da..81733a3 100644
--- a/doc/news.rst
+++ b/doc/news.rst
@@ -1,17 +1,13 @@
News
====
-Some user-visible changes in versions of Consfigurator >1.0.0 are documented
-here. Version numbers have three components, ``major.minor.patch``, with the
-following semantics:
+Some user-visible changes are documented here. Version numbers have three
+components, ``major.minor.patch``, with the following semantics:
- we increment ``major`` for a release which contains particularly significant
new features, enhancements and/or reworkings, whether or not upgrading to
the release will require changes to user consfigs (though usually it will);
- + Additionally, while ``major`` is zero, we will be much more willing to
- make breaking changes.
-
- we increment ``minor`` for a release which does not satisfy the requirements
for incrementing ``major``, but where there are changes that could require
changes in user consfigs, except very obscure such consfigs; and