On Fri, Sep 04, 2020 at 07:18:31AM -0700, Troy Dawson wrote: ...snipp.... > 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. I was thinking like the report that rawhide/branched composes send to the devel/test lists. So, basically that the compose happened and showing what updated, etc. I think that shouldn't be much work, but... we may need to do some work to make it not send if nothing has changed (which we should/could also reuse for branched). > I think Step 5 is a very important step (if I'm understanding it > correctly). Because it will give us a good idea about how many people > are utilizing playground. well, no, it will just make it more visible when packages in playground change. For usage, thats another thing... we should look at the new dnf counting that fedora is doing and see if we can use that with at least epel8... but thats another seperate project I guess. > > I think Step 3, changing the inheritance is the only change in the > work involved for releng. We would be changing the inheritance, > instead of deleting it. I don't know how much extra work that will > be. Should just be a few commands. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
