OK, that explains it.
+1
On 12/19/2022 11:57 AM, Rick McGuire wrote:
On Mon, Dec 19, 2022 at 11:54 AM Gilbert Barmwater
<gi...@bellsouth.net> wrote:
OK, I can see that but in looking at the 4.2.0 Rexx Ref. document,
I don't see them so I assumed they should go away. Totally agree
that they should come out of the trunk version.
We didn't start using them until Erich took over updating the docs in
5.0.0.
Rick
Gil
On 12/19/2022 10:22 AM, Rick McGuire wrote:
No, the flags should still be there. Those are for the benefit of
anybody making the upgrade. However, removing them from the trunk
version should be added to the release process checklist.
Rick
On Mon, Dec 19, 2022 at 10:13 AM Gilbert Barmwater
<gi...@bellsouth.net> wrote:
I have downloaded and installed the 5.0.0 Release Candidate
and noticed
that the docs still have the *CHG* and *NEW* flags in them.
I believe
they are normally removed once a release is made but I am not
sure what
the process is to make that happen. Can anyone comment on
this? BTW,
the code is running without problem.
Gil
On 12/19/2022 8:37 AM, ooRexx wrote:
>> On 19. Dec 2022, at 11:23, Rony G. Flatscher
<rony.flatsc...@wu.ac.at> wrote:
>>
>> Dear P.O.,
>>
>> On 18.12.2022 22:42, ooRexx wrote:
>>> Regarding the documentation I have merged 5.0.0html and
5.0.0beta into 5.0.0beta and then copied all into
5.0.0_Release_Candidate. Everything amended from this point
on should arrive in 5.0.0_Release_Candidate only.
>> great, thank you very much!
>>
>> Would it be possible to rename the zip-files such that
they end in "-html.zip" as was done for 4.2.0, e.g. instead
of "rexxref.zip" it should read "rexxref-html.zip"?
> I have done that, both for 5.0.0beta and for
5.0.0_Release_Candidate. I amended the build scripts so that
for the future it will stay like that.
>
> At the same time I removed rexxgtk from the documentation.
It will also not be built in the future; it you want to
revive it let me know and I will add it again.
>
>> This way it is clear for the uninitiated that the
zip-archives contain the html-rendering of the documentation
as opposed to the pdf-files ("rexxref.pdf").
>>
>> ---
>>
>> @Terry: in the context of rehauling the oorexx.org
<http://oorexx.org> page we could make all the
html-documentation available from that site which eventually
would make it possible to hit the ooRexx documentation via
search engines.
>>
>> ---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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
