> Am 27.08.2023 um 14:40 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>:
> 
> Hi P.O.,
> 
> first of all thank you very much for all of your efforts in midst of your 
> vacation far away from your IT infrastructure!
> 
> 
No problem, but I cannot do all things from remote so some things may have to 
wait a month or so.
> ---
> 
> One problem is probably that we have not done another release since the last 
> time where we had quite a few new scripts built to support the release 
> process. One such little tool is in docs/trunk/tools and named 
> "updateEntityValues.rex", the "readme.txt" in that directory gives brief 
> infos on the different utilities and how to use them. 
> 
Does this mean that the build process for the documentation needs to be 
modified? It did work impeccably until 5.0.0 was released, since then I have 
not touched it. I will check the above, currently the documentation build is a 
pure shell script on macOS.
> We probably should kick a new release (5.0.1?) to re-acquaint ourselves again 
> and update the release documentation steps if necessary!
> 
> 

I can not contribute until November at the earliest. And we should agree on a 
procedure before that, based on the list that Rick started at 5.0.0.
> ---rony
> 
> 
@Rony: can you explain what the printed information below actually means? 
Should something be changed whenever a commit is made (i.e. before the 
documentation is built)? That must be made by the committer I assume?
> 
> On 27.08.2023 13:38, oorexx wrote:
>> Dear all,
>> 
>> At the moment the building of the documentation is manually triggered, since 
>> Jenkins cannot find SVN on the build machine (it is there and works, unclear 
>> why Jenkins does not detect it). When making the latest documentation I 
>> noticed the following ooRexx build levels:
>> 
>> 12722 for ooRexx itself      (This is the current version)
>> 12723 for ooRexx TestGroups
>> 
>> 12728 for Rexxref.pdf
>> 12715 for Winextensions.pdf
>> 12643 for RexxExtensions.pdf
>> 
>> However, when I look at the built documentation I see this information:
>> 
>> rexxref
>> ooRexx Documentation 5.1.0 Open Object Rexx Reference Edition 2023.01.01 
>> (last revised on 20221024 with r12526)
>> 
>> winextensions
>> ooRexx Documentation 5.1.0 Open Object Rexx Windows Extensions Reference 
>> Edition 2023.01.01 (last revised on 20220524 with r12416)
>> 
>> rexxextensions
>> ooRexx Documentation 5.1.0 Open Object Rexx
>> Rexx Extensions Library Reference
>> Edition 2023.01.01 (last revised on 20220619 with r12444)
>> 
>> i.e. it seems the build revision is not reflected in the edition 
>> information? Is this as it should be or does something need to be changed?
>> 
>> If someone intends to work on the documentation please trigger manually a 
>> build of the documentation in Jenkins, or, if you do not now hoot, send me a 
>> mail and I will do it.
>> 
>> PS I am on leave and check my mail sparingly so there might be delays.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se <mailto:oor...@jonases.se>
>> 
> 
> _______________________________________________
> 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