As the Beta Freeze for F26 approaches, the modularity team (and friends) would like to seek approval from FESCo for changes during the freeze that, while technically within the allowed scope of changes, may not be in the spirit of the scope. Specifically, we expect to continue to update some incomplete modules as well as bugs and changes in kickstarts and pungi configs. Technically, we expect everything we submit for the Beta Freeze to be “working,” however, we do not think it will all be working the way we wish. As a result, the changes may be broader than is typically expected.
As per usual with new development, we have encountered more issues with infrastructure and packaging than we expected, slowing our development. We have (and will be) cutting the scope some and moving late arriving components to COPR but we do need to get to a viable Boltron spin to gather user feedback.
However, the silver lining is, all of our changes are essentially walled off from the main distribution of the Fedora Editions. Specifically, the modules are not used except by Boltron, the kickstarts and pungi configs in question are only the ones to make the Boltron spin images and the Base-Runtime container base image.
What does this approval get you that you wouldn't otherwise already have? I'm not sure what a blessing from FESCo actually translates to here. If everything is walled off and Boltron is the only thing impacted, it seems straightforward to say sure. However, I can't tell if granting that impacts other teams somehow.
I guess we wanted to be sure that y'all had a heads up and so we wouldn't have to have an uncomfortable conversation later. We also wanted to have approval (for timing, obviously, content would be at the time) for any merges we requested (pungi configs, kickstarts). Only impact we are aware of is on releng effort for merges.
Metadata Update from @maxamillion: - Issue tagged with: meeting
What does this approval get you that you wouldn't otherwise already have?
time
This is fine with me.
+1 here, I don't see any reason this should be bound by freeze.
We took this as information and no one expressed issues
Metadata Update from @ausil: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.