- 5.1.0 branches for docs, test and main have been created and committed.
- main/trunk has been adjusted to 5.2.0 according to release-steps.md
- Sourceforge trackers received a mileston 5.2.0 (and by default set to it from
now on)
---
There are the following (minor) problems currently:
* the uploading of created installers does not goes to
<https://sourceforge.net/projects/oorexx/files/oorexx/5.1.0beta/> instead of
<https://sourceforge.net/projects/oorexx/files/oorexx/5.1.0_Release_Candidate/>
* it seems that the 5.1.0 release candidate documentation is not uploaded to
SourceForge, should
go to
<https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.1.0_Release_Candidate/>
* the test unit fails for the following testcase
[failure] 20250502 12:30:36.509000
Test: TESTVERSION01
Class: METHOD.testGroup
File: ...\ooRexx\API\oo\METHOD.testGroup
Line: 2113
Failed: assertSame
Expected: 00050100
Actual: 00050200
the reason being that the METHOD.testGroup uses METHODPackage.cls, which
uses the native
orxmethod library to check the ooRexx version number against it. It seems that the
"orxmethod"
library that gets used is the one of trunk which now has a version number of
"5.2.0", where the
built version of the ooRexx interpreter from branches/5.1.0 reports "5.1.0".
Assuming that the setup at Jenkins points to the trunk versions of the
native libraries used for
the testunit. Hence one would have to adjust the library locations to the
version created by
"branches/5.1.0".
Will create a standalone version of "main/branches/5.1.0" and run the "test/branches/5.1.0" test
suite against it.
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
