Autobuilder fail?

I went to download the most recent nightly build for the Pi.
It seems to have stopped on the 5th of April…?
The Beagle, RiscPC, Iyonix, and Panda beta releases appear to be up to date.

Update: The RISC OS version present identifies itself as being from the 29th March.

The RISC OS version present identifies itself as being from the 29th March.

On my Pi the 5th of April ROM does own up to be just that, with *fx0.

The RPCEmu 20th of April ROM is 5.23!

The RPCEmu 20th of April ROM is 5.23!

As do all the images (except the Pi)
Presumably all changes from this point are to 5.23 and the frozen “5.21” with all fixes checked will be 5.22

Aha. Looks like RO 5.22 is going to be released at Wakefield.

I’m hoping that USBAudio will be in there.

Aha. Looks like RO 5.22 is going to be released at Wakefield.

That was my assumption

Build fixed. OS5.23 now on my RPi. Many thanks.

OS5.23 now on my RPi.

Does it have the USBAudio module?

Does it have the USBAudio module?

As of RISC OS 5.23 (22 Apr 2015), no.

P.S. Is USBAudio even in CVS?

Is USBAudio even in CVS?

I didn’t put it in CVS myself – I submitted the whole thing to ROOL via email. A subsequent conversation with Steve Revill confirmed that they had received it.

I didn’t put it in CVS myself

I did try a search of CVS and did not find USBAudio, but then it can be quite easy not to find things in CVS. Is USBAudio expected to be in the ROM or in !System? It’s not in either in the current OS5.23. I have not looked at RC14.

I think the product build/module files in CVS indicate what modules/versions are baked in. No sign of USBAudio.

In a completely non-critical way, it would be interesting to note any pending submissions, as maybe people can help review, merge and test. I appreciate it is quite an effort for ROOL to do this on their own.

Does Colin have LanMan fixes? USB? Any more on EDID?

I guess we have to be pragmatic. Official releases should be relatively mature, and there has to be a freeze at some point.

AIUI new software is not normally(never?) added to a ROM release that hasn’t been in the nightly builds!
The norm is I believe: Take a snapshot (Code Freeze) a while prior (a month or so?) and remove anything new that is known to have problems. Then test. Known bugs are not addressed but any bugs introduced are fixed or code reverted to the previous ‘release version’.
Sprow I’m sure can explain it better!

Well, yes, I would imagine something like that too. A ‘release’ should be akin to the kind of thing Acorn would have released, and people would have used by default. The minority who want the cutting-edge, that is, the last few months of development work, should either wait, or experiment with the nightly builds.

The minority who want the cutting-edge, that is, the last few months of development work, should either wait, or experiment with the nightly builds.

The purpose of the latter being to allow as many people as possible to run with the bleeding edge and test the developments.

The norm is I believe: Take a snapshot (Code Freeze) a while prior (a month or so?) and remove anything new that is known to have problems.

From the Iyonix :-

*FX0
RISC OS 5.22 (13 Apr 2015)
*help ScreenModes
==> Help on keyword ScreenModes
Module is: Screen Modes    0.38 (09 Mar 2014)

Commands provided:
LoadModeFile
*

*FX0
RISC OS 5.23 (22 Apr 2015)
*help ScreenModes
==> Help on keyword ScreenModes
Module is: Screen Modes    0.48 (24 Feb 2015)

Commands provided:
LoadModeFile    ReadEDID        CreateModeFile
*