Package Modularisation and Other Issues of Recent-ish Feren OS Past - An apology

Every day I'm always trying to make improvements and features and improve existing features in order to make the Feren OS Experience as great as possible... this can also mean that issues may arise and so I want to try and make sure that the issues are as lacking and rare as possible, but quite recently that has slipped a bit, and some noticeable cracks have shown in the updates Feren OS has had in recent time, before eventually being fixed, within Feren OS and Feren OS's packages alone. Here's an apology for the inconvenience those issues might've then caused, as well as me explaining what I've put in place since that has happened.

Feren OS PPA Settings (aka: Manage Base Update Channel)

Now you might be wondering what issues have happened regarding this? Quite a big slip up, actually, that went unnoticed for a few days...
So, basically, what happened was that the 'reset-feren-ppas' command which does what it says on the tin was mistakenly opting in everyone to the Non-LTS Update Channel when said buggy update was installed, meaning that an unsuspecting user would then be updating their system to have a Non-LTS Major Update then come and them be on a Non-LTS base of Ubuntu until the next LTS comes out. I'm truly sorry for this error but from what I know barely any users were affected, and no one reported it as an issue from what I've seen... The only reason I knew about this was because I updated another Feren OS Laptop which was not opted in to Non-LTS just to then notice that the 18.10 BETA (at the time) Major Update was then made available.

Since then, an update was released, and everyone using the updated package would've had their PPAs reset to defaults no matter what having installed that package, so people who didn't want to be opted-in to the Non-LTS channel are no longer opted in, unless they've already installed the Non-LTS Major Updater Update to their machines. If you've taken the update by accident, then you have two choices: Reinstall using the October 2018 Snapshot ISO, or keep Major Updating until the next LTS Major Update, and then immediately go back to LTS-only once that LTS Major Update is complete.
Sorry for the inconvenience caused.

Themes... or lack of.

Another big issue that had come as a result of the modularisation of some packages to make Themer better detachable from the Cinnamon DE was that Themes would either be completely hosed from your Feren OS install, meaning NO System Settings > Themes option, or Themes would be the Themes page found in every Cinnamon Desktop Environment using Distribution (the Vanilla Themes page). Sorry about that, too.

This isn't exactly fixable per-se by me past the point I've gone, but for starters the latest ISO is NOT affected by this issue in any way, and rather comes with the fix for this problem, and secondly for users affected, there's a tutorial on getting the Feren OS Themes page back in System Settings. I'm again sorry for this inconvenience that losing this feature temporarily might've caused.

Overall, what has been done in the wake of these accidents?

Well, a few things:

A New Troubleshooting Page:

There is now a Troubleshooting Page for fixing known issues that may have been caused by errors in packages, being accessible via 'Help' > 'Troubleshooting' on the website, or by clicking here. If there's at any time a major accident ever again with packages, gosh forbid, then that is the webpage to go to for a solution to the problem(s).

A new Snapshot:

As mentioned earlier, there's now the all-new October 2018 Snapshot available to download from our website, which comes pre-fixed from these issues people may then encounter with updating the July 2018 Snapshot, so I'd recommend using the October 2018 Snapshot from here on out instead of July 2018 for reinstalls and the like.

There is one thing however that will be very unlikely to ever happen: Maintenance Tool Online Script Downloading:
The concept of this is that an update would come to the Maintenance Tool to be able to constantly keep its script for checking for and fixing issues up to date so it isn't affected by APT-related issues, however, due to uncertainty over how secure that'd be, especially since the program is always running as Superuser, that will most likely never be happening any time soon.

Overall, I'm sorry for any inconvenience that these issues caused, and there really is no excuse for these issues, but I will try my best to make sure nothing like this ever happens, and gosh forbid it does, I'll try my bestest to be open about said future issues...
I hope you can forgive me for these human errors... even I feel some of the errors I made were sort of utterly stupid at times... Anyway, I hope you understand, and cheers for reading this.
PS: Be thankful that we didn't go Windows 10 1809 levels of accidents... That's a level of mistake(s) I seriously don't want to go ANYWHERE NEAR.
Most importantly, please, if you find issues within Feren OS, DO NOT hesitate to make use of the 'Send Feedback' shortcut, even if you're on Feren OS 'KDE Experimental', it doesn't matter, you can still make use of it fine, as long as the issue at hand hasn't already been reported, and send bug reports to The Developer on just about anything Feren OS.
(BTW, subscribe to EposVox if you want, this might be a plug in a serious post, but seriously though, he makes great content, he deserves the subscribers he gets and the plugs he gets)

The Feren OS Dev