#6047: handle packages that are retired only in Branched but not Rawhide

Fedora Release Engineering rel-eng at fedoraproject.org
Sat Nov 15 10:49:51 UTC 2014


#6047: handle packages that are retired only in Branched but not Rawhide
-----------------------------+------------------------
 Reporter:  till             |       Owner:  rel-eng@…
     Type:  task             |      Status:  new
Milestone:  Fedora 20 Final  |   Component:  koji
 Keywords:  meeting          |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------
 Currently we allow to retire packages in Branched even if they are not
 retired in Rawhide. Today I realized that if a package is retired in
 Branched (i.e. it will be blocked in f21), it will also not be shipped in
 Rawhide, even if it is not retired there, because currently if it is
 blocked in f21 it is also blocked in f22. It might make sense to only
 retire packages in Branched to not ship packages with broken deps, like it
 is currently proposed. However this does not mean that the package should
 be retired in Rawhide, to allow it being fixed for the next release.
 Therefore we should decide if we:

 1) Allow retirement in Branched only for packages retired in Rawhide
 2) Unblock packages in f22 if they are only retired in f21

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


More information about the rel-eng mailing list