When we went through vote on 3.1.3/3.2.1, we'd discussed releasing 3.2.2/3.1.4 on a shorter release period than normal. A shorter release cycle for these two versions would allow us to quickly address a bug or two found late in code freeze. Perhaps longer term, shorter release cycles might help produce less stress around getting PRs in for code freeze as there would be an expectation that another release would follow with reasonable speed.
I'd like to propose that we start code freeze 8/27 and go to vote on 9/5. I'll just mention that I could only see those dates slipping a little bit if TINKERPOP-1278 runs into troubles, but right now I think that's on track to get merged back to master in time for that deadline. Any thoughts? Thanks, Stephen
