On Thu, Apr 16, 2020 at 03:01:35PM +0200, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > I have a few items in my backlog that I'd like to discuss priorities with you, > so here is the unsorted list, let me know how you would sort it :) > > * Finish bringing bugzilla overrides to dist-git > means: > - Deploy pagure 5.9.x to src.fp.o > - Migrate the data from the scm-requests repo to dist-git > - Adjust the README of the scm-requests repo > - Close off the scm-requests repo to pull-requests > - Announce & profit/watch the world burn > Blocked by the current freeze, unless a FBR is acceptable to upgrade pagure > to 5.9.x (knowing that 5.9.x does not bring any DB changes). > > * Reworkd the packager sync from FAS to bugzilla > Currently, there is a cron job that adds bugzilla privileges to people that > are added to the packager group. That cron relies on a DB in FAS that tracks > people being added or removed from this group. This isn't quite the 2020 way > of doing things and this will not be portable to noggin (the next gen FAS). > Python-bugzilla also recently (it's merged but not released) gained support > for groups, so we can finally do something like: ask FAS for all the packagers > and their email, list all the people in the corresponding group in bugzilla, > do a diff and add/remove accordingly. > fixes https://pagure.io/fedora-infrastructure/issue/8628 > > * Finish retiring in bugzilla packages that are retired in Fedora (ie: close > these components to new bugs in bugzilla). > This was blocked on a change in bugzilla which has been deployed in the last > release. So we should be able to proceed and adjust our bugzilla<->dist-git > sync script to do this. > fixes https://pagure.io/fedora-infrastructure/issue/7639 > > * Mirror the ansible git repo on pagure.io > I'd like to set up a mirror on pagure.io that would pull from batcave01. It > would mean that PR can't really be merged in this mirror (unless we're fast > enough to pull from the mirror and push to the main repo right after the merge, > but there is a risk of a race-condition where the commit(s) just merged are > overridden by a push to the main repo). > It would expose a more up to date ansible repo to the public and we should be > able to wget the patch of the PRs, git am to apply them and git push to the > main repo. > > * Migrate stg.pagure.io and src.stg.fedoraproject.org to RHEL8. > While we're in freeze, I figure this is a good time to do this. We could do > pagure.io post-freeze and wait to do src.fp.o when it gets reinstalled in the > new data-center. So this is the order I deduced from the responses: Clément Ben Kevin Total* BZ overrides on dist-git 2 1 4 7 stg.pagure to RHEL8 1 4 2 7 Packager sync to BZ 3 2 1 6 Retire packages in BZ 4 5 5 14 Mirror ansible to pagure 4 3 3 10 *to sort in ascending order So it looks like the order is: Packager sync to BZ stg.pagure to RHEL8 BZ overrides on dist-git (since it needs to wait for after freeze) Retire packages in BZ Mirror ansible to pagure Since we have the opportunity do do pagure on RHEL8 early next week we'll invert the first two. Thanks for your input everyone, I know what I'll be working on next week! :) Pierre _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
