Re: Backlog prioritization
Thanks Pierre!! On Mon, May 4, 2020 at 11:09 AM Pierre-Yves Chibon wrote: > On Fri, Apr 17, 2020 at 11:53:34AM +0200, Pierre-Yves Chibon wrote: > > 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-git21 47 > > stg.pagure to RHEL8 14 27 > > Packager sync to BZ 32 16 > > Retire packages in BZ 45 5 14 > > Mirror ansible to pagure43 3 10 > > > > *to sort in ascending order > > A small update of where things are: > > > Packager sync to BZ > > - I've migrated the current script away from FAS and in doing so learned > that > the issue may not be coming from that script but from a bug in bugzilla > itself. So when bugzilla is fixed, well the old script may start working > again > :) > The new script can be ported to nogging when we move to it. > > > stg.pagure to RHEL8 > > Done, we should look at src.stg now. > > > BZ overrides on dist-git (since it needs to wait for after freeze) > > Freeze being now over, I'm thinking to tackle this this week > > > Retire packages in BZ > > Done > > > Mirror ansible to pagure > > Done as of this week-end, thanks Kevin! > > > Pierre > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct:
Re: Backlog prioritization
On Fri, Apr 17, 2020 at 11:53:34AM +0200, Pierre-Yves Chibon wrote: > 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-git21 47 > stg.pagure to RHEL8 14 27 > Packager sync to BZ 32 16 > Retire packages in BZ 45 5 14 > Mirror ansible to pagure43 3 10 > > *to sort in ascending order A small update of where things are: > Packager sync to BZ - I've migrated the current script away from FAS and in doing so learned that the issue may not be coming from that script but from a bug in bugzilla itself. So when bugzilla is fixed, well the old script may start working again :) The new script can be ported to nogging when we move to it. > stg.pagure to RHEL8 Done, we should look at src.stg now. > BZ overrides on dist-git (since it needs to wait for after freeze) Freeze being now over, I'm thinking to tackle this this week > Retire packages in BZ Done > Mirror ansible to pagure Done as of this week-end, thanks Kevin! Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Mon, Apr 20, 2020 at 09:48:45AM +0100, Mark O'Brien wrote: >I would like to work on this today if possible. Obviously I'm not very >familiar with the system so may slow you down a little but it would be >good to get hands on with it. Let's go this this afternoon then, we can sync on #fedora-admin if you're ok with this :) The agenda should be something like: - Backup: DB, git repos, releases - Move backups to safe place (the batcave) - Destroy current instance - Rebuild it as RHEL8 (adjust playbook where needed) - Reload backups - Figure out remaining fires Pretty straight forward :) Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
I would like to work on this today if possible. Obviously I'm not very familiar with the system so may slow you down a little but it would be good to get hands on with it. Mark On Sun, Apr 19, 2020 at 7:20 PM Pierre-Yves Chibon wrote: > On Fri, Apr 17, 2020 at 02:13:36PM -0700, Kevin Fenzi wrote: > > On Fri, Apr 17, 2020 at 11:40:25AM +0200, Pierre-Yves Chibon wrote: > > > On Fri, Apr 17, 2020 at 09:03:02AM +0200, Clement Verna wrote: > > > > > * Migrate [6]stg.pagure.io and [7]src.stg.fedoraproject.org > to RHEL8. > > > > > While we're in freeze, I figure this is a good time to do > this. We > > > > could do > > > > > [8]pagure.io post-freeze and wait to do src.fp.o when it > gets > > > > reinstalled in the > > > > > new data-center. > > > > > > > > Yeah, good to do. I was going to ask you about this the other > day. > > > > Perhaps I could reinstall stg pagure with rhel8 some day my > night and > > > > you could take over your next morning with reloading the old > data/etc? > > > > > > > > I agree it's a good time to do it. > > > > > > > > Perhaps monday night I could try and do it and you could work > on it > > > > tuesday morning? > > > > > > > >That could be also a good first issue for Mark to work on with > pingou on > > > >it since timezone will make that easier :-) > > > >What do you think ? > > > > > > That sounds good to me :) > > > > ok, so monday night I would: > > > > * take down pagure-stg > > * spin up a new rhel8 based one. > > * run the playbook as far as it will easily go > > * copy a dump of the database and the old data to the new vm? > > * let pingou and mark look at bringing it up the rest of the way > > > > Do we want to save the old data? I guess it would be good to make sure > > it all works before we do it in prod? Or do we want to just start out > > with a new clean one? > > > > Or do you want me to just step back here and you two can do the entire > > thing? (Thats just fine with me too). > > I'll let Mark answer there, but I'm fine with doing the entire procedure > (which > mean, we could start on this on directly Monday). > > Mark, any preferences? > > > Pierre > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Fri, Apr 17, 2020 at 02:13:36PM -0700, Kevin Fenzi wrote: > On Fri, Apr 17, 2020 at 11:40:25AM +0200, Pierre-Yves Chibon wrote: > > On Fri, Apr 17, 2020 at 09:03:02AM +0200, Clement Verna wrote: > > > > * Migrate [6]stg.pagure.io and [7]src.stg.fedoraproject.org to > > > RHEL8. > > > > While we're in freeze, I figure this is a good time to do this. > > > We > > > could do > > > > [8]pagure.io post-freeze and wait to do src.fp.o when it gets > > > reinstalled in the > > > > new data-center. > > > > > > Yeah, good to do. I was going to ask you about this the other day. > > > Perhaps I could reinstall stg pagure with rhel8 some day my night and > > > you could take over your next morning with reloading the old > > > data/etc? > > > > > > I agree it's a good time to do it. > > > > > > Perhaps monday night I could try and do it and you could work on it > > > tuesday morning? > > > > > >That could be also a good first issue for Mark to work on with pingou > > > on > > >it since timezone will make that easier :-) > > >What do you think ? > > > > That sounds good to me :) > > ok, so monday night I would: > > * take down pagure-stg > * spin up a new rhel8 based one. > * run the playbook as far as it will easily go > * copy a dump of the database and the old data to the new vm? > * let pingou and mark look at bringing it up the rest of the way > > Do we want to save the old data? I guess it would be good to make sure > it all works before we do it in prod? Or do we want to just start out > with a new clean one? > > Or do you want me to just step back here and you two can do the entire > thing? (Thats just fine with me too). I'll let Mark answer there, but I'm fine with doing the entire procedure (which mean, we could start on this on directly Monday). Mark, any preferences? Pierre signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Fri, Apr 17, 2020 at 11:40:25AM +0200, Pierre-Yves Chibon wrote: > On Fri, Apr 17, 2020 at 09:03:02AM +0200, Clement Verna wrote: > > > * Migrate [6]stg.pagure.io and [7]src.stg.fedoraproject.org to RHEL8. > > > While we're in freeze, I figure this is a good time to do this. We > > could do > > > [8]pagure.io post-freeze and wait to do src.fp.o when it gets > > reinstalled in the > > > new data-center. > > > > Yeah, good to do. I was going to ask you about this the other day. > > Perhaps I could reinstall stg pagure with rhel8 some day my night and > > you could take over your next morning with reloading the old data/etc? > > > > I agree it's a good time to do it. > > > > Perhaps monday night I could try and do it and you could work on it > > tuesday morning? > > > >That could be also a good first issue for Mark to work on with pingou on > >it since timezone will make that easier :-) > >What do you think ? > > That sounds good to me :) ok, so monday night I would: * take down pagure-stg * spin up a new rhel8 based one. * run the playbook as far as it will easily go * copy a dump of the database and the old data to the new vm? * let pingou and mark look at bringing it up the rest of the way Do we want to save the old data? I guess it would be good to make sure it all works before we do it in prod? Or do we want to just start out with a new clean one? Or do you want me to just step back here and you two can do the entire thing? (Thats just fine with me too). kevin signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
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-git21 47 stg.pagure to RHEL8 14 27 Packager sync to BZ 32 16 Retire packages in BZ 45 5 14 Mirror ansible to pagure43 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@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Thu, Apr 16, 2020 at 09:31:55AM -0400, Ben Cotton wrote: > Here's my ranking in descending order, and ignoring the fact that > we're in an infra freeze: > > > * Finish bringing bugzilla overrides to dist-git (not FBR-worthy, IMO, but > > I'll let y'all make that decision) > > * Reworkd the packager sync from FAS to bugzilla > > * Mirror the ansible git repo on pagure.io > > * Migrate stg.pagure.io and src.stg.fedoraproject.org to RHEL8. > > * Finish retiring in bugzilla packages that are retired in Fedora (if you > > have a list, I can do that manually during meetings and stuff. It makes me > > feel useful ;-) ) We don't have a list actually :( My idea is to include this in the script that sync dist-git info to BZ since it already checks for orphaned and retired packages. Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Fri, Apr 17, 2020 at 09:03:02AM +0200, Clement Verna wrote: >On Thu, 16 Apr 2020 at 22:43, Kevin Fenzi <[1]ke...@scrye.com> wrote: > > 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 :) > > Thanks for this pingou! :) > > Perhaps we should all try and do this at the beginning of the week or > something. :) > > > * 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). > > This is a good one. > > > > * 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 [2]https://pagure.io/fedora-infrastructure/issue/8628 > > This one I just had to manually fix 2 users. It's going to be an ongoing > source of pain. ;( > > > * 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 [3]https://pagure.io/fedora-infrastructure/issue/7639 > > This would be nice, but we have done without it for a long time, so more > shouldn't hurt too much. :) > > > > > * Mirror the ansible git repo on [4]pagure.io > > I'd like to set up a mirror on [5]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. > > I think we should just bite the bullet and move the repo to pagure if we > can get a nice way to sync it back to batcave01 for actually running > playbooks there. > > I know I have been holdinng off on this related to the gitforge stuff, > and it likely will mean that we have to move it again sometime, but so > what. I think it's worth it to have. > > Lets set aside a time and make this happen. :) > I guess after freeze. > > > * Migrate [6]stg.pagure.io and [7]src.stg.fedoraproject.org to RHEL8. > > While we're in freeze, I figure this is a good time to do this. We > could do > > [8]pagure.io post-freeze and wait to do src.fp.o when it gets > reinstalled in the > > new data-center. > > Yeah, good to do. I was going to ask you about this the other day. > Perhaps I could reinstall stg pagure with rhel8 some day my night and > you could take over your next morning with reloading the old data/etc? > > I agree it's a good time to do it. > > Perhaps monday night I could try and do it and you could work on it > tuesday morning? > >That could be also a good first issue for Mark to work on with pingou on >it since timezone will make that easier :-) >What do you think ? That sounds good to me :) Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
Re: Backlog prioritization
On Thu, 16 Apr 2020 at 22:43, Kevin Fenzi wrote: > 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 :) > > Thanks for this pingou! :) > > Perhaps we should all try and do this at the beginning of the week or > something. :) > > > * 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). > > This is a good one. > > > > * 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 > > This one I just had to manually fix 2 users. It's going to be an ongoing > source of pain. ;( > > > * 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 > > This would be nice, but we have done without it for a long time, so more > shouldn't hurt too much. :) > > > > > * 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. > > I think we should just bite the bullet and move the repo to pagure if we > can get a nice way to sync it back to batcave01 for actually running > playbooks there. > > I know I have been holdinng off on this related to the gitforge stuff, > and it likely will mean that we have to move it again sometime, but so > what. I think it's worth it to have. > > Lets set aside a time and make this happen. :) > I guess after freeze. > > > * 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. > > Yeah, good to do. I was going to ask you about this the other day. > Perhaps I could reinstall stg pagure with rhel8 some day my night and > you could take over your next morning with reloading the old data/etc? > > I agree it's a good time to do it. > > Perhaps monday night I could try and do it and you could work on it > tuesday morning? > That could be also a good first issue for Mark to work on with pingou on it since timezone will make that easier :-) What do you think ? > > > > > So here you go, let me know what you think :) > > My order: > > packager perms sync to bugzilla > pagure to rhel8 > mirror ansible repo (after freeze) > bugzilla overrides in pagure > retired packages closed to bugs > > kevin > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
Re: Backlog prioritization
On Thu, Apr 16, 2020 at 7:03 PM Adam Williamson wrote: > > On Thu, 2020-04-16 at 13:33 -0700, Kevin Fenzi wrote: > > > > > * 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. > > > > I think we should just bite the bullet and move the repo to pagure if we > > can get a nice way to sync it back to batcave01 for actually running > > playbooks there. > > > > I know I have been holdinng off on this related to the gitforge stuff, > > and it likely will mean that we have to move it again sometime, but so > > what. I think it's worth it to have. > > + > > especially if we can then set up some CI that at least checks PRs are > syntactically sound and stuff (should not be hard to at least set up a > job that runs a YAML syntax checker over it). That would save ever so > many brown-paper-bag commits...:P And pagure.io isn't going anywhere, so it's not going to be a problem to have it there anyway. :) -- 真実はいつも一つ！/ Always, there's only one truth! ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Thu, 2020-04-16 at 13:33 -0700, Kevin Fenzi wrote: > > > * 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. > > I think we should just bite the bullet and move the repo to pagure if we > can get a nice way to sync it back to batcave01 for actually running > playbooks there. > > I know I have been holdinng off on this related to the gitforge stuff, > and it likely will mean that we have to move it again sometime, but so > what. I think it's worth it to have. + especially if we can then set up some CI that at least checks PRs are syntactically sound and stuff (should not be hard to at least set up a job that runs a YAML syntax checker over it). That would save ever so many brown-paper-bag commits...:P -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
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 :) Thanks for this pingou! :) Perhaps we should all try and do this at the beginning of the week or something. :) > * 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). This is a good one. > > * 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 This one I just had to manually fix 2 users. It's going to be an ongoing source of pain. ;( > * 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 This would be nice, but we have done without it for a long time, so more shouldn't hurt too much. :) > > * 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. I think we should just bite the bullet and move the repo to pagure if we can get a nice way to sync it back to batcave01 for actually running playbooks there. I know I have been holdinng off on this related to the gitforge stuff, and it likely will mean that we have to move it again sometime, but so what. I think it's worth it to have. Lets set aside a time and make this happen. :) I guess after freeze. > * 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. Yeah, good to do. I was going to ask you about this the other day. Perhaps I could reinstall stg pagure with rhel8 some day my night and you could take over your next morning with reloading the old data/etc? I agree it's a good time to do it. Perhaps monday night I could try and do it and you could work on it tuesday morning? > > So here you go, let me know what you think :) My order: packager perms sync to bugzilla pagure to rhel8 mirror ansible repo (after freeze) bugzilla overrides in pagure retired packages closed to bugs kevin signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Thu, Apr 16, 2020 at 11:04 AM Clement Verna wrote: > > * Mirror the ansible git repo on [4]pagure.io > Trouble: Low > Gain: Low > > Since that would not allow PRs I think the gain is quite low, but it also > seems like not much trouble to do it. > We could upgrade the Gain to High if we configured the repo to push mirror back to the old location and just changed the canonical source to pagure.io. > * Migrate [6]stg.pagure.io and [7]src.stg.fedoraproject.org to RHEL8. > Trouble: Low > Gain: Medium > > I think that would be rather low trouble (destroying the current instances > and rebuilding on RHEL8) but that would give us an opportunity to test that > before the move and then maybe give us the confidence to reinstall dist-git > on RHEL8 in the new data centre. > I'd personally like to see if everything works. :) -- 真実はいつも一つ！/ Always, there's only one truth! ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Thu, 16 Apr 2020 at 15:28, Pierre-Yves Chibon wrote: > On Thu, Apr 16, 2020 at 03:16:29PM +0200, Clement Verna wrote: > >Should we use the same prioritization category that we have for > tickets ? > >(low-gain, medium-gain, high-gain, low-trouble, medium-trouble, > >high-trouble). That might give use a nice way to focus on 1 or 2 > things > >:-) > >Thoughts ? > > That or plain 1, 2, 3, 4 works for me :) > So here is my gain vs trouble thingy * Finish bringing bugzilla overrides to dist-git Trouble : Medium Gain: High There seems to be quite a few steps to be done, plus the need for an FBR so medium troubles, but it would be obviously a high gain in terms of user experience. * Rework the packager sync from FAS to bugzilla Trouble : Medium Gain: Medium I would put this as Medium in both Trouble and Gain since it looks like what we currently have works but we have a better way of doing things now :-). * Finish retiring in bugzilla packages that are retired in Fedora Trouble : Low Gain: Low Does not seems like this is much work to be done but I don't know how much value we will get from it too. * Mirror the ansible git repo on [4]pagure.io Trouble: Low Gain: Low Since that would not allow PRs I think the gain is quite low, but it also seems like not much trouble to do it. * Migrate [6]stg.pagure.io and [7]src.stg.fedoraproject.org to RHEL8. Trouble: Low Gain: Medium I think that would be rather low trouble (destroying the current instances and rebuilding on RHEL8) but that would give us an opportunity to test that before the move and then maybe give us the confidence to reinstall dist-git on RHEL8 in the new data centre. just my 2cents :-) > Some are easier to do than others, but there isn't any that is very high > trouble > I think. > > > Pierre > > >On Thu, 16 Apr 2020 at 15:08, Pierre-Yves Chibon <[1] > pin...@pingoured.fr> > >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 [2]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 [3]https://pagure.io/fedora-infrastructure/issue/7639 > > > > * Mirror the ansible git repo on [4]pagure.io > >I'd like to set up a mirror on [5]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 [6]stg.pagure.io and [7]src.stg.fedoraproject.org to > RHEL8. > >While we're in freeze, I figure this is a good time to do this. We > > could do > >[8]pagure.io post-freeze and wait to do src.fp.o when it gets > > reinstalled
Re: Backlog prioritization
Here's my ranking in descending order, and ignoring the fact that we're in an infra freeze: > * Finish bringing bugzilla overrides to dist-git (not FBR-worthy, IMO, but > I'll let y'all make that decision) > * Reworkd the packager sync from FAS to bugzilla > * Mirror the ansible git repo on pagure.io > * Migrate stg.pagure.io and src.stg.fedoraproject.org to RHEL8. > * Finish retiring in bugzilla packages that are retired in Fedora (if you > have a list, I can do that manually during meetings and stuff. It makes me > feel useful ;-) ) -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Backlog prioritization
On Thu, Apr 16, 2020 at 03:16:29PM +0200, Clement Verna wrote: >Should we use the same prioritization category that we have for tickets ? >(low-gain, medium-gain, high-gain, low-trouble, medium-trouble, >high-trouble). That might give use a nice way to focus on 1 or 2 things >:-) >Thoughts ? That or plain 1, 2, 3, 4 works for me :) Some are easier to do than others, but there isn't any that is very high trouble I think. Pierre >On Thu, 16 Apr 2020 at 15:08, Pierre-Yves Chibon <[1]pin...@pingoured.fr> >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 [2]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 [3]https://pagure.io/fedora-infrastructure/issue/7639 > > * Mirror the ansible git repo on [4]pagure.io > I'd like to set up a mirror on [5]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 [6]stg.pagure.io and [7]src.stg.fedoraproject.org to RHEL8. > While we're in freeze, I figure this is a good time to do this. We > could do > [8]pagure.io post-freeze and wait to do src.fp.o when it gets > reinstalled in the > new data-center. > > So here you go, let me know what you think :) > > Thanks, > Pierre > ___ > infrastructure mailing list -- [9]infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > [10]infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct: > [11]https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: > [12]https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > > [13]https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > > Links: > 1. mailto:pin...@pingoured.fr/ > 2. https://pagure.io/fedora-infrastructure/issue/8628 > 3. https://pagure.io/fedora-infrastructure/issue/7639 > 4. http://pagure.io/ > 5. http://pagure.io/ > 6. http://stg.pagure.io/ > 7. http://src.stg.fedoraproject.org/ > 8. http://pagure.io/ > 9. mailto:infrastructure@lists.fedoraproject.org/ > 10. mailto:infrastructure-le...@lists.fedoraproject.org/ > 11. https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > 12. https://fedoraproject.org/wiki/Mailing_list_guidelines > 13. > https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org > Fedora Code of Conduct:
Re: Backlog prioritization
Should we use the same prioritization category that we have for tickets ? (low-gain, medium-gain, high-gain, low-trouble, medium-trouble, high-trouble). That might give use a nice way to focus on 1 or 2 things :-) Thoughts ? On Thu, 16 Apr 2020 at 15:08, 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 here you go, let me know what you think :) > > > Thanks, > Pierre > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
