On Mon, Sep 17, 2018 at 3:59 AM Martin Pitt <mpitt(a)redhat.com> wrote:
Stephen Gallagher [2018-09-14 11:07 -0400]:
> On Fri, Sep 14, 2018 at 11:00 AM Martin Pitt <mpitt(a)redhat.com> wrote:
> <snip>
> > So long-term cockpit-kubernetes will go away. As a strawman I would propose to
> > still keep it in Fedora 29 (as it's past beta freeze already), but drop it
from
> > Rawhide. Thus there will still be a supported cockpit-kubernetes package for
> > ~ 1.5 more years.
>
> I think if it's going away and is already effectively unsupported, we
> should probably drop it from Fedora 29 as well.
I think that would be appropriate for the kubevirt part of the UI.
cockpit-kubernetes at large (Cluster dashboard and Image Registry) continues to
be supported for a while (it has to for downstream), so IMHO it's fine to stay
in Fedora 29. It won't get lots of new features, but we do investigate and fix bugs.
> We haven't actually *released* Beta, so there's an opportunity to remove it
> if we land the change today or early on Monday and get a Freeze Exception BZ
> approved. I can help with the latter process if this is the path we want to
> take.
OK, so I'll work on removing the kubevirt parts upstream, so that it won't be
contained any more in Wednesday's upstream release. I filed
https://bugzilla.redhat.com/show_bug.cgi?id=1629608 for tracking it in Fedora
29. How do I turn that into an exception BZ?
Actually, it turns out we don't need an exception BZ because
cockpit-kubernetes is not part of the default installation anyway. So
just land it in the updates-testing repo and it'll be fine.