Hi Rony, I think that is a good idea, I do not know of any bugs/features that 
are that serious that they are show stoppers? Anyone?

I can help with managing the build system next week. I will finalise my work 
before then.

I propose that we set up the release candidate under /main/branches/5.1 rather 
than directly under /main/releases. If we are not happy with the RC we can just 
replace it. Also it can serve as the source for any 5.1.x releases later. When 
I look at the SVN tree this is what seems to have been the strategy in the 
past. There is a 4.3 in /main/branches that never reached the /main/releases 
for instance. Here is how it looks: 

main
├── branches
│   ├── 4.1
│   │   └── trunk
│   ├── 4.2
│   │   └── trunk
│   ├── 4.3-old
│   └── 5.0
│       └── trunk
├── releases
│   ├── 3.1.2
│   │   └── trunk
│   ├── 3.2.0
│   │   └── trunk
│   ├── 4.0.0
│   │   └── trunk
│   ├── 4.0.1
│   │   └── trunk
│   ├── 4.1.0
│   │   └── trunk
│   ├── 4.1.1
│   │   └── trunk
│   ├── 4.1.2
│   │   └── trunk
│   ├── 4.1.3
│   │   └── trunk
│   ├── 4.2.0
│   │   └── trunk
│   └── 5.0.0
│       └── trunk
├── sandbox
└── trunk

There is a /main/sandbox that is empty, is it allowed to put things in there? 
If so I could make a test before we go ahead. There is still the problem that 
the rexx -v reports the SVN version number of the release. I understand it 
should report something else (1?). Same goes for the naming of the built 
artifacts. Maybe this works if built under a different branch than trunk? 
Anyone with understanding of how this works is welcome to explain, this was not 
solved for the 5.0.0 release.

Hälsningar/Regards/Grüsse,
ooRexx
oor...@jonases.se



> Am 24.04.2025 um 19:13 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>:
> 
> Suggesting to prepare a general availability version for ooRexx 5.1.0 with 
> the aim to release it next week such that we have a new release for this 
> year's International Rexx symposium in Vienna. Any thaughts, comments?
> 
> ---rony
> 
> 
> 
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to