>> Ideally, though - docs should be updated through the process. (i.e., >> let's not wait until M3W1 to start doc updates, please.) > > Absolutely true. I just think that we need to call out the feature > freeze as being the point in time that documentation can start being > reviewed in earnest, against the features themselves (knowing that > they may be buggy).
IMO Feature freeze == Code freeze == Docs freeze Features shouldn't be landing without documentation, and this will (hopefully) prevent docs from being a blocker in future releases. After feature freeze someone should be actively minding the commits that come into the release branch IMO.
