Messages files in submitted changes.

When submitting changes to apps; are you going to update the version string in the messages file on our behalf, or should we do it?

We will do that bit – it’s done by a tool that we use to check a component into cvs. This will hopefully be a bit more obvious when we have the released sources available on our cvs server.

Ticket 131 tracks the progress of fault (thanks for submitting that, James).

Erm, I’ve just downloaded the prebuilt batch one stuff and !CloseUp still shows a version number of 3.09 (15-Sep-94). According to cvs it should now be 3.12

I realise this is a pretty minor thing, but it could cause problems with tracking bugs.

There are a couple of areas where things can get temporarily out of sync: the first is the live cvs repository and the released archives of sources/binaries may not always match because we don’t (yet) have an automated way of updating one when the other is changed.

Another is the stuff you find in RISC OS 5.13 on the IYONIX may have different version numbers than the stuff we’ve released. That’s because we haven’t completed merging the latest sources from Castle into our source tree so some of our sources are a bit older. We should sort this out quite soon though (hopefully over the next week).

The CloseUp RunImage that I downloaded is definitely the 3.12 version, it’s just that the Message file doesn’t reflect this.

OK. I’ll get it fixed.