rel-eng April 2021

rel-eng@lists.fedoraproject.org

3 participants
18 discussions

[pungi-fedora] PR #846: Use compose-create-legacy-composeinfo to generate .composeinfo file
by Mohan Boddu 11 Nov '21

11 Nov '21

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Use compose-create-legacy-composeinfo to generate .composeinfo file `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/846

4 7

[pungi-fedora] PR #777: Config and script to generate modular build repos using overrides
by Mohan Boddu 11 Nov '21

11 Nov '21

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Config and script to generate modular build repos using overrides `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/777

4 5

[pungi-fedora] PR #1010: Add support for building Fedora Kinoite
by Timothée Ravier 19 May '21

19 May '21

siosm opened a new pull-request against the project: `pungi-fedora` that you are following: `` Add support for building Fedora Kinoite `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/1010

5 17

[release] Pungi 4.2.8
by Ondrej Nosek 04 May '21

04 May '21

Hello everyone, Pungi development team is pleased to announce the availability of Pungi 4.2.8. The updates for F32 and F33 are waiting in updates-testing repo. Others (Rawhide, F34) are already in stable repo Main changes: A new version of Pungi is available and installable from RCM Tools compose and repositories. Here are the major changes: * Added image-container phase. This phase runs after image-build and osbuild and can embed an image into a container. * Added ability to wait for signed packages. If packages are appearing quickly in Koji, and signing them is triggered by automation, there may be a delay between the package being signed and compose running. In such case, it may be preferable to wait for the signed copy rather than fail the compose. * Include just one version of module. When adding extra modules via option *pkgset_koji_module_builds*, all other versions of the same stream potentially available in a Brew tag should be skipped. * Remove reuse file when packages are not signed. In such case, we never want to reuse the pkgset, as it risks leaking unsigned packages. The safest option is to remove the file completely. * Preserve default arg on groupid. When the wrapper processes comps file, it wasn't emitting "default" argument for groupid element. The default is false and most entries are actually using the default, so let's only emit it if set to true. * Stopped copying .git directory with module defaults. This will potentially speedup full cloning of big repositories. * Dropped usage of kobo.plugins ... and other minor fixes Refer to the documentation [1] for details on what configuration options are available. [1] https://docs.pagure.org/pungi/index.html If you encounter problems or need general help, stop by #fedora-releng IRC channel or file issues in Pagure. Happy composing! Compose team _______________________________________________ rel-eng mailing list -- rel-eng(a)lists.fedoraproject.org To unsubscribe send an email to rel-eng-leave(a)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/rel-eng@lists.fedoraproject.o…

1 1

[pungi-fedora] PR #1026: Make the armhfp disk image non-failable.
by Paul Whalen 29 Apr '21

29 Apr '21

pwhalen opened a new pull-request against the project: `pungi-fedora` that you are following: `` Make the armhfp disk image non-failable. `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/1026

2 3

[Fedocal] Reminder meeting : Fedora Release Engineering
by mohanboddu＠fedoraproject.org 26 Apr '21

26 Apr '21

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2021-04-27 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://calendar.fedoraproject.org//meeting/9274/

1 0

Guardrails for too-short RC-to-Go/No-Go
by Ben Cotton 26 Apr '21

26 Apr '21

Hi everyone, In Friday's Go/No-Go meeting, we decided that having 5 hours between the completion of an RC and the start of the Go/No-Go meeting is not the ideal situation. So I got assigned the homework of starting the conversation about how to prevent this in the future. After all, if we don't stop ourselves from doing it, the temptation will be there. Since this is going to multiple mailing lists, I ask that the conversation happen in this Discussion thread to make sure we're all talking in one place: https://discussion.fedoraproject.org/t/guardrails-for-too-short-rc-to-go-no… -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

[pungi-fedora] PR #1030: Prep for f34-rc2
by Kevin Fenzi 23 Apr '21

23 Apr '21

kevin opened a new pull-request against the project: `pungi-fedora` that you are following: `` Prep for f34-rc2 `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/1030

2 1

[pungi-fedora] PR #1029: Setup for F34 Final 1.1
by Mohan Boddu 21 Apr '21

21 Apr '21

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Setup for F34 Final 1.1 `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/1029

2 2

F34 Final Go/No-Go moved to Friday
by Ben Cotton 21 Apr '21

21 Apr '21

Hi everyone, Since we anticipate a Fedora Linux 34 release candidate request today, I am moving the Go/No-Go meeting from Thursday to Friday. This will allow the QA team more time to perform validation tests. The Fedora Linux 34 Final Go/No-Go[1] meeting is scheduled for Friday 23 April at 1700 UTC in #fedora-meeting-1. At this time, we will determine the status of F34 for the 27 April target date. For more information about the Go/No-Go meeting, see the wiki[2]. [1] https://calendar.fedoraproject.org/meeting/9969/ [2] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng April 2021