-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/17/2014 05:55 PM, Elad Alfassa wrote: > Hi all. > > Continuing the discussion from here > https://plus.google.com/+RichardHughes/posts/LmPUMRJVFP6 (because > G+ is a horrible platform for discussion). > > Also see this thread: > https://lists.fedoraproject.org/pipermail/desktop/2014-January/008741.html > > I don't think anything have changed since the last thread > (besides Matthew voicing his perfectly valid objections to push it > as an update). > > What I want to know is if there are people who are willing to > invest their time in making 3.12 in F20 a reality, be it via COPR > or a regular update. For a regular update, we'll need FESCO's > approval, so someone will need to submit a ticket with our > proposal. > > If we are going to do this in COPR, we will face some critical > issues: > > How can we preform sufficient QA in COPR? The lack of a -testing > stage is a huge disadvantage. Moving packages between COPR repos > is impossible, so if we make a -testing repo separately a rebuild > will be needed every time we move packages between -testing and > -stable COPRs, this will take quite a lot of time, seeing how COPR > is much slower than koji. > > Another issue that might arise with COPR is the lack of "team" > support. This means that if we do it in COPR, only one person will > have access to updating any package of the stack. This is quite a > dealbreaker, because the entire workload will fall on that person. > Also, if said person is unavailable, updating the repo will be > impossible. > > Those issues are quite major if we are going to maintain an entire > GNOME release in COPR, and the reason why I believe we should use > COPR as a testing stage and then move it all to the real repo. > > So, anyone volunteering to this effort? I think convincing FESCO > to grant a policy exception is the only sensible way right now, > unless the features we need (QA stages, bodhi-style karma system, > and team repositories) will be implemented by COPR soon. I've decided to take this particular flying leap. Initial bugs: * bijiben requires an olderversion of libcogl and should be rebuilt in the COPR against the new version. * None of my extensions (including those provided as part of GNOME Classic) work after the upgrade. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlMGPNgACgkQeiVVYja6o6NMIQCfZSp9QHBOLNIPDxn7KUoL+5g5 IcEAoK5i1RildBq6XDCQ7s9ZArwZAFdN =FgPl -----END PGP SIGNATURE----- -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
