======================================
#fedora-meeting-3: RELENG (2020-04-21)
======================================
Meeting started by mboddu at 15:02:56 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-3/2020-04-21/releng.2020-0…
.
Meeting summary
---------------
* init process (mboddu, 15:02:56)
* #9408 Tag ghc into EPEL8 buildroot for ghc bootstrap (mboddu,
15:06:00)
* LINK: https://pagure.io/releng/issue/9408 (mboddu, 15:06:07)
* nirik will check with rhel folks to figure out how we can get the
ghc builds that are used in rhel buildroot (mboddu, 15:16:16)
* #7265 blender git repo contains large files causing git checkout to
timeout during builds (mboddu, 15:16:47)
* LINK: https://pagure.io/releng/issue/7265 (mboddu, 15:16:53)
* LINK:
https://meetbot-raw.fedoraproject.org/teams/fesco/fesco.2018-03-02-15.00.lo…
(nirik, 15:27:05)
* mboddu commented on the ticket with the meeting minutes from
https://meetbot-raw.fedoraproject.org/teams/fesco/fesco.2018-03-02-15.00.lo…
and asked chruchyard if he is still interested in helping us
(mboddu, 15:30:31)
* #8948 Update list of critpath packages (mboddu, 15:31:42)
* LINK: https://pagure.io/releng/issue/8948 (mboddu, 15:31:48)
* we will deploy this on pdc-backend01 and run it as part of cron
everyday (mboddu, 15:34:50)
* #8879 Create pungi config for Rawhide/F32 ursa prime buildroot
(mboddu, 15:37:12)
* LINK: https://pagure.io/releng/issue/8879 (mboddu, 15:37:18)
* Open Floor (mboddu, 15:46:37)
* RC 1.4 is done and we found couple more issues, maybe we need to run
another RC (mboddu, 15:47:03)
* Now releng repo has *only* 99 tickets (mboddu, 15:59:45)
Meeting ended at 16:00:09 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (78)
* nirik (38)
* jkaluza (18)
* zodbot (7)
* sgallagh (3)
* jednorozec (0)
* pbrobinson (0)
* dustymabe (0)
* pingou (0)
* ksinny (0)
* sharkcz (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
jkaluza opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Use Rawhide module-defaults for ELN composes.
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/830
jkaluza opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Use comps-rawhide.xml for ELN composes.
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/829
Hi all,
I wanted to start a discussion and possibly some work around automating the
manual tasks involved in the release engineering work.
In particular I have in mind the following tasks :
- processing the unretire package tickets.
- processing the requests for a new package or a new branch.
- container base image release.
Instead of looking at each of these individually I was thinking that it
might be interesting to look at having an automation framework or something
like a bot that could be flexible enough to add more tasks or process in
the future.
To do that we have different possibilities, one could be to build a bot
that has a similar architecture than the compose-tracker (
https://pagure.io/releng/compose-tracker) ie a fedora-messaging consumer
processing messages.
Another option is to use loopabull (https://github.com/maxamillion/loopabull)
to trigger ansible playbook on fedora-messaging messages.
Both solutions are quite similar, but one (loopabull) provides already the
boilerplate to trigger a script or a function based on messages received (a
bit like AWS lambda or other serverless framework). We also have already a
few process automated that way (
https://pagure.io/Fedora-Infra/loopabull-tasks)
So I believe that using loopabull might be the best way forward, but I
would be interested to hear about other ideas :-)
Now if we look at the tasks to automate, I was thinking that we could
implement that automation in different phases :
*un-retiring tickets*:
- First step would be to run automatically the check-unretirement script
(https://pagure.io/releng/blob/master/f/scripts/check-unretirement.py)
and redirect its output into the ticket comments. That way people
processing the ticket have all the information available in the ticket.
- Second step would be to process automatically the tickets that do not
require a new bz review (retired less than 8 weeks ago)
- Finally see if we can process automatically all the tickets.
*creating new dist-git repo or branches:*
- Idea here would be to run the fedscm-admin (
https://pagure.io/fedscm-admin) cli automatically when a new ticket is
created here (https://pagure.io/releng/fedora-scm-requests)
*container base image release:*
- Instead of building the image every night, we could rebuild the image
only when at least 1 package present in the base image has been updated.
- Push the image weekly to the registry if a build happened during that
week.
Again here are some ideas, and I would very much appreciate feedback or
other ideas :-). Also if you think about another process that could be
automated that way please share it :-).
Thanks
Clément
kalev opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Add file-roller flatpak to Silverblue
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/826
mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Setup for F32 Final 1.4
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/828
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2020-04-21 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/
kalev opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Add file-roller flatpak to Silverblue
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/825
jkaluza opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Add initial ELN Pungi configuration.
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/827
The release status of Fedora 32 Final is no-go..
Due to open blocker bugs, Fedora 32 Final was declared "no-go". We
will reconvene at 1700 UTC on Thursday, 23 April[1] to re-evaluate.
If we determine at that time that Fedora 32 is go, it will release on
the "target release date #1" of 28 April.
For more information, please see the minutes[2] from the Fedora 32
Final Go/No-Go meeting.
[1] https://apps.fedoraproject.org/calendar/meeting/9738/
[2] https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-16/f32-final-go_…
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis