| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
There may be a few NEWS changes after this, but no code (hopefully).
|
| |
|
|
|
|
|
| |
As usual, only `version' is edited by hand. The rest of the changes I
blame on the machine.
|
|
|
|
| |
also semi-automatically update man page and python bindings versions.
|
| |
|
|
|
|
| |
We found another serious-ish bug during freeze.
|
|
|
|
| |
This to "celebrate" pushing a bugfix in at the last minute.
|
|
|
|
| |
and keep python, man page, and debian package in sync.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Arguably editing debian/changelog violates the "do one thing at a
time" rule, but all of these versions need to be kept in sync.
|
|
|
|
| |
and the usual dance with the python bindings version.
|
|
|
|
| |
also bump python bindings version.
|
|
|
|
| |
We continue to keep the python bindings version in sync manually
|
|
|
|
|
| |
This version number change should not be taken as definitive, rather
refer to the signed tag.
|
|
|
|
| |
See commit 6979b65 for more discussion.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
Importing the notmuch module in setup.py is a no-no, and we want
to auto-generate the version number in the release process.
Outsource __VERSION__ to the new version.py which contains nothing else
and which can therefor easily be autogenerated. Have setup.py read in
the file via execfile and test if importing the version number actually
worked.
This should make all happy.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|