I thought of it as a week to merge remaining PR's (and do minor cleanups, like you're planning to do for the tutorials). Code freeze means (to me), that we don't add new things / PR's, but care more about the things that were already done.
Cheers, Daniel On Mon, Nov 9, 2015 at 2:21 PM, Stephen Mallette <[email protected]> wrote: > We agreed on having a 1 week code freeze - yet i'm now merging PRs on code > freeze day. bad? > > I'm not sure it is. I guess it *could* have been bad if someone tried to > jam in a massive change during code freeze week and the PR was full of > holes and risks. Seems like we were smart enough to mitigate that for this > release as we carefully watched the "high-risk" JIRA tickets on the way > into code freeze. If we continue to do that, I imagine we'd be fine, but > all committers will have to be responsible in their choices as it pertains > to PRs. > > Anyway, just thought I'd bring it up, in case anyone had any thoughts they > wanted to share on procedural changes in this area. >
