mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 10:58:10 +01:00
Increment notmuch version to 0.4.
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.
This commit is contained in:
parent
4dd066ae6c
commit
efee51ba75
3 changed files with 7 additions and 7 deletions
4
NEWS
4
NEWS
|
@ -1,5 +1,5 @@
|
||||||
Notmuch 0.4.0 (2010-11-01)
|
Notmuch 0.4 (2010-11-01)
|
||||||
==========================
|
========================
|
||||||
New command-line features
|
New command-line features
|
||||||
-------------------------
|
-------------------------
|
||||||
notmuch search --output=(summary|threads|messages|tags|files)
|
notmuch search --output=(summary|threads|messages|tags|files)
|
||||||
|
|
|
@ -48,10 +48,10 @@ repository. From here, there are just a few steps to release:
|
||||||
as "1.1" or "1.2").
|
as "1.1" or "1.2").
|
||||||
|
|
||||||
Finally, releases that do not change "features" but are merely
|
Finally, releases that do not change "features" but are merely
|
||||||
bug fixes either add increase the micro number or add it
|
bug fixes either increase the micro number or add it (starting
|
||||||
(starting at ".1" if not present). So a bug-fix release from
|
at ".1" if not present). So a bug-fix release from "1.0" would
|
||||||
"1.0" would be "1.0.1" and a subsequent bug-fix release would
|
be "1.0.1" and a subsequent bug-fix release would be "1.0.2"
|
||||||
be "1.0.2" etc.
|
etc.
|
||||||
|
|
||||||
Commit this change.
|
Commit this change.
|
||||||
|
|
||||||
|
|
2
version
2
version
|
@ -1 +1 @@
|
||||||
0.3.1
|
0.4
|
||||||
|
|
Loading…
Reference in a new issue