Re: Starting to address backlog

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Mon, 30 Sep 2019 at 22:36, Stephen John Smoogen <smooge@xxxxxxxxx> wrote:
On Mon, 30 Sep 2019 at 16:22, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
>
> Greetings.
>
> A few weeks ago I went and tagged a bunch of old releng and
> infrastructure tickets with the 'backlog' tag. Clement added some more
> the other day.
>
> In our last meeting we did some simple voting on the list to determine
> priority.
>
> The idea is that we will take the top 1-3 per week and get small groups
> of people to work on them (at the very least one person can do the work
> and explain it to another to document/provide feedback on). Then at each
> meeting we look at the list, confirm what we did and take some more.
>
> Of course we have other priorities to deal with too, but focusing on a
> few tasks and trying to spread knowledge around them will hopefully get
> our backlog down over time.
>
> As a side note we are trying also with this copying these to an internal
> jira instance to see if we can track backlog flow better and figure out
> workflows, but this is purely a copy and pagure instances are where all
> the work and comments are done, so anyone not on the CPE team can ignore
> this for now. :)
>
> So, for this week we decided to work on:
>
> 8178 provision new aarch64 builders   xxxxxx
>
> I have this one, it takes access to get them setup, but I am happy to
> explain on IRC what I am doing and how the setup works. Assistance could
> be used to add them to ansible, as well as documentation if there's
> anything special about them. I intend to work on this tomorrow morning.
> I'll ping everyone in #fedora-admin on this who is interested.
>
> 8157 ansible: enable ansible-report as a hook   xxxxxx
>
> I'd love someone else to take this one. Any takers?
> I can provide pointers...

I can try to look at that, if anybody else wants to collaborate on that with me (apprentice ?) let me know :-)

Thanks for driving that Kevin.
 
>
> 8065 Move older koji builds to archive volumes   xxxxxx
>
> This is already in progress and has been for some time. I'd love to talk
> to others and explain how it's being done and get some documentation
> written up on it and others to know how to do it if I am not around.
> We could also use some discussion about how to split the koji volume a
> bit more. I might be able to work on this wed morning? Anyone interested
> in helping?
>
> Thanks and hopefully we can start cranking out some of this backlog
> now...

I am interested in taking this one.



--
Stephen J Smoogen.
_______________________________________________
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
_______________________________________________
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

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux