- This topic has 1 reply, 3 voices, and was last updated Jun 15-9:44 pm by Brian Masinick.
-
Posts
-
Brian Masinick
I just downloaded a brand new instance of Debian Bullseye. I’ve been running Bullseye in a different partition for many months, which is why I have been so optimistic about it.
Let me be candid about what I’ve been doing so that you can get a fair and reasonable impression, then, of course, I recommend that you consider grabbing a copy for yourself to form your own impressions, if you have an environment that you can use for testing.
1. Like many antiX and MX releases, these Alpha and Beta versions come from a very solid place. Though there are certainly NOT release quality – AND we KNOW that Debian won’t release unless they meet a rather rigorous standard, which includes NO remaining SHOW STOPPER or critical category bugs, and a low number of defects in general, below a certain threshold, and nothing that prevents usage without usable workarounds for any remaining issues.
2. I have not done exhaustive testing, but I have used several of these builds for routine every day use for Web browsing, file management, and simple editing, which is my typical every day workload as a retired former software professional. I’m definitely NOT going through a rigorous set of test cases, yet I am, and I have been, using this, and our antiX releases and test versions for the typical things that I do.
Given that we now have a proposed freeze that is about a month away and a tentative release date that is about 45 days away, it’s reasonable to start building our own final code for our next release upon this foundation, realizing that the final version will still change a bit, but the core pieces, at this stage, are relatively solid, with a set of remaining issues that have been documented and are being tracked as this software works toward its planned release at the end of July.
Should there be any remaining issues that do not get resolved by the end of July, we don’t necessarily have to lock our own release to that date, but we can be watching it, putting our non SystemD replacements firmly in place, making sure that our own infrastructure is also solid.
As I’ve felt with Debian, though we also have several issues to resolve before release, we are also in a solid position to cut down our defects and to the extent that we are able to do so, track them with reproducible, documented, tested and recorded steps. We may or may not be as formal as they are, but I am pretty happy that we have a lot of people who care deeply about doing the best possible job, and I’m pleased to be a small part of it.
So I hope that at least a few people take a look at Debian too, because even though we diverge from it in the scheduling component (systemd and related subsystems) we still use a great deal of Debian software that isn’t tightly coupled to those elements. Despite some sharp philosophical differences, we still owe a lot to this distro and it serves our own interests to see that both they and we are successful during our testing stages. Best wishes and happy testing with Debian, antiX, and maybe some other Debian derivatives too!
--
Brian MasinickBrian Masinick
By the way, up to this moment, I’m running a LIVE instance of this RC2; I installed Bullseye Alpha 2 some time ago, and like our antiX stuff, I’ve been updating it with the usual sudo apt-get update ; sudo apt-get dist-upgrade (or their shorter apt alternatives).
So I’m testing LIVE now, and I’ve been testing INSTALLED for several months.
--
Brian Masinick
- You must be logged in to reply to this topic.
