Release Fedora 24. Race for Versions

Yesterday, June 21, a new version of Fedora was released. What's new in Fedora can read on oppenet . I have been using this OS for a month and a half and I wanted to share with the habra people about whether to switch and whether to release it so often.

Why Fedora?

The fact is that back in 1998, I installed RedHat Linux version 4, figured out the rpm system and learned how to create my own rpm builds. Then came Fedora Core. It was like a breath of fresh air, the core was updated regularly, always the latest versions of php, perl, Gnome, gcc. I used the Fedora build on both the desktop and the colocattion production. The pace of development pleased, our company even introduced virtualization based on oVirt (KVM management performed by RedHat programmers) . It would seem that everything “blooms and smells,” but, in my opinion, this is not so.

What we have in the new release

• System:
  Glibc 2.23, kernel 4.5, gcc 6.1
  all on top - credit!
  
• Programming languages:
  • Python 3.5 - fresh
  • Ernang 18.3 - fresh
  • Ruby 2.3.1 - fresh
  • Nodejs 4.2 - old, now 6.2
  • PHP 5.6 - old, now 7.0
  • perl 5.22 - old, now 5.24
  
  not so good
  
• Updated font - Cantarell, font authors - credit
• You can manually turn on support for the OpenH264 codec
• FreeIPA 4.3 - good!
• Everything else - well, not bad, that it is, but it seems to me that these are niche features.

')
The list of features is not impressive, there is no “Wow!” That arises from a version change.

What problems do I see?

1. Well, it is clear that the team that releases, constantly does not have time. Previously, deadlines were moved for several days, well, for a couple of weeks - now more than a month .
2. The release is not balanced, something was upgraded to the latest stable versions, but was “scored” for something.
3. Some of the packages that my company needs for work need to be re-compiled already for 5 Fedora 19-Fedora 24 distributions.
4. Our programmers no longer update the system with each new release, most of them "jump through the version."
5. But many companies have problems with assemblies for new releases:
rpmfusion , didn’t have time before the release, but today there are packages for Fedora 24
oVirt - the latest build for Fedora 22
MariaDB - the latest build for Fedora 23
ParconaServer for 24 Fedora you do not collect from src.rpm
(Well, that's what I'm working with)
6. No update passes without any problems, problems with dependencies on third-party package builds, the format of configs sometimes changes or needs updating, and you yourself know it.
7. There are no clear dates on which the release is oriented, once it was the end of autumn / end of spring. Now it's already a new year / beginning of summer.

What to do to make it better

1. It seems to me that calling the version with reference to the year of release is a good idea. Fedora 2016 sounds good. The frequency of releases set to 1 year. You can always release the desired update.
2. To increase the attractiveness of the distribution itself, at least for the assembly that is “Server”, enter LTM (Long-term Support) for 3 years
3. Pay more attention to marketing, release announcements look very unattractive.

Does it update

Well worth it, where are you going? Everything, your Fedora is outdated, you have not had time to get used to it? - don't worry, upgrade and get used to 24 :)

For more than a month when working with the beta version, I cannot complain about stability. No better and no worse than Fedora 23, it seems like nothing has changed.

Is it so often released