rel-eng January 2021

rel-eng@lists.fedoraproject.org

5 participants
41 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 #958: Add Java modules to ELN
by Mikolaj Izdebski 23 Mar '21

23 Mar '21

mizdebsk opened a new pull-request against the project: `pungi-fedora` that you are following: `` Add Java modules to ELN `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/958

4 6

[pungi-fedora] PR #598: Fedora Minimal Compose for OpenQA testing
by Mohan Boddu 09 Mar '21

09 Mar '21

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Fedora Minimal Compose for OpenQA testing `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/598

5 20

[pungi-fedora] PR #438: Add post-compose rsync script
by Kellin 08 Mar '21

08 Mar '21

kellin opened a new pull-request against the project: `pungi-fedora` that you are following: `` Add post-compose rsync script `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/438

3 2

[pungi-fedora] PR #502: WIP: Add fedora-atomic-ws config
by Colin Walters 08 Mar '21

08 Mar '21

walters opened a new pull-request against the project: `pungi-fedora` that you are following: `` WIP: Add fedora-atomic-ws config `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/502

6 20

Attempting to allow for a source of truth for Fedora release cycle information: releasestream
by Adam Williamson 11 Feb '21

11 Feb '21

Hi folks! Before the RH holiday shutdown, I started a new project designed to address a long-standing pain point in Fedora: we don't really have a good source of truth for release cycle information. I'm thinking of situations where something: * Needs to know what the "current stable" Fedora release(s) are * Needs to know if Fedora X is Branched * Needs to know whether Fedora X Beta happened yet * Needs to know whether Fedora X is frozen ...etc etc etc. Some of this information is available...sort of...from various different systems, with various awkward caveats that I won't dive into unless someone asks. But there isn't really a single source of truth for it, and some of it just isn't really available in any easily machine-consumable way. So I wrote releasestream: https://pagure.io/fedora-qa/releasestream releasestream is intended to be a system that will let us do this. It is a very very simple webapp with three capabilities: * It can read a simple record ("stream") of "release events" for a "release" and produce several static JSON representations of the information * It can write an entry to one of these streams in response to a properly-formatted POST request * It can publish a message when a new entry is received that is all it does. The "releases" and "events" are entirely arbitrary; a "release" can be any string, and so can the "state" for a given "event". An "event" is defined as a state being either reached or left; any number of events for the same state can be present for a release. The JSON outputs are basically "states by release" and "releases by state", as you might want either depending on what you're doing. You can conveniently look up "what releases are currently in state X?" or "what states is release X currently in?". This all works right now; the main thing that isn't implemented yet is any form of authentication. Right now if you can talk to the server you can submit events. I wanted to check if there is interest in moving forward with this, and discuss various options, before working on that. There is a ticket where I sketched out various possible approaches: https://pagure.io/fedora-qa/releasestream/issue/2 My idea for using this is basically that we deploy an 'official' releasestream instance in infra, and then find things that do the actual work of moving Fedora releases into and out of given "states" and tack on a bit at the end to tell releasestream about it. So when e.g. Mohan is putting Fedora 34 into the Beta freeze, we would add a "submit 'enter freeze' event to releasestream" to that process somehow - ideally something that has to be run as part of the process anyway would send the POST, but in a pinch a human could do it too. When Fedora 34 is being 'released', we tweak that process to include sending a releasestream event POST. And so on. The thing I like about this design is that there's a low barrier to entry, and can easily be adopted piecemeal but still be immediately useful for some things - as long as the event your code needs to watch for has been "onboarded", you're good. It also allows for the implementation details of a state change to change radically - it can go from being done by a human to being done by system X to being done by system Y, and all that needs to happen is to ensure the same dead simple POST request is sent to the same server. So, what do folks think? Does this seem like a good idea? Should I go ahead with trying to get it deployed and onboard things to it? Any comments, ideas, potential problems? Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

3 6

[pungi-fedora] PR #984: epel8-playground: fix config to use main.
by Kevin Fenzi 01 Feb '21

01 Feb '21

kevin opened a new pull-request against the project: `pungi-fedora` that you are following: `` epel8-playground: fix config to use main. `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/984

1 1

[pungi-fedora] PR #982: Blocking perl-bootstrap:*, rust:*, rpm:* modules
by Mohan Boddu 01 Feb '21

01 Feb '21

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Blocking perl-bootstrap:*, rust:*, rpm:* modules `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/982

2 1

[pungi-fedora] PR #911: hardlink content for rawhide/branched
by Kevin Fenzi 01 Feb '21

01 Feb '21

kevin opened a new pull-request against the project: `pungi-fedora` that you are following: `` hardlink content for rawhide/branched `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/911

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2021