notmuch.git - [no description]

	Commit message (Collapse)	Author	Age
*	version: bump for bugfix release 0.10.2	David Bremner	2011-12-05
\|
*	version: update to 0.10.1	David Bremner	2011-11-25
\|
*	version: update to 0.10	David Bremner	2011-11-23
\|
*	version: update version info for 0.10~rc2	David Bremner	2011-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~rc1	David Bremner	2011-11-15
\| \| \| \|	and the usual dance with the python bindings version.
*	version: bump to 0.9	David Bremner	2011-10-11
\| \| \| \|	also bump python bindings version.
*	version: bump to 0.9~rc2	David Bremner	2011-10-07
\| \| \| \|	We continue to keep the python bindings version in sync manually
*	version: bump to 0.9~rc1	David Bremner	2011-09-24
\| \| \| \| \|	This version number change should not be taken as definitive, rather refer to the signed tag.
*	update versions for release 0.8	David Bremner	2011-09-10
\| \| \| \|	See commit 6979b65 for more discussion.
*	update versions for release candidate	David Bremner	2011-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 importing	Sebastian Spaeth	2011-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>