tag:blogger.com,1999:blog-8289133884257433530.post2287362631518400886..comments2023-04-30T11:48:35.735+02:00Comments on More Fedora: How code makes from upstream to Fedora and RHELAnonymoushttp://www.blogger.com/profile/12153554158754437579noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8289133884257433530.post-66592820445223926582009-10-09T11:03:40.986+02:002009-10-09T11:03:40.986+02:00The point is the two distributions are independent...The point is the two distributions are independent projects, with very different goals and target audience.<br /><br />Fedora releases at a fast pace to integrate the latest from upstream projects, RHEL basically forks Fedora at a given time and then the "quality assurance" step in RHEL kicks in, actually marking the start for the Beta testing phase.<br /><br />From there the fork is handled entirely within Red Hat and they support it for years to come by backporting patches into the original packages (so for instance, RHEL is still running a kernel based on 2.6.18).<br /><br />So, before the new RHEL finish it's Beta cycle and hits the streets Fedora already integrated enough new packages that its value for the in development RHEL is nil.Anonymoushttps://www.blogger.com/profile/12153554158754437579noreply@blogger.comtag:blogger.com,1999:blog-8289133884257433530.post-31159973300402856752009-10-09T06:11:36.030+02:002009-10-09T06:11:36.030+02:00man, I understood the process, but still it does n...man, I understood the process, but still it does not make any clarification on "fedora is beta of RHEL", worse, it kind of harden that view: RHEL does cherry picking on what it interests, and leave others into fedora without what you called "quality assurance resources to test, harden and certify this set of features".<br /><br />Sorry, I did not see your point, maybe I am wrongAnonymousnoreply@blogger.com