[PATCH] update version number everywhere it's needed

Nicolas Sebrecht nicolas.s-dev at laposte.net
Mon Dec 13 18:44:18 GMT 2010

On 12/13/2010 12:25 PM, Nicolas Sebrecht wrote:

> The release number information is hard coded. Here is a quick fix to update it
> to the last release.
> We may introduce more elaborated stuff to define the release dynamically.

FYI: not sure if you all saw it or changed it, but there were three
places I always changed for each new release:


in particular, the value in version.py must match the value in the
offlineimap(.py) file that someone uses to start the thing up.

Reported-by: Mark Plaksin <happy at usg.edu>
Reported-by: John Goerzen <jgoerzen at complete.org>
Signed-off-by: Nicolas Sebrecht <nicolas.s-dev at laposte.net>

	Thanks John. May I ask why you duplicated this information 3 times? Is there
	any logic behind?

 bin/offlineimap        |    2 +-
 offlineimap/version.py |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/bin/offlineimap b/bin/offlineimap
index 420ddb0..46cd481 100755
--- a/bin/offlineimap
+++ b/bin/offlineimap
@@ -20,4 +20,4 @@
 from offlineimap import OfflineImap
 offlineimap = OfflineImap()
diff --git a/offlineimap/version.py b/offlineimap/version.py
index 6ae95fc..045b56b 100644
--- a/offlineimap/version.py
+++ b/offlineimap/version.py
@@ -1,5 +1,5 @@
 productname = 'OfflineIMAP'
-versionstr = "6.2.0"
+versionstr = "6.3.1"
 versionlist = versionstr.split(".")
 major = versionlist[0]

More information about the OfflineIMAP-project mailing list