aboutsummaryrefslogtreecommitdiffhomepage
path: root/bindings/python/notmuch/version.py
Commit message (Collapse)AuthorAge
* bump versions to 0.15.2Gravatar David Bremner2013-02-17
|
* version: bump to 0.15.1Gravatar David Bremner2013-01-24
| | | | A simple bugfix release, no user visible changes
* version: update to 0.15Gravatar David Bremner2013-01-18
| | | | Bump the version in-place in NEWS.
* version: set version to 0.15~rc1Gravatar David Bremner2013-01-16
| | | | | This is in some sense a rollback, but it makes all the automation happier if the Debian and upstream versions match.
* version: bump to 0.15Gravatar David Bremner2013-01-07
| | | | "Atomically" update the python bindings and man page versions.
* version: propagate version changesGravatar David Bremner2012-08-21
| | | | These are the result of running "make update-versions"
* version: update to 0.13.2Gravatar David Bremner2012-06-02
|
* version: bump to 0.13.1Gravatar David Bremner2012-05-25
|
* version: bump to 0.13Gravatar David Bremner2012-05-15
|
* bump version to 0.13~rc1Gravatar David Bremner2012-05-08
|
* update version to 0.12Gravatar David Bremner2012-03-19
| | | | There may be a few NEWS changes after this, but no code (hopefully).
* bump version to 0.12~rc2Gravatar David Bremner2012-03-18
|
* bump version to 0.12~rc1Gravatar David Bremner2012-03-01
| | | | | As usual, only `version' is edited by hand. The rest of the changes I blame on the machine.
* version: bump to 0.11.1Gravatar David Bremner2012-02-03
| | | | also semi-automatically update man page and python bindings versions.
* Update version to 0.11Gravatar David Bremner2012-01-13
|
* version: update to 0.11~rc3Gravatar David Bremner2012-01-09
| | | | We found another serious-ish bug during freeze.
* version: bump to 0.11~rc2Gravatar David Bremner2012-01-02
| | | | This to "celebrate" pushing a bugfix in at the last minute.
* version: update version to 0.11~rc1Gravatar David Bremner2011-12-25
| | | | and keep python, man page, and debian package in sync.
* version: bump for bugfix release 0.10.2Gravatar David Bremner2011-12-05
|
* version: update to 0.10.1Gravatar David Bremner2011-11-25
|
* version: update to 0.10Gravatar David Bremner2011-11-23
|
* version: update version info for 0.10~rc2Gravatar David Bremner2011-11-19
| | | | | Arguably editing debian/changelog violates the "do one thing at a time" rule, but all of these versions need to be kept in sync.
* version: update to 0.10~rc1Gravatar David Bremner2011-11-15
| | | | and the usual dance with the python bindings version.
* version: bump to 0.9Gravatar David Bremner2011-10-11
| | | | also bump python bindings version.
* version: bump to 0.9~rc2Gravatar David Bremner2011-10-07
| | | | We continue to keep the python bindings version in sync manually
* version: bump to 0.9~rc1Gravatar David Bremner2011-09-24
| | | | | This version number change should not be taken as definitive, rather refer to the signed tag.
* update versions for release 0.8Gravatar David Bremner2011-09-10
| | | | See commit 6979b65 for more discussion.
* update versions for release candidateGravatar David Bremner2011-09-06
| | | | | | | | | | 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.
* python: Have setup.py read the version number without importingGravatar Sebastian Spaeth2011-08-24
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>
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-20 13:06:27 +0000