You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
Priority review needed on everything labeled Release Cycle from downstream so that commit chosen for releases include 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 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.
The text was updated successfully, but these errors were encountered:
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)
Date might be postponed, in which case title of this issue will change.
TODO from downstream:
The text was updated successfully, but these errors were encountered: