To improve on our release process a bit and to make things a bit less hectic for the "release manager" on release day I've been documenting a few things I've done this week in preparation for 3.0.2.
https://github.com/apache/incubator-tinkerpop/blob/tp30/RELEASE.asciidoc#pre-flight-check I'd like to include in this list something that Matt Frantz had suggested when we released 3.0.1 - code freeze 1 week prior to release. To be more specific, I think that means that we should stop changes to actual "code" the day we begin the pre-flight check. Documentation tweaks and other knick-knacks would still be fair game, but I think we reduce some risk/headache by placing this limit on ourselves. So, I guess this thread is about two things: 1. What do you think of my pre-flight checks? Should anything be added? 2. Should we implement Matt Frantz's suggestion and institute a 1 week code freeze prior to release?
