#6010: Create Fedora 21 Beta test compose (TC) and release candidate (RC)

[Fedora Release Engineering]

#6010: Create Fedora 21 Beta test compose (TC) and release candidate (RC)
-----------------------------+-----------------------
  Reporter:  adamwill        |      Owner:  rel-eng@…
      Type:  task            |     Status:  closed
 Milestone:  Fedora 21 Beta  |  Component:  koji
Resolution:  fixed           |   Keywords:
Blocked By:                  |   Blocking:
-----------------------------+-----------------------

Comment (by adamwill):

 Re-opening for RC2. There is a rather significant consideration with the
 compose environment. I am requesting an SDDM update as a freeze exception
 below. I have pushed a set of commits to spin-kickstarts:

  * https://git.fedorahosted.org/cgit/spin-
 kickstarts.git/commit/?h=f21&id=ab93ba68cb43fc95d841d357cc3885bb0c7582ea
  * https://git.fedorahosted.org/cgit/spin-
 kickstarts.git/commit/?h=f21&id=73543397cfa075ae60c0c0570478e3911a39bb57
  * https://git.fedorahosted.org/cgit/spin-
 kickstarts.git/commit/?h=f21&id=1dddaeebc48d8d865fb3397d4381033295b84de9

 which go along with the SDDM update. If it is pulled into the compose,
 those commits *must* be in the spin-kickstarts used to build the KDE live
 image. If the SDDM image is not pulled into the compose, those commits
 *must not* be in the spin-kickstarts used to build the KDE live image.

 If you just include all the builds listed and use HEAD of spin-kickstarts
 f21 branch everything will be fine, but as it's so critical to the KDE
 image I thought I'd better explain this very clearly just in case anything
 weird happens.

 Please include:

 == Blockers ==

  * [https://admin.fedoraproject.org/updates/python-
 blivet-0.61.8-1.fc21,anaconda-21.48.13-1.fc21 python-
 blivet-0.61.8-1.fc21,anaconda-21.48.13-1.fc21] for
 [https://bugzilla.redhat.com/show_bug.cgi?id=1156614 #1156614],
 [https://bugzilla.redhat.com/show_bug.cgi?id=1156354 #1156354], and
 [https://bugzilla.redhat.com/show_bug.cgi?id=1157864 #1157864]
  * [http://koji.fedoraproject.org/koji/buildinfo?buildID=587578 selinux-
 policy-3.13.1-91.fc21] for
 [https://bugzilla.redhat.com/show_bug.cgi?id=1156378 #1156378] (no Bodhi
 update yet)

 == Freeze exception ==

  * [https://admin.fedoraproject.org/updates/FEDORA-2014-13809/uboot-
 tools-2014.10-4.fc21 uboot-tools-2014.10-4.fc21] for
 [https://bugzilla.redhat.com/show_bug.cgi?id=1158149 #1158149]
  *
 [https://admin.fedoraproject.org/updates/FEDORA-2014-12442/sddm-0.9.0-2.20141007git6a28c29b.fc21
 sddm-0.9.0-2.20141007git6a28c29b.fc21] for
 [https://bugzilla.redhat.com/show_bug.cgi?id=1149610 #1149610] (this is
 the update with spin-kickstarts implications, see above)

 There is a gnome-initial-setup update that fixes an accepted FE but I'm
 gonna say at this point we should play it safe and not include it. I want
 the SDDM update because it fixes CVEs, and the ARM one fixes a bunch of
 platforms. The g-i-s bug is less significant.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6010#comment:17>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project