: IMO, a lot of the packaging is somewhat boring. You just download the new tarball, verify it, increase the number in the spec file, reset the release number to 1, check if patches still apply, then commit all changes and submit the new spec file for building. I've automated that bit (triggered by ftp-release-list). If it builds successfully, it'll be available really quickly for Mageia Cauldron users. I know other distributions have a policy that things should be tested before uploading, but that is what we use Cauldron for. Further, anything on gnome.org
is often reliable anyway. Also, I don't do stable->unstable upgrades (initial change from GNOME 3.2 -> 3.3 is more manual on purpose). This is partly helped because Mageia packages libraries by their major version (e.g. lib64jpeg8-1.2.0-3.mga2 has /usr/lib64/libjpeg.so.8). We can package a "libjpeg" with a new major (e.g. 9) and then gradually recompile things against the new libjpeg. Until everything is recompiled, both libjpeg packages are on the mirrors. There are also checks in place to ensure things get recompiled.
I'm trying to automate all the boring tasks. E.g. updating buildrequires, removing patches applied upstream, etc (still on the todo though).
Oh, and within Mageia we have maintainers (people responsible), but anyone can commit and submit a package. So if something bad happens, there will be a lot of people who can fix it quickly. There are also lots of people looking at every new package + spec change (very noticeable on the mageia-dev mailing list).