Re: CPE Weekly: 2020-04-26
On Tue, 5 May 2020 at 20:44, Stephen John Smoogen wrote: > > On Tue, 5 May 2020 at 13:59, Fabio Valentini wrote: > > > > On Tue, May 5, 2020 at 4:08 PM Leigh Griffin wrote: > > > > > > We have performed technical analysis at all stages, this is a deeper dive > > > from two perspectives. The first is in respect to the Council and FESCo > > > conversations for the proposed changes to ensure distgit functionality > > > moves through appropriate approval chains and we arrive at a > > > collaborative solution. The second is more technical questions to help > > > arrive at what work CPE needs to undertake and what Gitlab may be able to > > > provide be it tooling / plugin / support and so on. > > > > <...> > > > > > We could not perform the latter until we had arrived at a decision > > > > You keep saying that, but I still fail to understand: Why? > > > > Fabio > > > > This conversation is not going to get anywhere unless people ask > deeper questions than one word ones. Spell out what you wanted the > selection process to be and why you thought it was going to be that > method. Otherwise each side is going to give an answer which they > think satisfies 'why' and the other side is going to keep asking again > because it clearly wasn't what they wanted. It has been clearly asked by several people several times already: why do we need to wait for a decision to tackle more technical questions to know what work CPE needs to undertake and what GitLab may be able to provide? Several people consider that this deeper analysis is actually **needed** to take an informed decision. Otherwise, it's not hard to see how we may end up going forward against a bricked wall thanks to a decision impossible to fulfill. Iñaki Úcar ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Tue, 5 May 2020 at 13:59, Fabio Valentini wrote: > > On Tue, May 5, 2020 at 4:08 PM Leigh Griffin wrote: > > > > > > > > On Tue, May 5, 2020 at 10:55 AM Guido Aulisi wrote: > >> > >> Il giorno dom, 26/04/2020 alle 18.13 +0100, Aoife Moloney ha scritto: > >> > # CPE Weekly: 2020-04-26 > >> > --- > >> > title: CPE Weekly status email > >> > tags: CPE Weekly, email > >> > --- > >> > >> Hello, > >> > >> ... snip > >> > > >> > ## GitForge Updates > >> > * We will be tracking our progress here > >> > https://fedoraproject.org/wiki/Git_forge_update > >> > * Please be aware this does not contain any new information, as we > >> > don't have any to share yet. > >> > * However once we have more information for you, we will be posting > >> > it > >> > to the above link, and with the URL in the weekly emails for quick > >> > access. > >> > * We are currently doing a technical deep-dive with our own team on > >> > what we need from GitLab > >> > * We are also still engaging with Fedora Council who are tracking the > >> > Fedora Communities needs here > >> > https://pagure.io/Fedora-Council/tickets/issue/292 > >> > * And we are looking at ways to engage closer with the CentOS > >> > community too to share information as and when we have it > >> > * Public Q sessions are still being discussed to allow for open > >> > conversations in public forums too as we move through this journey, > >> > so > >> > thank you for your patience with us. > >> > >> So you are doing a technical deep-dive now after choosing Gitlab, not > >> before deciding? It's a very strange way to take decisions... > > > > > > We have performed technical analysis at all stages, this is a deeper dive > > from two perspectives. The first is in respect to the Council and FESCo > > conversations for the proposed changes to ensure distgit functionality > > moves through appropriate approval chains and we arrive at a collaborative > > solution. The second is more technical questions to help arrive at what > > work CPE needs to undertake and what Gitlab may be able to provide be it > > tooling / plugin / support and so on. > > <...> > > > We could not perform the latter until we had arrived at a decision > > You keep saying that, but I still fail to understand: Why? > > Fabio > This conversation is not going to get anywhere unless people ask deeper questions than one word ones. Spell out what you wanted the selection process to be and why you thought it was going to be that method. Otherwise each side is going to give an answer which they think satisfies 'why' and the other side is going to keep asking again because it clearly wasn't what they wanted. -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Tue, May 5, 2020, 18:52 Fabio Valentini wrote: > On Tue, May 5, 2020 at 4:08 PM Leigh Griffin wrote: > > > > > > > > On Tue, May 5, 2020 at 10:55 AM Guido Aulisi > wrote: > >> > >> Il giorno dom, 26/04/2020 alle 18.13 +0100, Aoife Moloney ha scritto: > >> > # CPE Weekly: 2020-04-26 > >> > --- > >> > title: CPE Weekly status email > >> > tags: CPE Weekly, email > >> > --- > >> > >> Hello, > >> > >> ... snip > >> > > >> > ## GitForge Updates > >> > * We will be tracking our progress here > >> > https://fedoraproject.org/wiki/Git_forge_update > >> > * Please be aware this does not contain any new information, as we > >> > don't have any to share yet. > >> > * However once we have more information for you, we will be posting > >> > it > >> > to the above link, and with the URL in the weekly emails for quick > >> > access. > >> > * We are currently doing a technical deep-dive with our own team on > >> > what we need from GitLab > >> > * We are also still engaging with Fedora Council who are tracking the > >> > Fedora Communities needs here > >> > https://pagure.io/Fedora-Council/tickets/issue/292 > >> > * And we are looking at ways to engage closer with the CentOS > >> > community too to share information as and when we have it > >> > * Public Q sessions are still being discussed to allow for open > >> > conversations in public forums too as we move through this journey, > >> > so > >> > thank you for your patience with us. > >> > >> So you are doing a technical deep-dive now after choosing Gitlab, not > >> before deciding? It's a very strange way to take decisions... > > > > > > We have performed technical analysis at all stages, this is a deeper > dive from two perspectives. The first is in respect to the Council and > FESCo conversations for the proposed changes to ensure distgit > functionality moves through appropriate approval chains and we arrive at a > collaborative solution. The second is more technical questions to help > arrive at what work CPE needs to undertake and what Gitlab may be able to > provide be it tooling / plugin / support and so on. > > <...> > > > We could not perform the latter until we had arrived at a decision > > You keep saying that, but I still fail to understand: Why? > To do so would have been to presuppose that Gitlab was the choice. > > Fabio > > > so we are now actively engaged there and a public facing ticket will be > available soon for the community to track. > >> > >> > >> I'd expect that the entire git forge discussion would start from the > >> beginning, because of the many mistakes that were made in this process. > >> > >> Sorry for my bad english... > >> > >> Guido Aulisi > >> > >> FAS: tartina > >> > >> ___ > >> devel mailing list -- devel@lists.fedoraproject.org > >> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > > > > > > > > -- > > > > Leigh Griffin > > > > Engineering Manager > > > > Red Hat Waterford > > > > Communications House > > > > Cork Road, Waterford City > > > > lgrif...@redhat.com > > M: +353877545162 IM: lgriffin > > > > @redhatjobs redhatjobs @redhatjobs > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Tue, May 5, 2020 at 4:08 PM Leigh Griffin wrote: > > > > On Tue, May 5, 2020 at 10:55 AM Guido Aulisi wrote: >> >> Il giorno dom, 26/04/2020 alle 18.13 +0100, Aoife Moloney ha scritto: >> > # CPE Weekly: 2020-04-26 >> > --- >> > title: CPE Weekly status email >> > tags: CPE Weekly, email >> > --- >> >> Hello, >> >> ... snip >> > >> > ## GitForge Updates >> > * We will be tracking our progress here >> > https://fedoraproject.org/wiki/Git_forge_update >> > * Please be aware this does not contain any new information, as we >> > don't have any to share yet. >> > * However once we have more information for you, we will be posting >> > it >> > to the above link, and with the URL in the weekly emails for quick >> > access. >> > * We are currently doing a technical deep-dive with our own team on >> > what we need from GitLab >> > * We are also still engaging with Fedora Council who are tracking the >> > Fedora Communities needs here >> > https://pagure.io/Fedora-Council/tickets/issue/292 >> > * And we are looking at ways to engage closer with the CentOS >> > community too to share information as and when we have it >> > * Public Q sessions are still being discussed to allow for open >> > conversations in public forums too as we move through this journey, >> > so >> > thank you for your patience with us. >> >> So you are doing a technical deep-dive now after choosing Gitlab, not >> before deciding? It's a very strange way to take decisions... > > > We have performed technical analysis at all stages, this is a deeper dive > from two perspectives. The first is in respect to the Council and FESCo > conversations for the proposed changes to ensure distgit functionality moves > through appropriate approval chains and we arrive at a collaborative > solution. The second is more technical questions to help arrive at what work > CPE needs to undertake and what Gitlab may be able to provide be it tooling / > plugin / support and so on. <...> > We could not perform the latter until we had arrived at a decision You keep saying that, but I still fail to understand: Why? Fabio > so we are now actively engaged there and a public facing ticket will be > available soon for the community to track. >> >> >> I'd expect that the entire git forge discussion would start from the >> beginning, because of the many mistakes that were made in this process. >> >> Sorry for my bad english... >> >> Guido Aulisi >> >> FAS: tartina >> >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > > > > -- > > Leigh Griffin > > Engineering Manager > > Red Hat Waterford > > Communications House > > Cork Road, Waterford City > > lgrif...@redhat.com > M: +353877545162 IM: lgriffin > > @redhatjobs redhatjobs @redhatjobs > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Tue, May 5, 2020 at 10:55 AM Guido Aulisi wrote: > Il giorno dom, 26/04/2020 alle 18.13 +0100, Aoife Moloney ha scritto: > > # CPE Weekly: 2020-04-26 > > --- > > title: CPE Weekly status email > > tags: CPE Weekly, email > > --- > > Hello, > > ... snip > > > > ## GitForge Updates > > * We will be tracking our progress here > > https://fedoraproject.org/wiki/Git_forge_update > > * Please be aware this does not contain any new information, as we > > don't have any to share yet. > > * However once we have more information for you, we will be posting > > it > > to the above link, and with the URL in the weekly emails for quick > > access. > > * We are currently doing a technical deep-dive with our own team on > > what we need from GitLab > > * We are also still engaging with Fedora Council who are tracking the > > Fedora Communities needs here > > https://pagure.io/Fedora-Council/tickets/issue/292 > > * And we are looking at ways to engage closer with the CentOS > > community too to share information as and when we have it > > * Public Q sessions are still being discussed to allow for open > > conversations in public forums too as we move through this journey, > > so > > thank you for your patience with us. > > So you are doing a technical deep-dive now after choosing Gitlab, not > before deciding? It's a very strange way to take decisions... > We have performed technical analysis at all stages, this is a deeper dive from two perspectives. The first is in respect to the Council and FESCo conversations for the proposed changes to ensure distgit functionality moves through appropriate approval chains and we arrive at a collaborative solution. The second is more technical questions to help arrive at what work CPE needs to undertake and what Gitlab may be able to provide be it tooling / plugin / support and so on. We could not perform the latter until we had arrived at a decision so we are now actively engaged there and a public facing ticket will be available soon for the community to track. > > I'd expect that the entire git forge discussion would start from the > beginning, because of the many mistakes that were made in this process. > > Sorry for my bad english... > > Guido Aulisi > > FAS: tartina > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > -- Leigh Griffin Engineering Manager Red Hat Waterford <https://www.redhat.com/> Communications House Cork Road, Waterford City lgrif...@redhat.com M: +353877545162 IM: lgriffin @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://red.ht/sig> ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
Il giorno dom, 26/04/2020 alle 18.13 +0100, Aoife Moloney ha scritto: > # CPE Weekly: 2020-04-26 > --- > title: CPE Weekly status email > tags: CPE Weekly, email > --- Hello, ... snip > > ## GitForge Updates > * We will be tracking our progress here > https://fedoraproject.org/wiki/Git_forge_update > * Please be aware this does not contain any new information, as we > don't have any to share yet. > * However once we have more information for you, we will be posting > it > to the above link, and with the URL in the weekly emails for quick > access. > * We are currently doing a technical deep-dive with our own team on > what we need from GitLab > * We are also still engaging with Fedora Council who are tracking the > Fedora Communities needs here > https://pagure.io/Fedora-Council/tickets/issue/292 > * And we are looking at ways to engage closer with the CentOS > community too to share information as and when we have it > * Public Q sessions are still being discussed to allow for open > conversations in public forums too as we move through this journey, > so > thank you for your patience with us. So you are doing a technical deep-dive now after choosing Gitlab, not before deciding? It's a very strange way to take decisions... I'd expect that the entire git forge discussion would start from the beginning, because of the many mistakes that were made in this process. Sorry for my bad english... Guido Aulisi FAS: tartina signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Mon, Apr 27, 2020 at 12:58:52AM +0200, Miro Hrončok wrote: > On 26. 04. 20 20:12, Pierre-Yves Chibon wrote: > > We know some people are happy with it and at least one person is not > > I hope you are not counting me as the not happy person. No, I actually included you in the first group :) > I am quite happy, but I just find that one tiny problem a blocker for me :D > > https://pagure.io/Fedora-Infra/rpmautospec/issue/107 I realize it's annoying to you in the current state of rpmautospec but Nils, Adam and I already chat a bit about this and we believe we can fix the situation so it's no longer a blocker. If the community deems our approach worthy of being pushed forward, we will ensure you get to use this ! Thanks for your feedback and support on this! Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Sun, Apr 26, 2020, at 11:12 PM, Kevin Fenzi wrote: > On Sun, Apr 26, 2020 at 08:47:51PM -0400, James Cassell wrote: > > > > What's Kojira? > > Its a process run by koji (The fedora buildsystem) that manages > buildroots. It keeps track of the buildroots that need regerenation, > makes sure not too many are regenerated at once and deleting old > builroot repos when they are no longer needed. > > If you build foo and need it in the buildroot to build bar, kojira is > the thing that notices foo built and that the buildroot needs updating, > fires off that update process (when resources are available for it). > Cool. Thanks for the explanation! (I'd never heard of it before.) V/r, James Cassell ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Sun, Apr 26, 2020 at 08:47:51PM -0400, James Cassell wrote: > > What's Kojira? Its a process run by koji (The fedora buildsystem) that manages buildroots. It keeps track of the buildroots that need regerenation, makes sure not too many are regenerated at once and deleting old builroot repos when they are no longer needed. If you build foo and need it in the buildroot to build bar, kojira is the thing that notices foo built and that the buildroot needs updating, fires off that update process (when resources are available for it). kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Sun, Apr 26, 2020, at 1:13 PM, Aoife Moloney wrote: > # CPE Weekly: 2020-04-26 > --- > title: CPE Weekly status email > tags: CPE Weekly, email > --- > > > > > Background: > The Community Platform Engineering group is the Red Hat team combining > IT and release engineering from Fedora and CentOS.Check out our teams > info here https://docs.fedoraproject.org/en-US/cpe/ > > > ## GitForge Updates > * We will be tracking our progress here > https://fedoraproject.org/wiki/Git_forge_update > * Please be aware this does not contain any new information, as we > don't have any to share yet. > * However once we have more information for you, we will be posting it > to the above link, and with the URL in the weekly emails for quick > access. > * We are currently doing a technical deep-dive with our own team on > what we need from GitLab > * We are also still engaging with Fedora Council who are tracking the > Fedora Communities needs here > https://pagure.io/Fedora-Council/tickets/issue/292 > * And we are looking at ways to engage closer with the CentOS > community too to share information as and when we have it > * Public Q sessions are still being discussed to allow for open > conversations in public forums too as we move through this journey, so > thank you for your patience with us. > > > > ## Fedora Updates > * F32 release is a Go! > * Estimated release date is April 28th - well done to everyone involved! > > > > > > ### Data Centre Move > * Due to Covid-19 restrictions at each datacentre, we have > unfortunately experienced a delay during the initial move. > * The need to push out our dates by 2-3 weeks was made necessary on > Thursday 23rd April, following meetings with Red Hat IT on network > connectivity status and estimate connection times for our team to > access the new datacentre. > * We will need to adjust our outage schedule and move schedule to > properly reflect the new dates of services being turned off and > reduced, and the full amended schedule will be published to hackmd, > with emails sent to the devel-announce & infra lists next week (week > ending 1st May) > * We will also include links to the updated move schedule and service > impact schedule in next weeks CPE Weekly > * Please be aware that CommuniShift is now down indefinitely until > earliest May 8th. > > > ### AAA Replacement > * The team have begun phase two of the project and you can view their > board for more technical information on their work here > https://github.com/orgs/fedora-infra/projects/6 > * They are doing amazing work :) > > > > > ### CI/CD > > * Monitor-gating is now running in production and has already caught a > couple of issues with bodhi (both in stg and in prod)! > * Rpmautospec > * In review as a Fedora package: > https://bugzilla.redhat.com/show_bug.cgi?id=1816124 > * Work progressing on Koji tagging plugin (post-build), full use > case support for bumping releases > * Plan is still to get it deployed in staging > > > > > > > > ### Sustaining Team > * Mbbox Upgrade > * Some progress on CRD for koji-builder and koji-hub components > * Bodhi 5.2.2 released > * Some issues with celery tasks, however rawhide monitoring super useful. > * Compose tracker enhancement > * Focusing on tagging issues, and having the ability to ping maintainers > > Odcs-backend-releng01 provision to enable testing in Fedora Minimal Compose > > * Infra > * The daily standup the team has has helped a lot with managing > infra tickets - they are down to 99 tickets! > * Mass update of stg and prod > * Please note you may experience some Kojira slowness What's Kojira? > * New review-stats application deployed - > (https://fedoraproject.org/PackageReviewStatus/) > > > > > > > ## CentOS Updates > > ### CentOS > * ppc64le and aarch64, 8 and 8-stream nodes now available in cico for > tenants to checkout. -- Email sent to ci-user list > * New signing for SIGs (through https://cbs.centos.org) live on 25th April > 2020 > > > > > > > > ### CentOS Stream > * Summit Videos took our attention this week > * We have a booth, so don't forget to register your attendance! > https://www.redhat.com/en/summit > * Qt5.12 pushed in response to an internal request > * NetworkManager re-imported > > > > > > > > > > > > > > > As always, feedback is welcome, and we will continue to look at ways > to improve the delivery and readability of this weekly report. > > > Have a great week ahead! > > Aoife >
Re: CPE Weekly: 2020-04-26
On 26. 04. 20 20:12, Pierre-Yves Chibon wrote: We know some people are happy with it and at least one person is not I hope you are not counting me as the not happy person. I am quite happy, but I just find that one tiny problem a blocker for me :D https://pagure.io/Fedora-Infra/rpmautospec/issue/107 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Re: CPE Weekly: 2020-04-26
On Sun, Apr 26, 2020 at 06:13:08PM +0100, Aoife Moloney wrote: > ### CI/CD > > * Monitor-gating is now running in production and has already caught a > couple of issues with bodhi (both in stg and in prod)! > * Rpmautospec > * In review as a Fedora package: > https://bugzilla.redhat.com/show_bug.cgi?id=1816124 > * Work progressing on Koji tagging plugin (post-build), full use > case support for bumping releases > * Plan is still to get it deployed in staging Looks like I forgot to remove this section from the original doc, my apologies for this. The CI/CD work on rpmautospec is what we announced a couple of weeks ago. It is deployed and running in staging and we're happy to gather feedback about its UX, performance, issues. We will likely reach out again when we start considering if this is worth moving forward. We know some people are happy with it and at least one person is not, so it will be up to the community to tell us if they want us to move ahead with our design or if they prefer another one. In the mean time, please have a look at it in staging and let us know if you run into issues with it. I'll make sure this section is removed from the next weekly email. Thanks, Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
CPE Weekly: 2020-04-26
# CPE Weekly: 2020-04-26 --- title: CPE Weekly status email tags: CPE Weekly, email --- Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS.Check out our teams info here https://docs.fedoraproject.org/en-US/cpe/ ## GitForge Updates * We will be tracking our progress here https://fedoraproject.org/wiki/Git_forge_update * Please be aware this does not contain any new information, as we don't have any to share yet. * However once we have more information for you, we will be posting it to the above link, and with the URL in the weekly emails for quick access. * We are currently doing a technical deep-dive with our own team on what we need from GitLab * We are also still engaging with Fedora Council who are tracking the Fedora Communities needs here https://pagure.io/Fedora-Council/tickets/issue/292 * And we are looking at ways to engage closer with the CentOS community too to share information as and when we have it * Public Q sessions are still being discussed to allow for open conversations in public forums too as we move through this journey, so thank you for your patience with us. ## Fedora Updates * F32 release is a Go! * Estimated release date is April 28th - well done to everyone involved! ### Data Centre Move * Due to Covid-19 restrictions at each datacentre, we have unfortunately experienced a delay during the initial move. * The need to push out our dates by 2-3 weeks was made necessary on Thursday 23rd April, following meetings with Red Hat IT on network connectivity status and estimate connection times for our team to access the new datacentre. * We will need to adjust our outage schedule and move schedule to properly reflect the new dates of services being turned off and reduced, and the full amended schedule will be published to hackmd, with emails sent to the devel-announce & infra lists next week (week ending 1st May) * We will also include links to the updated move schedule and service impact schedule in next weeks CPE Weekly * Please be aware that CommuniShift is now down indefinitely until earliest May 8th. ### AAA Replacement * The team have begun phase two of the project and you can view their board for more technical information on their work here https://github.com/orgs/fedora-infra/projects/6 * They are doing amazing work :) ### CI/CD * Monitor-gating is now running in production and has already caught a couple of issues with bodhi (both in stg and in prod)! * Rpmautospec * In review as a Fedora package: https://bugzilla.redhat.com/show_bug.cgi?id=1816124 * Work progressing on Koji tagging plugin (post-build), full use case support for bumping releases * Plan is still to get it deployed in staging ### Sustaining Team * Mbbox Upgrade * Some progress on CRD for koji-builder and koji-hub components * Bodhi 5.2.2 released * Some issues with celery tasks, however rawhide monitoring super useful. * Compose tracker enhancement * Focusing on tagging issues, and having the ability to ping maintainers Odcs-backend-releng01 provision to enable testing in Fedora Minimal Compose * Infra * The daily standup the team has has helped a lot with managing infra tickets - they are down to 99 tickets! * Mass update of stg and prod * Please note you may experience some Kojira slowness * New review-stats application deployed - (https://fedoraproject.org/PackageReviewStatus/) ## CentOS Updates ### CentOS * ppc64le and aarch64, 8 and 8-stream nodes now available in cico for tenants to checkout. -- Email sent to ci-user list * New signing for SIGs (through https://cbs.centos.org) live on 25th April 2020 ### CentOS Stream * Summit Videos took our attention this week * We have a booth, so don't forget to register your attendance! https://www.redhat.com/en/summit * Qt5.12 pushed in response to an internal request * NetworkManager re-imported As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great week ahead! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
