Distro developers consider skipping this verse for the sake of tweaking the system development process.
The Fedora project is one of the most avant-garde when it comes to open source technology and definitely not a project that is afraid of reinventing itself for improvement. Apparently 2019 is a very important year for Fedora and it is in a certain release gap.
The Fedora project has changed several times in the past, to exemplify, until version 7, the project was called "Fedora Core", because of the main and extra repositories, in version 21, we had the division into 3 versions, the Workstation, Server and Atomic and recently we had the project announcement Silverblue.
Fedora version 29 was released a few weeks ago and we reviewed the news for you to check out:
Fedora version 30 is due to arrive in May 2019 and it will be the only one to be released by the project over a longer period of time, perhaps a full year, even considering skipping version 31, as Fedora often releases more regular versions. every 6 months, with possible (minor) delays.
Contrary to what some people may think, it is good to make it clear that this release gap has nothing to do with IBM's purchase of Red Hat, this is a process of remodeling the district-building process proposed by the Fedora community and members themselves. The distro aims to reshape how to automate testing and improve the software release process, as well as improve the project infrastructure itself, to make Fedora more scalable and better in the long run.
Although the words used to describe change are few and far between, the procedure is really massive, and it will occupy Fedora developers, leaders, and project managers who are in favor of skipping distro release 31 and the development cycle to achieve these goals. .
To ensure that Fedora 30 users are adequately supported, increasing distro support is being considered until a next release is available. On the Fedora Project Website Some notes have been published explaining some of the challenges and solutions proposed for this recast.
See you next time!
_____________________________________________________________________________ See any errors or would you like to add any suggestions to this article? Collaborate, click here.