[1.9] Feature Freeze about sig-release

[Bradamant3]

IIRC, 1.9 is now slated to be a maintenance release? If so, we should minimize sig-specific themes I believe, although I know that sig-apps is planning to move the workloads api wholesale to v1, and will no doubt want to feature the move prominently. @idvoretskyi ran this aspect of things for 1.8 (and earlier) -- can you help out here too? Am I understanding correctly? Should we be reaching out to sigs? (I need to do so in any case wrt release notes.)

[idvoretskyi]

@enisoc

@idvoretskyi Do you require anything at feature freeze other than that the issues are populated in the features repo?

No, nothing else.

@Bradamant3 yes, we need reach to SIGs. Also, on maintenance/non-maintenance releases - it seems, we would avoid using this terminology for the future, as discussed at 1.8 retro. No final agreement yet, but let's focus on release deliverability, not terminology.

[enisoc]

Features are populated at http://bit.ly/k8s19-features.