Hi Jim and all,
Well, the work I wanted to do to the RBE and release media is finished. I’ve
replaced the downloads on my server with the new versions. You can fetch them,
or view the report information at https://fd.lod.bz/releases/unstable/
<https://fd.lod.bz/releases/unstable/>
Mostly, the additional stuff I wanted to get in there came down to two more
things mentioned earlier. The interim builds include a warning message
displayed at boot (from install media and one the installed system). Also, the
interim build uses a different theme for the installer. Basically the theme is
the same as the normal mode except instead of a blue background, it is black.
In order for us to have the first interim build officially available on 7/1,
there are a couple minor items that need a final decision…
First, how will we Label and refer to these builds? I went with “Unstable” with
the short name would be “FreeDOS U2207” and long name as “FreeDOS
2206-Unstable”. To me, it is a well established nomenclature. However to the
general user base, that may not be the case. We could use “Unstable” for now
and possible change it later. But, I think we should commit to a scheme and
stick with it for the foreseeable future.
Should we stick with “Unstable” or use…
Test build; FreeDOS 2207; FreeDOS 2207-TEST
Development build; FreeDOS DEV2207; FreeDOS 2207-DEVEL
Or, some other specific terms or variation?
Second, do we want the changes log to go back as far as the previous interim
build or back to the previous OS release? At present, it limits itself to the
previous build. But since users / testers will probably not test every
iteration, I think it may be best to always include everything back to the
previous official release. At present that would be FreeDOS 1.3-Final.
Third, what path do we wish to provide them on ibiblio under
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/
<https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/> ?
I prefer
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/unstable
<https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/unstable>
or
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/unstable/2207
<https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/unstable/2207>
But, we could use dev, devel, or test. I don’t think unofficial/dev is
the best choice and suggests it is not an official test version. But, that
could just be me. As always, whichever you decide is best.
Finally, what path on ibiblio do you want to use to provide package updates?
This has nothing to do with creating the interim build. As you recall, the
current RBE uses the GitLab FreeDOS Archive (https://gitlab.com/FreeDOS
<https://gitlab.com/FreeDOS>) to create the packages on the release. It can
also automatically pull specific branches of those packages based on the
release, interim, development or other type of build it is creating. The
package update url only applies to where the release / interim build will check
for package updates.
I think it makes sense to keep it along side the other OS update repositories.
There are already repositories for each Release
1.1 -
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.1/
<https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.1/>
1.2 -
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.2/
<https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.2/>
1.3 -
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/
<https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/>
I think using
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/
<https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/>
makes sense. It also makes it easy for users running one of the Official
Release versions (1.1, .1.2, 1.3) to find and try the latest versions of
package updates. However if you think renaming it to something like “TEST” or
“DEV” is a better choice, it is easy to adjust. The repository management
utility is flexible with such things and at is also not a problem to put it in
an entirely different directory not under “repositories”.
Let me know what changes you want. None of theses changes are that difficult or
time consuming. Hopefully, we will can make the first interim build available
on 7/1.
:-)
Jerome
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
