Good point Gil, this is the same for macOS so we need to stop amending the documentation and then someone could do the final commit, maybe tomorrow?
I have done all I could think of, there are a few bugs reported by me that should probably be “won’t Fix”. Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se > On 22. Dec 2022, at 23:18, Gilbert Barmwater <gi...@bellsouth.net> wrote: > > So, as Jon has noted, on Windows the installer includes the documentation > which will be the "current" set as of the time the Windows build is executed. > Now if one updates one (or more) of the documents - which we have been doing > quite a bit over the last several days - the documents get regenerated but > new builds are not. I just downloaded the newest Windows 64-bit installer I > could find which was built 2 days ago and, of course, its documents are NOT > the latest. I guess someone needs to do a "dummy" commit to the code base > (in the Release Candidate?) in order for new Windows builds to be generated > that will pick up the latest documents. Or is that going to happen some > other way? > > Gil > > On 12/22/2022 3:48 PM, ooRexx wrote: >> The building and uploading of the documentation is, and has been for quite >> some time, automatic. The documentation will be built within an hour of any >> amendment to the documentation (and I mean ANY amendment changing the SVN >> revision). What is on Sourceforge should always be the latest version of all >> documents, I can see for instance that the name changes appear to be there. >> The only exception is when new amendments are done while building the >> documents but eventually that is sorted out (within some hours). >> >> Today I experienced one hick-up with building ooDialog (the heaviest >> document) since the Unix command rm for removing files before build ran out >> of internal space! Quite an unusual problem but I think I managed to work >> around it, at least I do not see any errors or warnings any more. >> >> May I ask all interested bodies to look into some random documents and check >> that they appear to be correct? If I hear nothing I assume this will be the >> final build. >> >> The only document I have touched , the document oorexxbuild.pdf is in no way >> near finalised; it describes an earlier state of the build and test system >> and I intend to continue update it, but not right now, I have a chimney to >> clean... >> >> Hälsningar/Regards/Grüsse, >> ooRexx >> oor...@jonases.se <mailto:oor...@jonases.se> >> >> >> >>> On 22. Dec 2022, at 19:20, Rony G. Flatscher <rony.flatsc...@wu.ac.at >>> <mailto:rony.flatsc...@wu.ac.at>> wrote: >>> >>> On 22.12.2022 19:10, Gilbert Barmwater wrote: >>>> >>>> If this is the final step, I think we should have P.O. build a new set of >>>> documents and upload them to sourceforge, replacing those that are there >>>> if possible. Then I would encourage everyone on this list to retrieve >>>> them and review them for appearance at least. Barring any really bad >>>> comments, the doc's will be ready for final release. >>>> >>> +1 >>> >>> ---rony >>> >>> >>> >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> >> >> >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> <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
