GitLab/Gitk: Module Version / OS Version

Hello, how can I find out which version of a module a particular OS version was released with?

I can see git tags on the kernel and modules, and I can see the OS version in Kernel.Version, but how do I know which ones went together in a release?

You want to look at the different repos in the Products group: https://gitlab.riscosopen.org/Products

Each product will have a tag for each of the stable releases of that product. Checking out the tag should also check out the correct submodule versions for that release.

You’ll still need to work out how to map the commit hash of each submodule to a version number / tag – chances are someone can work out how to write a shell script to do that.

Hello, how can I find out which version of a module a particular OS version was released with?

An alternative is to look here.

Chris, do you have a time line of RISC OS 5 releases?

Jeffrey, I can click on the commit for each tag on a product and it gives me a list of all the submodule versions that got changed — this takes me back to about 2008 / RISC OS 5.13 on Tungsten, which is pretty good.

I suppose for before that I’ll have to make my best guess based on commit dates.

Chris, do you have a time line of RISC OS 5 releases?

Let’s hope this doesn’t fool textile. It was part of my contribution to the BASIC manual. And probably needs bringing up to date.

BASIC V and BASIC VI continued to be developed as the hardware platforms developed. The improvements in each version are described below but the timeline is given below so that the version numbers can be tied to the various hardware platforms. Where features are described in this manual that are not present in all versions of BASIC V and BASIC VI (i.e. were added after version 1.05) then they will be so marked.

The Acorn Archimedes was launched in June 1987 and by 1992 was available in several models including the A400 series (with an ARM 3 processor), the A3000 series (with an ARM250 processor) and the portable A4 (with an ARM3 preocessor). All of these contained RISC OS 3.10 and BASIC version 1.05 (10-Apr-1992) on which issue 1 of the BBC BASIC Reference Manual was based, published in October 1992. The principal hardware developments that followed are described below – these are complicated by the fact that BASIC was developed in two forks from version 1.20, reaching version 1.36 in the RISC OS Limited fork before that line of development became defunct.

Development of RISC OS 3 reached 3.70/3.71 in 1996 which included StrongARM compatability, but there was little change in BASIC functionality between version 1.06 (RISC OS 3.50), 1.16 (RISC OS 3.70) and 1.19 (RISC OS 4.02). Some development took place under the ‘Select’ scheme (mostly, if not exclusively, confined to bug fixes) up to version 1.34 (06-Oct-2004) (RISC OS 4.42). Meanwhile development was taking place, in parallel, for the Iyonix computer, which was released with version 1.34 (02-Dec-2002) (RISC OS 5.01).

Whilst the changes at each version are described in some detail below, there are good reasons to review how developments between 1999 (RISC OS 4.02 and 4.03) and 2002 (RISC OS 4.33 and RISC OS 5.01) took place, if only to retain clarity between the Select fork and the Castle fork. Up to version 1.19, the version number of BASIC is unambiguous. After that point it is clearer to say ‘requires RISC OS 5’ or ‘requires RISC OS 5.19 (18-Sep-2012) or later’ or ‘requires RISC OS 5.20 or later’. In each case these are equivalent to requiring at least version 1.34 (02-Dec-2002), 1.53 (18-Sep-2012) and 1.54 (27-Apr-2013) respectively but avoid confusion with Select developments.

The Iyonix computer contains a ‘flash ROM’ allowing a simple route to apply free updates and most users will have updated to at least RISC OS 5.16 which contained version 1.44 (16-Jun-2009). Other platforms (such as Beagleboard, Pandaboard, IGEPv5, ARMX6, Titanium and Raspberry Pi) will also be at least at version 5.21. Developments in the Select fork beyond RISC OS 4.42 (BASIC version 1.34) are not covered further.

Wow!

Peter Howkins’ database has been useful also to cross-check Module/OS from times long since passed.