neos team mailing list archive

[Johannes Wettinger <revager@xxxxxxxxxxxxxx>]

I think we can just use the 'bzr' command, i.e. '<exec executable="bzr"
outputproperty="revno">'. This should be a platform-independet solution
because after you installed bazaar, the binaries will be registered in
the environment path variable automatically. IMHO we should not
introduce distinctions between different platforms where it is not
necessarily needed. ;-)

I like Daniel's suggestion to find a way to split the bazaar-dependent stuff from the dist & release targets. Maybe we can just add a target called 'bzr-newrelease' which updates the build number inside the appResources.properties file and after that calls the 'release' target.
Inside the 'release' target we should update the date inside the appResources.properties file as well.

Besides of that, I suggest to insert a new property called
'vcsRepository' into the appResources.properties file. This property in
our case holds the bazaar branch URL like 'lp:revager/1.2', so we can
include this information in the About screen.

What do you think about these suggestions?

-- 
(FR) Build number and release date should be obtained automatically
https://bugs.launchpad.net/bugs/497927
You received this bug notification because you are a member of Team
N.E.O.S., which is the registrant for RevAger.

Status in RevAger: New

Bug description:
We should find a way to automatically integrate the current build number from the VCS (i.e. using "bzr revno", but a solution which does not depend on the bzr binary would be even better) and the current date (should be rather simple) dynamically into the build script, that is, without relying on resources/appResources.properties. This would simplify bug tracking from development builds. Since these strings are currently updated rather rarely, "Help->About" often reports incorrect information.