March 2020 - rel-eng - Fedora Mailing-Lists

[Fedocal] Reminder meeting : Fedora Release Engineering

by mohanboddu＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2020-03-31 from 11:00:00 to 12:00:00 US/Eastern At fedora-meeting-3(a)irc.freenode.net The meeting will be about: Fedora Release Engineering weekly meeting Source: https://apps.fedoraproject.org/calendar/meeting/9274/

4 years

1
0
0 / 0

Fedora Release Engineering Meeting Summary for 2020-03-24

by Mohan Boddu

====================================== #fedora-meeting-3: RELENG (2020-03-24) ====================================== Meeting started by mboddu at 15:01:38 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-3/2020-03-24/releng.2020... . Meeting summary --------------- * init process (mboddu, 15:01:39) * #9329 F33/Changes/MAKE43 (mboddu, 15:04:38) * LINK: https://pagure.io/releng/issue/9329 (mboddu, 15:04:44) * #9308 F33 system wide change: Sqlite Rpmdb (mboddu, 15:10:52) * LINK: https://pagure.io/releng/issue/9308 (mboddu, 15:10:58) * mboddu will comment on the ticket asking them to let us know when the work is done so that we can do some testing in staging. (mboddu, 15:21:30) * #9154 F32 Change: new buildroot for CPU baseline update (mboddu, 15:23:55) * LINK: https://pagure.io/releng/issue/9154 (mboddu, 15:24:01) * LINK: https://fedoraproject.org/wiki/Changes/ELN_Buildroot_and_Compose (nirik, 15:26:05) * #9336 Exception for epel8 branch for rpms/asio (mboddu, 15:29:01) * LINK: https://pagure.io/releng/issue/9336 (mboddu, 15:29:07) * mboddu will fix fedscm-admin and will leave fedpkg as is for now. People can file releng tickets and releng will manually fix them if this happens. Also, if there a huge load of tickets like this, we will look at how to fix it properly in fedpkg. (mboddu, 15:34:56) * #9267 aarch64 upgrade from branched release to rawhide fails (mboddu, 15:35:04) * LINK: https://pagure.io/releng/issue/9267 (mboddu, 15:35:12) * #9220 Failure to start build during mass rebuild (mboddu, 15:47:35) * LINK: https://pagure.io/releng/issue/9220 (mboddu, 15:47:41) * LINK: https://koji.fedoraproject.org/koji/taskinfo?taskID=41163489 (nirik, 15:56:16) * we have to check if any of packages in https://pagure.io/releng/issue/9220#comment-635220 did not build after mass rebuild and dont have ftbfs bug, then we need to add them to the ftbfs bug and ask the maintianers to build for f33 as well. (mboddu, 16:02:10) * Open Floor (mboddu, 16:05:37) * nirik updated all the builders over the weekend which upgraded mock to 2.1 and he downgraded it back to 1.4.21 (mboddu, 16:07:58) Meeting ended at 16:08:10 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mboddu (78) * nirik (51) * zodbot (7) * cverna (1) * jednorozec (0) * pbrobinson (0) * dustymabe (0) * pingou (0) * ksinny (0) * sharkcz (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

4 years

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora Release Engineering

by mohanboddu＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2020-03-24 from 11:00:00 to 12:00:00 US/Eastern At fedora-meeting-3(a)irc.freenode.net The meeting will be about: Fedora Release Engineering weekly meeting Source: https://apps.fedoraproject.org/calendar/meeting/9274/

4 years

1
0
0 / 0

[pungi-fedora] PR #817: update silverblue and workstation disk image configs for aarch64 and ppc64le

by Dan Horák

sharkcz opened a new pull-request against the project: `pungi-fedora` that you are following: `` update silverblue and workstation disk image configs for aarch64 and ppc64le `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/817

4 years, 1 month

2
1
0 / 0

[pungi-fedora] PR #808: https://fedoraproject.org/wiki/Changes/ARM_Release_Criteria_Changes

by Kevin Fenzi

kevin opened a new pull-request against the project: `pungi-fedora` that you are following: `` https://fedoraproject.org/wiki/Changes/ARM_Release_Criteria_Changes `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/808

4 years, 1 month

3
2
0 / 0

[pungi-fedora] PR #816: update silverblue and workstation disk image configs for aarch64 and ppc64le

by Dan Horák

sharkcz opened a new pull-request against the project: `pungi-fedora` that you are following: `` update silverblue and workstation disk image configs for aarch64 and ppc64le `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/816

4 years, 1 month

1
1
0 / 0

[pungi-fedora] PR #815: update silverblue and workstation disk image configs for aarch64 and ppc64le

by Dan Horák

sharkcz opened a new pull-request against the project: `pungi-fedora` that you are following: `` update silverblue and workstation disk image configs for aarch64 and ppc64le `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/815

4 years, 1 month

2
1
0 / 0

Fedora Release Engineering Meeting Summary for 2020-03-17

by Mohan Boddu

====================================== #fedora-meeting-3: RELENG (2020-03-17) ====================================== Meeting started by mboddu at 14:59:55 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-3/2020-03-17/releng.2020... . Meeting summary --------------- * init process (mboddu, 14:59:56) * #9320 Silverblue composes fail on aarch64 and ppc64le because it requires flatpaks (mboddu, 15:06:02) * LINK: https://pagure.io/releng/issue/9320 (mboddu, 15:06:07) * Since we are not building flatpaks for non x86_64 arches, we will remove flatpak config part of Silverblue in pungi configs of rawhide for aarch64 and ppc64le and see what happens. (mboddu, 15:14:24) * #9279 Workstation image fails for ppc64le due missing bcm283x-firmware (mboddu, 15:14:49) * LINK: https://pagure.io/releng/issue/9279 (mboddu, 15:14:55) * We decided not to make workstation disk images for ppc64le as it never worked and not used by anyone, we will still keep the live image available for workstation ppc64le. (mboddu, 15:29:55) * LINK: https://raptorcs.com/content/BK1B01/intro.html, preassembled system under $3k (sharkcz, 15:32:18) * #9169 Block unretirement commits (mboddu, 15:34:34) * LINK: https://pagure.io/releng/issue/9169 (mboddu, 15:34:41) * We fixed it using last day as the EOL in pdc. Closing the ticket as there is no better way to fix it. (mboddu, 15:38:32) * #9014 System Wide Change: Freeze after branching until compose is ready (mboddu, 15:42:39) * https://pagure.io/releng/issue/9014 (mboddu, 15:42:46) * Open Floor (mboddu, 15:48:48) * Fedora 32 Beta is out (mboddu, 15:48:58) Meeting ended at 15:55:28 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mboddu (54) * sharkcz (28) * nirik (15) * zodbot (7) * cverna (1) * jednorozec (0) * pbrobinson (0) * dustymabe (0) * pingou (0) * ksinny (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

4 years, 1 month

1
0
0 / 0

[Fedocal] Reminder meeting : Fedora Release Engineering

by mohanboddu＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2020-03-17 from 11:00:00 to 12:00:00 US/Eastern At fedora-meeting-3(a)irc.freenode.net The meeting will be about: Fedora Release Engineering weekly meeting Source: https://apps.fedoraproject.org/calendar/meeting/9274/

4 years, 1 month

1
0
0 / 0

COVID-19 contingency plans for infra and release engineering

by Ben Cotton

Hi teams, As many of you already know, Red Hat has asked all employees to work from home. I know that many (most?) of you don't work from a Red Hat office normally (particularly if you're not a Red Hat employee!), but I want to check on the impact that an extended shutdown might have on the infrastructure, particularly the release engineering activities as we approach the Fedora 32 GA (currently scheduled for 21 April). In addition, what are our personnel risks? For example, if Mohan gets too sick to work, do we have enough shared knowledge and access to cut a release? Obviously, everyone is going to be impacted in some way, even if none of us get sick. This is a stressful and uncertain time. I've made it clear to Fedora and Red Hat leadership that we will continue with the schedule, but that the priority is the health of our community members. I don't want anyone working beyond what's reasonable for their personal situation. I just need to understand the risks so we can make plans to mitigate them or adjust the release schedule. Thanks, BC -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

4 years, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng March 2020