debian/notmuch
1
0
Fork 0
mirror of https://git.notmuchmail.org/git/notmuch synced 2024-11-29 06:04:11 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
5620 commits 14 branches 412 tags 12 MiB
Commit graph

91 commits

Author SHA1 Message Date
David Bremner
6c9cd7d20c version: bump to 0.17~rc2 2013-11-28 21:00:52 -04:00
David Bremner
bd0c56b2bd version: bump to 0.17~rc1 
Various other files are synched using "make update-versions".  NEWS
has to be hand edited.
 2013-11-23 20:29:46 -04:00
David Bremner
80b25792b2 version: set new version and release date 
These are manually set in version and NEWS, and propagate to the other files via
"make update-versions"
 2013-07-28 11:28:03 -03:00
David Bremner
bcccc2e1fe bump versions to 0.15.2 2013-02-17 11:39:46 -04:00
David Bremner
d273ed6cf1 version: bump to 0.15.1 
A simple bugfix release, no user visible changes
 2013-01-24 07:11:27 -04:00
David Bremner
df9f50185c version: update to 0.15 
Bump the version in-place in NEWS.
 2013-01-18 21:27:57 -04:00
David Bremner
81866a82ad version: set version to 0.15~rc1 
This is in some sense a rollback, but it makes all the automation
happier if the Debian and upstream versions match.
 2013-01-16 23:23:00 -04:00
David Bremner
37be45767f version: bump to 0.15 
"Atomically" update the python bindings and man page versions.
 2013-01-07 21:38:20 -04:00
David Bremner
2bd02b68a5 version: bump primary version 
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-08-20 13:53:50 +02:00
David Bremner
9d5f73db7a version: update to 0.13.2 2012-06-02 18:10:55 -03:00
David Bremner
df96c93239 version: bump to 0.13.1 2012-05-25 21:17:54 -03:00
David Bremner
3fb08bc125 version: bump to 0.13 2012-05-15 18:18:45 -03:00
David Bremner
a4b10675bf bump version to 0.13~rc1 2012-05-08 14:49:08 -03:00
David Bremner
c302bfa2f6 update version to 0.12 
There may be a few NEWS changes after this, but no code (hopefully).
 2012-03-19 22:28:17 -03:00
David Bremner
d71cb5e45b bump version to 0.12~rc2 2012-03-18 08:07:00 -03:00
David Bremner
916aefc2de bump version to 0.12~rc1 
As usual, only `version' is edited by hand. The rest of the changes I
blame on the machine.
 2012-03-01 07:47:21 -04:00
David Bremner
c10b780b44 version: bump to 0.11.1 
also semi-automatically update man page and python bindings versions.
 2012-02-03 08:32:49 -04:00
David Bremner
9ada8335c6 Update version to 0.11 2012-01-13 19:58:36 -04:00
David Bremner
310608f279 version: update to 0.11~rc3 
We found another serious-ish bug during freeze.
 2012-01-09 07:05:40 -04:00
David Bremner
ff58a06e83 version: bump to 0.11~rc2 
This to "celebrate" pushing a bugfix in at the last minute.
 2012-01-02 06:50:07 -04:00
David Bremner
c616ada489 version: update version to 0.11~rc1 
and keep python, man page, and debian package in sync.
 2011-12-25 23:09:17 -04:00
David Bremner
d7276c6241 version: bump for bugfix release 0.10.2 2011-12-05 18:07:00 -04:00
David Bremner
f3ad20b20a version: update to 0.10.1 2011-11-25 12:11:04 -05:00
David Bremner
1915c14a3a version: update to 0.10 2011-11-23 07:37:02 -04:00
David Bremner
eb88cd977b version: update version info for 0.10~rc2 
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-19 08:24:30 -04:00
David Bremner
6b8fd9dd41 version: update to 0.10~rc1 
and the usual dance with the python bindings version.
 2011-11-15 19:46:08 -04:00
David Bremner
8603396861 version: bump to 0.9 
also bump python bindings version.
 2011-10-11 21:50:56 -03:00
David Bremner
af1dc7ef48 version: bump to 0.9~rc2 
We continue to keep the python bindings version in sync manually
 2011-10-07 22:42:18 -03:00
David Bremner
78d39a0908 version: bump to 0.9~rc1 
This version number change should not be taken as definitive, rather
refer to the signed tag.
 2011-09-24 20:00:29 -03:00
David Bremner
24fc8f97e8 update versions for release 0.8 
See commit 6979b65 for more discussion.
 2011-09-10 08:55:33 -03:00
David Bremner
6979b6533a update versions for release candidate 
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-09-06 22:55:01 -03:00
David Bremner
ef36eb794f version: bump to 0.7 
No actual changes since 0.7~rc1
 2011-08-01 21:18:03 +02:00
David Bremner
97d090c105 bump upstream version to 0.7~rc1 2011-07-29 17:22:42 +02:00
David Bremner
2b1b6df06f version: bump to 0.6.1 2011-07-17 10:59:08 -03:00
David Bremner
6bd02fb4db version: bump to 0.6 
The release machinery in the build system depends on this file
being correct.
 2011-07-01 15:28:16 -03:00
Carl Worth
1365ebf146 Increment notmuch version to 0.5 
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-11 20:43:56 -08:00
Carl Worth
efee51ba75 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.
 2010-11-01 16:16:03 -07:00
Carl Worth
774225b8b5 Increment version to 0.3.1 
For our 0.3.1 bug-fix release.
 2010-04-27 17:00:34 -07:00
Carl Worth
f12b1fe3c5 Increment package version to 0.3. 
For the 0.3 release, of course.
 2010-04-27 02:03:26 -07:00
Carl Worth
3461aa8dc2 Increment version to 0.2. 
Only minor features added this time--nothing that merits a 1.0.
 2010-04-16 13:02:34 -07:00
Carl Worth
b7dc24298d Makefile: Add an explicit version file to the repository. 
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.
 2010-04-16 11:34:48 -07:00