Item1198: configure extension installer reports all extension rev numbers wrong

Priority:	CurrentState:	AppliesTo:	Component:	WaitingFor:
Urgent	Closed	Engine

All the default plugins and all the plugins you have just installed a minute ago are out of date and needs upgrading according to configure

Something is goofed up.

Release blocker.

-- KennethLavrsen - 04 Mar 2009

Duplicate of Item1055, the fix for which broke it even worse.

We need to change EXTENSIONS.pm to scrape the extension topic for %$VERSION% instead of using $VERSION.

-- CrawfordCurrie - 04 Mar 2009

Actually need to do a bit more than that, as described in ReleaseNumbering

-- CrawfordCurrie - 05 Mar 2009

OK, here's what I have done:

1. configure now scrapes the version number from the topic, and is tolerant of version expressed as SVN revision numbers, triples (1.2.3), ISO dates and dd Mmmm yyyy format dates.
2. BuildContrib now computes the SVN rev number and date correctly
3. BuildContrib now supports %$RELEASE% for expansion of $RELEASE in extension topics (this is the route for 1.2.3 to get in)
4. Fixed the extension topics that had grown extra dates, due to a misunderstanding of how it all works

-- CrawfordCurrie - 05 Mar 2009

Related: Item1604.

-- MichaelDaum - 05 Mar 2009

Table colors and table headers have got lost in these changes. re-applied.

-- ArthurClemens - 07 Mar 2009