summaryrefslogtreecommitdiff
path: root/version
AgeCommit message (Collapse)Author
2014-05-06version: bump to 0.18David Bremner
debian changelog to be done seperately.
2014-05-04version: bump for 0.18~rc1David Bremner
Doing all of the needed version bumps in one commit, and do a complete, if minimal debian changelog entry
2014-04-22version: bump to 0.18~rc0David Bremner
Start the promised feature freeze
2013-12-30version: bump to 0.17David Bremner
2013-12-28version: bump to 0.17~rc4David Bremner
Unfortunately release-checks.sh will whine a bit because it has not caught up with the renaming of the version macros.
2013-12-07version: bump versionDavid Bremner
Roll (one last?) release candidate because of Austin's LIBNOTMUCH_VERSION changes. Atomically bump the manually (NEWS, debian/changelog) and automatically (everywhere else) updated places version is mentioned.
2013-11-28version: bump to 0.17~rc2David Bremner
2013-11-23version: bump to 0.17~rc1David Bremner
Various other files are synched using "make update-versions". NEWS has to be hand edited.
2013-07-28version: set new version and release dateDavid Bremner
These are manually set in version and NEWS, and propagate to the other files via "make update-versions"
2013-02-17bump versions to 0.15.20.15.2David Bremner
2013-01-24version: bump to 0.15.1David Bremner
A simple bugfix release, no user visible changes
2013-01-18version: update to 0.15debian/0.15-10.15David Bremner
Bump the version in-place in NEWS.
2013-01-16version: set version to 0.15~rc1David Bremner
This is in some sense a rollback, but it makes all the automation happier if the Debian and upstream versions match.
2013-01-07version: bump to 0.15David Bremner
"Atomically" update the python bindings and man page versions.
2012-08-20version: bump primary versionDavid Bremner
The date for man pages is taken from the last commit, so in this case it makes sense to do this in two commits.
2012-06-02version: update to 0.13.2David Bremner
2012-05-25version: bump to 0.13.1David Bremner
2012-05-15version: bump to 0.13David Bremner
2012-05-08bump version to 0.13~rc1debian/0.13_rc1-10.13_rc1David Bremner
2012-03-19update version to 0.12David Bremner
There may be a few NEWS changes after this, but no code (hopefully).
2012-03-18bump version to 0.12~rc2David Bremner
2012-03-01bump version to 0.12~rc1David Bremner
As usual, only `version' is edited by hand. The rest of the changes I blame on the machine.
2012-02-03version: bump to 0.11.1David Bremner
also semi-automatically update man page and python bindings versions.
2012-01-13Update version to 0.11David Bremner
2012-01-09version: update to 0.11~rc3debian/0.11_rc3-10.11_rc3David Bremner
We found another serious-ish bug during freeze.
2012-01-02version: bump to 0.11~rc2David Bremner
This to "celebrate" pushing a bugfix in at the last minute.
2011-12-25version: update version to 0.11~rc1debian/0.11_rc1-10.11_rc1David Bremner
and keep python, man page, and debian package in sync.
2011-12-05version: bump for bugfix release 0.10.2David Bremner
2011-11-25version: update to 0.10.1David Bremner
2011-11-23version: update to 0.10David Bremner
2011-11-19version: update version info for 0.10~rc2debian/0.10_rc2-10.10_rc2David Bremner
Arguably editing debian/changelog violates the "do one thing at a time" rule, but all of these versions need to be kept in sync.
2011-11-15version: update to 0.10~rc1David Bremner
and the usual dance with the python bindings version.
2011-10-11version: bump to 0.9David Bremner
also bump python bindings version.
2011-10-07version: bump to 0.9~rc2David Bremner
We continue to keep the python bindings version in sync manually
2011-09-24version: bump to 0.9~rc1David Bremner
This version number change should not be taken as definitive, rather refer to the signed tag.
2011-09-10update versions for release 0.8David Bremner
See commit 6979b65 for more discussion.
2011-09-06update versions for release candidate0.8_rc1David Bremner
we now have three files to keep in sync. That seems wrong, but I guess we will live with it for now. The main problem is that the python code is distributed separately, so it can't get the version from 'version'. The choice ~rcX is for convenience with debian versioning.
2011-08-01version: bump to 0.7David Bremner
No actual changes since 0.7~rc1
2011-07-29bump upstream version to 0.7~rc1David Bremner
2011-07-17version: bump to 0.6.1David Bremner
2011-07-01version: bump to 0.60.6David Bremner
The release machinery in the build system depends on this file being correct.
2010-11-11Increment notmuch version to 0.5Carl Worth
The big change here is the support for maildir-flag synchronization. But there are a number of other thigns as well---library support for multiple filenames, new ruby bindings, improvements to the vim interface, and a few tweaks to the emacs interface.
2010-11-01Increment notmuch version to 0.4.Carl Worth
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.
2010-04-27Increment version to 0.3.1Carl Worth
For our 0.3.1 bug-fix release.
2010-04-27Increment package version to 0.3.Carl Worth
For the 0.3 release, of course.
2010-04-16Increment version to 0.2.Carl Worth
Only minor features added this time--nothing that merits a 1.0.
2010-04-16Makefile: Add an explicit version file to the repository.Carl Worth
We do this so that "git archive" produces a usable tar file without us having to post-modify it, (since tools like git-buildpackage might not give us an easy way to hook into the tar-file-creation step). To support this we also have to change our preference to prefer the git-described-based version (if available) and only if not available do we fallback to using what's in the "version" file. Finally, we also ovverride this preference when releasing, (where what's in the "version" file wins). Note that using our Makefile's rule to create a tar file still will insert the git-based version into the tar file. This is useful for creating snapshots which will correctly report the git version from which they were created.