update version number everywhere it's needed
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: offlineimap.py bin/offlineimap offlineimap/version.py 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: John Goerzen <jgoerzen@complete.org> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
This commit is contained in:
parent
03ee2cd5b1
commit
1c106a4ce9
@ -20,4 +20,4 @@
|
||||
from offlineimap import OfflineImap
|
||||
|
||||
offlineimap = OfflineImap()
|
||||
offlineimap.startup('6.2.0')
|
||||
offlineimap.startup('6.3.1')
|
||||
|
@ -1,5 +1,5 @@
|
||||
productname = 'OfflineIMAP'
|
||||
versionstr = "6.2.0"
|
||||
versionstr = "6.3.1"
|
||||
|
||||
versionlist = versionstr.split(".")
|
||||
major = versionlist[0]
|
||||
|
Loading…
Reference in New Issue
Block a user