Item4480: Better handling of VERSION

The Foswiki VERSION is currently unreliable, because it reflects the number of the last checkin of Foswiki.pm, and not the last checkin of anything. It would be better to have a VERSION.pm that was automatically updated by the subversion post-commit script, so it always reflects the state of the latest checkin to lib, bin, tools etc.

Sven also suggested that all modules should have their own $VERSION = '$Id: Item4480.txt,v 1.10 2009/03/08 07:13:51 CrawfordCurrie Exp $', which is an excellent idea to help with support.

-- Foswiki:Main/CrawfordCurrie - 22 Aug 2007

What we really want to do is to get the latest version number into a file that can be read by Foswiki.pm (and anything else that wants the version number). That file could easily be checked in, and then updated by the build script. So we might as well modify TWiki.pm, and replace $Rev$ in that file with the latest (global) rev from the repository. But what we really want is a file that is updated on an svn update, so that those of us running in checkout areas can see what rev we are running. That means a checkin. But we can't do a checkin without incrementing the revision number, so we end up with an extra checkin for every checkin - yuck.

Note that to do Sven's idea will require svn propset svn:keywords on every code file.

CC

For now, made the cron job on trunk.foswiki.org auto-edit the rev number into the release name

CC

This subject has re-opened in ReleaseNumbering, and is applicable to all modules, not just the main build.

---

Fixed this in Foswiki. The build engine checks the latest rev of all files in the MANIFEST.

-- CrawfordCurrie - 08 Mar 2009