> > We do not want to encourage/enable the rush to commit stuff before the 1st > May cut-off. IMHO we should be comfortable leaning towards saving any > significant commits for the next dev cycle. > > With sufficient testing added for a new feature, feature flags for > optionality, and a window of time to fuzz test things, why should we shy > away from even large commits the day before we freeze if they have a green > CI board? >
Yes, we are aligned here. If things are done properly then that's not "a rush", and there's no reason we shouldn't be _working as normal_ up until the 1st May. Keeping in mind that the time to do it properly can be something out of your control: CI not working, rebasing if there's a lot landing in trunk, etc. We also have the requirement that there will be no release without green CI. Do we cut a release branch on the 1st May if we don't yet have a green CI and can't be making a cut off it?
