How should Impala branches be a manged? Today, most of our new development happens on trunk, except when a CDH release is imminent. I propose we move to a time-based release model, where development happens on the "master" branch and every N weeks a commit that is passing all of the tests is tagged with a version number.
Then we can do an actual release: http://www.apache.org/dev/release.html For big breaking changes, we could keep two branches around corresponding to the two versions currently being developed on. Thoughts?
