1. I've long been a fan of rolling releases; it's only the fear of having to rebuild my workstation / laptop occasionally that keeps me from running Rawhide by default. 2. I don't think it's the release schedule that impacts Fedora's popularity relative to Ubuntu. Ubuntu is popular because third parties test there first, and CentOS / RHEL second. If they have spare test resources, they'll do Debian or SUSE Linux Enterprise before they'll do Fedora. So I would make Fedora something like openSUSE Tumbleweed- a rolling release with heavy automated QA. That way you get your latest desktop, compilers and kernel with much less data loss risk than Rawhide (or openSUSE "Factory", to keep the analogy.) To satisfy the people who want an every-two-years-with-five-year-support distro like Ubuntu's LTS, incorporate that philosophy into RHEL and CentOS. This seems to me to be simply a matter of reallocating people and machines. I don't know why one would run Fedora on a server, even a stable release, without a long-term support capability. I spent most of the time between Fedora 24 and Fedora 25 releases on Ubuntu 16.04 LTS, mostly because of the third-party testing issue. Their GNOME 3 desktop is seriously pain-provoking and I went back to Fedora once F25 was released and I finished the project I was working on to the point where I could do everyting in a virtual machine. But I'll probably *never* run a Fedora Docker image - there's just so much more out there already existing on Alpine, Debian or Ubuntu. I'll most likely *never* run a Fedora Project Atomic host, or a Fedora Amazon / Google Cloud / Digital Ocean instance. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
