FEATURE FREEZE PLANNED FOR 2024-11-20

[tlaurion]

This is follow-up conclusion from discussions having happened after my QubesOS mini-summit Heads rolling release : roles of upstream and downstream forks (Design Session)

• Takeaway is 30 seconds long at end of the recording, up to the end: https://youtu.be/mAb_kHrF6SQ?list=PLuISieMwVBpL5S7kPUHKenoFj_YJ8Y0_d&t=1848
• Priority review needed on everything labeled Release Cycle EDIT: Release cycle -2024-11-20 from downstream so that commit chosen for releases include upstream merged stuff.
• Everything unfixed at time of feature freeze should be labeled known issues in downstream release to be fixed in next release.
• Note that downstream plans 1 to 2 releases a year, so this is important to prioritize.

Date might be postponed, in which case title of this issue will change.

TODO from downstream:

• Prepare automated testing system for @tlaurion to access them as early as possible. (task: @macpijan? otherwise tag proper github aliases here)
• Downstream needs to raise issues upstream ASAP to have a chance to be addressed if not already (task: @nestire/@jans23 + @wessel-novacustom + @JonathonHall-Purism ? otherwise tag proper github aliases here from your support team issue dispatchers for most common issues)
• Other tasks? Comment and i'll add them here in OP.

[wessel-novacustom]

I will try the latest Heads upstream version tomorrow and provide feedback in tickets.

[wessel-novacustom]

I will try the latest Heads upstream version tomorrow and provide feedback in tickets.

I'm sorry for the delay. I have to postpone this for now, as we are now working on the videos for the current Dasharo coreboot+Heads release. I hope to find enough time to continue this on Saturday, otherwise the Saturday after.

20th of November sounds a bit early to me since there is probably also some time needed for realising improvements, if needed from our side of course.

[tlaurion]

I will try the latest Heads upstream version tomorrow and provide feedback in tickets.

I'm sorry for the delay. I have to postpone this for now, as we are now working on the videos for the current Dasharo coreboot+Heads release. I hope to find enough time to continue this on Saturday, otherwise the Saturday after.

20th of November sounds a bit early to me since there is probably also some time needed for realising improvements, if needed from our side of course.

@wessel-novacustom I didn't know you were spooling this this fast. There are still changes pending that changes the UX, so please sync with me prior of doing the videos. One example is #1541 (comment) which I cross-linked here exactly for video creation purposes. Once that PR is merged, oem-factory-reset/Re-ownership is not expected to change until feature freeze.

EDITED: link

[tlaurion]

20th of November sounds a bit early to me since there is probably also some time needed for realising improvements, if needed from our side of course.

This is date Dasharo picked for coreboot release. This is interesting experience.

@wessel-novacustom @macpijan @pietrushnic : this needs better synchronization.

Bugs still awaited to be opened on heads (upstream release) to work on issues. Then fixes need to be tested and then pooled to dasharo for downstream release.

This is why I said Heads is rolling release in my talk. If I have to wait for input from all parties, and videos are to be produced, this is forever chicken egg problem and hence why rolling release.

Let's say as of now that known issues upstream of today will be fixed first week of November as of now.

If this is the case, then videos should be spooled to be produced when Dasharo will pick Heads commit, but issues still awaited on Heads master as of today and planned feature freeze planed is in 20 days as of now. Time to redefine?

Sync needed off github people. Let's chat under matrix and come here with realistic date with now better understanding of realities of a release requiring a feature freeze without issues even opened yet nor upstream tested today from downstream, nor stated needed development for next downstreamrelease that is expected to happen only once a year.