c2c-oerpscenario team mailing list archive

[Phong Nguyen <681241@xxxxxxxxxxxxxxxxxx>]

Hello,

I'm talking about the development phase where there are lots of check-in
to the trunk, and regression errors are introduced while keeping up with
the latest revision in trunk: one day it works, the next day it doesn't
(after merging from the trunk), and cannot identify what revision (in
the trunk) causes failures.

I think the author(s) will be responsible for the version/revision
number, base on his/her code control tools. If openerp-server is
developed mainly in bzr/launchpad, I think it should have revno from
bzr.

-- 
Include bzr revno in version string in the log file
https://bugs.launchpad.net/bugs/681241
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: New

Bug description:
The current version number shown in the log file of server doesn't contain the repository number (e.g revno from bzr), making it hard to isolate regression bugs between versions, especially during development and test/fix cycle

[2010-11-23 06:14:25,080][?] INFO:server:OpenERP version - 6.0.0-rc1

should be 

[2010-11-23 06:14:25,080][?] INFO:server:OpenERP version - 6.0.0-rc1 (rev 3037)