On Fri, Sep 4, 2020 at 7:18 AM Troy Dawson <tdawson@xxxxxxxxxx> wrote: > Step 1 - Approve plan via Steering Committee. > Step 1a - Documents and communication > -- No releng needed. > -- Should be done along the whole way > Step 2 - Update fedpkg and remove all package.cfg from epel8. > -- Can be done by a proven packagers, no releng needed. > Step 3 - Change the inheritance in koji so it inherits from epel8 > -- releng work > --- I don't know how easy / hard this will be for releng > Step 4 - Untag all the things that are "older" in playground > -- currently that is a releng process. There is no way for a > maintainer to retire their package from playground. > -- This needs to happen some time (3 months?) after step 2 is > finished. A time that we can see that people have manually built > their package in playground, versus the automatic builds. So that the > "older" packages are obvious. > -- If we do this as a huge batch, it should be a fairly simple (though > long) step for releng. > Step 5 - Send a daily report > -- Is this similar to what we send for EPEL6,7,8 ? > --- If this is true, I'm in favor of it. If not, then please explain more. > -- I have no idea about the work involved for this. > This plan has been approved by the Fedora Steering Committee. Thus Step 1 has been accomplished. Ya!!! We will start steps 1a and 2 next week. Step 4 - We will determine what "older" means, but right now I think Paul has the right idea that anything with the same NVR is both epel8 and epel8-playground is considered "older", or non-automated. Troy _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
