Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1913852 - i3 Spin
Summary: i3 Spin
Keywords:
Status: ON_QA
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Justin W. Flory (he/him)
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F34Changes
TreeView+ depends on / blocked
 
Reported: 2021-01-07 17:45 UTC by Ben Cotton
Modified: 2021-04-04 05:44 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Cotton 2021-01-07 17:45:34 UTC
This is a tracking bug for Change: i3 Spin
For more details, see: https://fedoraproject.org/wiki/Changes/Fedora_i3_Spin

Create an official Fedora Spin shipping the popular i3 window manager. This Spin would be the first Fedora Spin to feature a tiling/window manager instead of a traditional desktop environment.

Comment 1 Ben Cotton 2021-02-09 14:58:46 UTC
Today we reached the Completion deadline (testable) milestone in the Fedora schedule. All approved changes should be in a testable state. If you change is testable, please indicate this by setting the status to MODIFIED.

If you need to defer the change to Fedora 35 or withdraw the change entirely, please indicate this in a comment and NEEDINFO bcotton.

The 100% code complete deadline is Tuesday 23 February. By that date, your change should be fully implemented and the tracking bug set to ON_QA.

For other Fedora 34 milestones, see https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html

Comment 2 Justin W. Flory (he/him) 2021-02-16 15:18:09 UTC
This Change was approved by Release Engineering:

- https://pagure.io/releng/issue/9864

Two new kickstarts were submitted to pagure.io/fedora-kickstarts: one for rawhide and one for F34:

- https://pagure.io/fedora-kickstarts/pull-request/758
- https://pagure.io/fedora-kickstarts/pull-request/761

We anticipate having a nightly ISO build in time for the 100% code completion deadline:

https://openqa.fedoraproject.org/nightlies.html

Comment 3 Ben Cotton 2021-02-16 15:51:53 UTC
Reminder: The change complete (100% complete) deadline for Fedora 34 changes is Tuesday 23 February. At that point, changes should be 100% code complete, along with supporting documentation where appropriate. Please indicate this by setting the tracker bug for your change to ON_QA.

Comment 4 Ben Cotton 2021-02-23 16:38:07 UTC
Today is the change complete (100% complete) deadline for Fedora 34 changes. At this point, changes should be 100% code complete, along with supporting documentation where appropriate. Please indicate this by setting the tracker bug for your change to ON_QA. If you need to defer this change to Fedora 35, please set the version to 'rawhide'.

As a reminder, the Beta freeze is now in effect.

Comment 6 Justin W. Flory (he/him) 2021-03-10 23:31:38 UTC
Thank you Zbigniew for following up here. Bugzilla needinfo reminder emails flood my email and sometimes it is overwhelming if you do not check Bugzilla for a few days.

Anyways, for reference, I am sharing some of the Pull Requests which enabled us to begin building the i3 Spin in Fedora Infrastructure. As shown above in Zbigniew's comment, there are nightly composes taking place. The Respins SIG is supporting us in making build environment adjustments and fixes before the Fedora 34 Beta launch.

- https://pagure.io/fedora-comps/pull-request/569
- https://pagure.io/fedora-kickstarts/pull-request/761
- https://pagure.io/pungi-fedora/pull-request/1012

There were later iterations to all three of these repos with i3 deliverables, but these are the Pull Requests that got things in motion.


Note You need to log in before you can comment on or make changes to this bug.