RELEASING: Change wording of libnotmuch version instruction

We actually want this version to be incremented by the commits that
extend the interface. So the release process really is not to just
verify two things (NEWS and libnotmuch version), then run "make
VERSION=x.y release", and send the mail. Quite nice.
This commit is contained in:
Carl Worth 2010-04-15 20:50:46 -07:00
parent 00263dd1a9
commit a29f49b943

View file

@ -16,13 +16,16 @@ repository. From here, there are just a few steps to release:
not mentioned there. If so, pleas add them, (and ask the not mentioned there. If so, pleas add them, (and ask the
authors of the commits to update NEWS in the future). authors of the commits to update NEWS in the future).
2) Increment the libnotmuch library version in lib/Makefile.local 2) Verify that the library version in lib/Makefile.local is correct
See the instructions there for how to increment it. The See the instructions there for how to increment it.
command below can be useful for inspecting header-file changes
since the last release X.Y.Z:
git diff X.Y.Z..HEAD -- lib/notmuch.h The version should have been updated with any commits that
added API, but do check that that is the case. The command
below can be useful for inspecting header-file changes since
the last release X.Y:
git diff X.Y..HEAD -- lib/notmuch.h
Note: We currently don't plan to increment Note: We currently don't plan to increment
LIBNOTMUCH_VERSION_MAJOR beyond 1, so if there *are* LIBNOTMUCH_VERSION_MAJOR beyond 1, so if there *are*
@ -30,7 +33,7 @@ repository. From here, there are just a few steps to release:
stop. Don't release. Figure out the plan on the notmuch stop. Don't release. Figure out the plan on the notmuch
mailing list. mailing list.
Commit this change. Commit this change, if any.
3) Run "make VERSION=X.Y release" which will perform the following steps: 3) Run "make VERSION=X.Y release" which will perform the following steps: