]> git.notmuchmail.org Git - notmuch/commitdiff
Increment notmuch version to 0.4.
authorCarl Worth <cworth@cworth.org>
Mon, 1 Nov 2010 23:16:03 +0000 (16:16 -0700)
committerCarl Worth <cworth@cworth.org>
Mon, 1 Nov 2010 23:16:03 +0000 (16:16 -0700)
As reminded in the RELEASING instructions, the correct version is 0.4,
not 0.4.0, so update this in the NEWS file as well.

NEWS
RELEASING
version

diff --git a/NEWS b/NEWS
index 92abb3db06c93346177bf701e012b75e5ba2d8e2..db437d312bd634aa1ab86ffc9c8732f2fc9e1dba 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,5 @@
-Notmuch 0.4.0 (2010-11-01)
-==========================
+Notmuch 0.4 (2010-11-01)
+========================
 New command-line features
 -------------------------
 notmuch search --output=(summary|threads|messages|tags|files)
index e9cb3d0bfbe2040dcf46a4edcee1f6086ebb6ef2..6c714f8e48a691ab8ae32fd7ecd22c3e71f52439 100644 (file)
--- a/RELEASING
+++ b/RELEASING
@@ -48,10 +48,10 @@ repository. From here, there are just a few steps to release:
        as "1.1" or "1.2").
 
        Finally, releases that do not change "features" but are merely
-       bug fixes either add increase the micro number or add it
-       (starting at ".1" if not present). So a bug-fix release from
-       "1.0" would be "1.0.1" and a subsequent bug-fix release would
-       be "1.0.2" etc.
+       bug fixes either increase the micro number or add it (starting
+       at ".1" if not present). So a bug-fix release from "1.0" would
+       be "1.0.1" and a subsequent bug-fix release would be "1.0.2"
+       etc.
 
        Commit this change.
 
diff --git a/version b/version
index 9e11b32fcaa96816319e5d0dcff9fb2873f04061..bd73f47072b1fe4b9914ec14a7f6d47fcc8f816a 100644 (file)
--- a/version
+++ b/version
@@ -1 +1 @@
-0.3.1
+0.4