#29 Submit i3 kickstarts to fedora-kickstarts releng repo
Opened 2 months ago by jflory7. Modified 3 days ago

Summary

In order to build i3 ISOs in Fedora build infrastructure, submit the i3 kickstarts to pagure.io/fedora-kickstarts

Background

The i3 Spin Change Proposal for Fedora 34 was approved and accepted by FESCo. We should now begin preparing the Fedora build infrastructure with our kickstarts and troubleshoot for any issues ahead of the 100% code completion deadline on Tue 2021-02-23.

Details

pbrobinson tipped us off on how to do this in releng#9864. There are some light instructions in the pagure.io/fedora-kickstarts repo, but it is not entirely clear on what the process is.

We need a volunteer to work on integrating our "upstream" kickstarts into Fedora build infrastructure.

Outcome

Fedora i3 Spin ISOs are produced by official Fedora build infrastructure


Metadata Update from @jflory7:
- Issue set to the milestone: F34 – Change Completion deadline (testable)

2 months ago

Metadata Update from @x3mboy:
- Issue assigned to nasirhm

a month ago

Metadata Update from @jflory7:
- Issue unmarked as blocking: #15
- Issue unmarked as depending on: #26
- Issue set to the milestone: F34 – Change 100% Code Complete Deadline (was: F34 – Change Completion deadline (testable))
- Issue tagged with: help wanted, type - releng

17 days ago

The deadline for submitting the i3 kickstarts to Release Engineering composes for F34 branching. We missed this deadline. I updated the milestone for the absolute hard deadline on 23 February 2021 (100% Code Completion deadline). This gives us 14 days to make the release.

@nasirhm How is the work going on the fedora-kickstarts PR? Have you had a chance to look into this or should be open the ticket up for someone else? Keep us informed on how things are going or if you need a hand. Here to help!

Issue added to pungi to have nightly builds: pungi-fedora#1009

It still needs the maintainers.toml

Metadata Update from @x3mboy:
- Issue assigned to odilhao (was: nasirhm)

3 days ago

Metadata Update from @x3mboy:
- Issue priority set to: next meeting (was: waiting on assignee)

3 days ago

Login to comment on this ticket.

Metadata