Hi,
> On Jun 22, 2022, at 6:26 PM, Eric Auer <e.a...@jpberlin.de> wrote:
>
>
> Hi!
>
>> Changes since FreeDOS 1.3 release
>> 2022-06-22 10:02:08 project_RBE (shidel): Adjust interim build file names
>> 2022-06-22 09:13:23 project_RBE (shidel): Automatic Unstable Build Versioning
>> 2022-06-21 09:21:37 project_FD-NLS (shidel): added FreeDOS release README to
>> NLS project
>> 2022-06-19 20:43:04 project_FD-NLS (cardpuncher): Add files via upload
>> 2022-06-19 19:51:27 project_FD-NLS (shidel): from W.Spiegl
>> …
>> 2022-06-17 23:29:30 project_FD-NLS (Andrew Bird): Fixup incorrect UTF-8 file
>> extension suffix
>> 2022-06-13 14:46:45 sbpmixer (Shidel): Initial commit
>> 2022-06-13 10:50:00 sbpmixer (shidel): v2.0
>> 2022-06-06 21:32:25 project_FD-NLS (cardpuncher): Add files via upload
>> 2022-06-03 06:53:06 project_FD-NLS (shidel): W.Spiegl
>> 2022-05-30 10:38:58 project_FD-NLS (shidel): Codepage corrections
>> 2022-05-26 10:42:04 xdel (shidel): v2.08
>> 2022-05-24 02:31:32 xdel (shidel): v2.07
>> 2022-05-17 07:40:47 fasm (shidel): v1.73.30
>
> How about those kernel updates which allegedly make FreeDOS compatible with
> Windows for Workgroups WfW 3.11 beyond safe mode, and with Windows 3.x 386enh
> mode, which were both not supported by previous kernels?
I should go into a little more detail regarding the automatic CHANGES.LOG.
First, the log is created from the git commit messages from where the the RBE
pulls files to create a build (interim or release).
project_RBE is the RBE itself. project_FD-NLS, project_FDI and project_FDI_x86
are those respective projects. These are not FreeDOS packages. However, they
are used directly by the RBE during release creation. The RBE also creates a
SOURCES package based on the FDI project for inclusion on the install media.
Other message entries (like sbpmixer, xdel, fasm, etc.) are generated from
their commits to the appropriate project staged in the FreeDOS Archive
(https://gitlab.com/FreeDOS <https://gitlab.com/FreeDOS>). While some programs
are maintained there, most are not.
For the ones maintained elsewhere, the Archive must be manually updated at
present. That involves coping the files, possibly compiling, arranging them
into package format, updating metadata and other adjustments. When they are
committed to the archive, they generally just get a version update commit
message. Like xdel v2.07 and v2.08. Since it is maintained over at
https://github.com/FDOS/kernel <https://github.com/FDOS/kernel>, this would be
the same for the kernel. For those, you would need to visit that specific
project to view individual changes. Perhaps at some point, we could include
such “SOURCE LOGS” in the Archive for those and they could be included by the
RBE.
The RBE also filters out a bunch of commit messages. For example, to maintain
correct file timestamps the package maintenance utility fdvcs.sh pushes an
additional commit regarding timestamps gets filtered out. Also, simple
individual package NLS updates are filtered. Consecutive commits with identical
messages gets pruned and some additional filtering is performed. Without the
filtering, just the commits since the last release was maybe a dozen or so
pages long and bloated with useless and duplicate information. With the
filtering, it is now about a page or two and much more relevant.
However, the FD-NLS project gets a lot of updates and ends up with many entries
in the LOG. But if those are of little interest, you could easily filter them
out locally with grep.
Also, the CHANGES.LOG only includes changes since the prior build. For
Releases, this will be all changes back to the prior Release (at present
v1.3-Final) and for interim builds the previous interim build (generally one
the last month). Although, it may be better for the interim build to include
all changes back to the previous Release.
Finally, the CHANGES.LOG is all of those updates combined and sorted in reverse
order. They are also included in the RBE build report. However, there they are
broken down by project / package. For packages that have been modified, the
entry in the main list includes an in-page link to the appropriate list of
changes. You should check out the new report…
https://fd.lod.bz/releases/unstable/report.html
<https://fd.lod.bz/releases/unstable/report.html>
:-)
Jerome
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
