Hello everyone!!
D.eSystem 6.0.6 alpha introduces the first GUI for my operating system D.eSystem 6.
The system is currently keyboard‑only, but mouse support is planned for future versions.
The usage is similar to D.eSystem 6.0.5, but now with a graphical interface, and the calculator also received a GUI version.
Requirements:
64‑bit CPU
UEFI firmware (Legacy BIOS is not supported)
D.eSystem 6.0.6 alpha runs on any VM (QEMU, VirtualBox, VMware) and on real hardware.
Download D.eSystem 6.0.6 alpha here: https://github.com/D-electronics-scratch/D.eSystem-6.0.6-alpha-iso-download
Looks very interesting, will definitely try to play around with this if I find a free minute at some point.
One thing that struck my eye is your use of github repositories which I am not fully understanding. Is there a specific reason for having each major and minor version of the OS as a separate git repository with only a single real commit, and each iso download as another separate git repository?
In my mind it seems so antithetical to tracing the development history that right now I am scratching my head at it a little.
Should I only have one reposotory?
That is the convention. It is also common for devs to make a new branch for each release so you can issue updates for that version by adding a commit to that branch.
Definitely one and only one repository where the "versions / releases" are branches or tags. That way, you can compare your versions with git, fix an old version, etc.
Having multiple repositories is a PITA for you and for others.
I like this branching strategy but you can use your own: https://trunkbaseddevelopment.com/
Ok,thanks for your tip
You should also have a backup somewhere else every other major release in case GitHub glitches out and decides to delete your account, or marks it as malware or such. It's happened to even better known projects like KitchenOwl.
Yes,I have a backup local on a USB drive,I save there every version from D.eSystem 6