On Fri, Sep 1, 2017 at 11:34 AM, Pramod Immaneni <pra...@datatorrent.com> wrote:
> > > > Regarding procedural vote, the decision to start development towards new > > major release is a longer term decision, not just code change. > > > > Longer term decision does not mean procedural change. You can have changes > that can be proposed as being beneficial in the long term which still > manifest in code changes now such as this one. Example of procedural > changes would be, steps a contributor should follow to submit code, steps a > committer should follow, jira filing process, release processes etc., the > kind of updates you made recently in the contribution guidelines on the > apex site. > > Most decisions eventually result in code modifications. Beginning of major release development is not a code modification vote. It looks in fact very similar to a release vote, a majority approval decision. The only imminent code change is the version number.
