Lack of policy for qualification for update, and no backports repo?
Posted Mar 11, 2010 13:42 UTC (Thu) by buchanmilne
Parent article: Who is Fedora for?
I think the problem here is that Fedora is trying to accomplish two
different goals with the same repo:
- Updates all users should get (security and bugfix-only updates)
- New version updates (which may provide new features etc. at the risk of
Of course, sometimes the lines get blurred, but the QA/vetting process for
non-security updates should be sufficient going as updates, and packages
that don't pass or get sufficient testing should not be shipped as updates.
I note that in Mandriva, updates is reserved for bugfix and security
updates. The contrib repo is not QA'ed though, so security updates for
contrib can go directly (submitted to build system and immediately after
successful build and any automated test directly to primary mirrors) to
contrib/updates, while updates for main must go to main/testing before
being QA'ed by the QA team. On successful tests, the package will be moved
For new versions, there is the backports repo (which also allows
introducing packages which did not exist in the distro when released), so
for example amarok 2.2.2, gimp 2.6.0, thunderbird 3.0.x, openldap 2.4.21,
xen 3.4.2 etc. are available there (in main/backports). contrib/backports
has things like gcompris 9.2, gpodder 2.2, kernel 126.96.36.199 koffice 2.1.0,
monodevelop 2.2, nexuiz 2.5.2, playonlinux 3.7.3, psi 0.14, qgis 1.3.0, vlc
1.0.5 xbmc 9.11.
However, KDE 4.4.x is not available in any Mandriva stable repo, only in
"cooker", which is what you run if you want bleeding edge. KDE 4.4.0
available in a KDE repo (packaged by the Mandriva KDE maintainer). Then
again, what percentage of fedora users actually run rawhide (compared to
those that run, say, Mandriva cooker).
This arrangement allows people who want mostly stable with updates but some
new versions to get automatic updates from the "updates" repos, and choose
updates from backports, without subjecting everyone to the most aggressive
updates available. It also allows contributors to get new packages out to
users without too much effort and bureaucracy.
to post comments)