> On Jan 4, 2025, at 12:11 PM, Jim Hall via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > I agree that whatever we put in FreeDOS 1.4 RC2 should be what we > include in FreeDOS 1.4. We need to focus our efforts on testing RC2 so > we can release 1.4. > > Ideally, we would have had all the changes in before releasing RC1. > Swapping out bmp2png with dosview is a pretty easy decision. As Jerome > said, it's not part of the "core" components of FreeDOS, it's an image > utility, no issues in making that change. > > The current FreeCOM in 1.3 (same as RC1) is 0.85a. This is a good > FreeCOM, but it has some bugs that should be fixed, and 0.86 does > that. > > I know I said in an earlier thread (a while ago) that we should hold > off on including an updated FreeCOM and kernel in 1.4 so they can be > thoroughly tested, with plans to include them in a future FreeDOS > "1.5" or "2.0" distribution (which we could release later this year). > But having FreeCOM 0.86 in hand, I think it's worth including in RC2. > FreeCOM 0.86 has been very solid in my tests, I haven't been able to > trigger any bugs in it. Including 0.86 in RC2 will be a further test > that I can do everything, including supporting the install process. > > But I know there's a risk. If we see problems with FreeCOM 0.86 in > FreeDOS 1.4 RC2, then we should release an RC3 that reverts back to > 0.85a. But if 0.86 works well in RC2, then we could release FreeDOS > 1.4 in March (instead of an RC3) using FreeCOM 0.86.
That is doable. We just need a “Full” build of FreeCOM including the different languages and swap versions. If that is all compiled and ready. It can be pushed to the FreeDOS GitLab Archive staging project for FreeCOM under a “candidate” branch using the same directory structure and file names that are currently used in that project. The RBE and installers will then use the newer FreeCOM for the next RC. Like I said, it must have the same structure or there will be issues building a release. For FreeDOS 1.5 (or later), I want to improve the FreeCOM package and remove the need to have the different versions pre-built in the package. Either by updating the installer(s) to glue the languages onto the binary at install time, or by adding functionality to the SETLANG.BAT to perform this task at any time. > > > **That said, I still think a new kernel (even if it's released soon) > should wait for the next distribution. And again, we could release an > updated distribution with the new kernel later this year .. and I > think a kernel update that supports WfW should bump up the > distribution version to FreeDOS "2.0". There are a bunch of things I would love to see for a FreeDOS 2.0. But, that discussion can wait. :-) _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
