On 22.12.2022 23:18, Gilbert Barmwater 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
On 22.12.2022 21:48, 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
Yes, hopefully, people on this list will know that they need to download
the book(s) they wish to inspect and not to expect that installing a new
build will give it to them. Lets see if anyone raises any issues with
the books and then we can "trigger" a new set of builds.
Gil
On 12/22/2022
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
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
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
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
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
Subject says it all: docs/branches/5.0.0: updated copyright, added & committed
"${book}/revision_info.txt", updated & commited EDITION entity
The following scripts got now added and commited to docs/branches/5.0.0/tools:
listAuthorsAsOfLate.rex
updateCopyright.rex
