On Thu, 20 May 2021 at 02:55, Clement Verna <[email protected]> wrote:
> > > > >> It's not like making changes and breaking upgrades is acceptable in >> Fedora Linux either. > > > Breaking or non backward compatible changes are acceptable in Fedora Linux > tho between major version bump. Again here the cgroups v2 is a good > example, folks using Docker had to perform some manual steps to switch back > to cgroups v1 to keep using their workflow working. This is fine when you > have a major version bump but this does not happen in FCOS. > > Then maybe FCOS needs to have a major version number to indicate that these breaks are going to happen. I am going to say off the bat it DOES NOT need to be the same as the Fedora Linux release number. It also doesn't mean that number change means that you can't move a system from say FCOS-1 to FCOS-2... but that you make no promises of moving it back to FCOS-1. Eventually something is going to cause this. The many changes like: cgroups etc are adding up to an area where FCOS will reach a point it only 'matches' Fedora in name and might as well be based off of Debian Jessie or Slackware 14.2 or CentOS-8 Stream. -- Stephen J Smoogen. I've seen things you people wouldn't believe. Flame wars in sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law. All those moments will be lost in time... like posts on BBS... time to reboot.
_______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
