Using 0.10.0 for the next version sounds good to me. That would get us to a baseline for different branches on Hadoop3 and Hadoop2. Once that is squared away, we would have more time to discuss what people think should be included in a 1.0.
Maybe something like? Hadoop2: 0.9.1 -> 0.9.2 -> 0.9.3 -> 0.9.4 -> ... Hadoop3: \----> 0.10.0 -> 1.0 -> 1.1 -> ... On Tue, May 1, 2018 at 8:47 AM, Jonathan Eagles <[email protected]> wrote: > My personal feeling was to keep the version 0.10.0 as part of what > discussed as part of the VOTE to move 0.9.x release line to branch-0.9 and > keep master branch for 0.10.x. However, this question was asked by Eric as > part of TEZ-3923. > > Reference comment. > https://issues.apache.org/jira/browse/TEZ-3923?focusedCommentId=16458814&; > page=com.atlassian.jira.plugin.system.issuetabpanels: > comment-tabpanel#comment-16458814 > > Wanted to give some background of this discussion so it doesn't seem like > we are discussing something we already decided upon. > > jeagles > > On Tue, May 1, 2018 at 10:44 AM, Jonathan Eagles <[email protected]> > wrote: > > > Devs, > > > > As part of the moving 0.9.x line to a branch, should we call the new line > > that supports hadoop 3.x 0.10.x or 1.0.x? > > > > Moving to 1.x caries with it a certain connotation of being stable, but I > > wanted to reach out to the community to get a feel for what people are > > thinking for the next release line naming scheme. > > > > jeagles > > >
