UIP 0137 merge window notice#88
Conversation
Add Process UIP requiring minimum four weeks notice before any merge window closes, announced at Core Architecture meetings. Includes exceptions for CVEs, critical bugs, and security dependency uplifts.
|
As discussed in core architecture the other day (~2026.04.30), Core is open to providing the courtesy of a four-week closure notice for the "guaranteed to make it into the release" merge window. We note that this doesn't say anything about merges or releases of any kind after that window. It will be business as usual (that is to say, up to release manager's discretion). With that in mind, points 6 through 9 feel potentially out of scope. The desire here, and the extent of the courtesy, is to communicate a deadline for inclusion in some release. Generally, yes, this will be the immediately upcoming release that's actively being pursued. But we want to retain the flexibility of sneaking hotfixes out the door or changing our mind about release ordering or scheduling. Points 6-9 read like they're trying to accommodate that flexibility, but are implicitly assuming guarantees about release schedule. Again, we are open to communicating early about release planning, but not to committing to a release schedule. In short: this UIP should be slimmed down to a scope of points 1-5 and emphasize it's about communication rather than hard release scheduling. |
2 participants
No description provided.