Spark's branch-2.0 is a maintenance branch, effectively meaning that only bug-fixes will be added to it. There are other maintenance branches (such as branch-1.6) that are also receiving bug-fixes in theory, but not so much in fact as maintenance branches get older. The major and minor version numbers of maintenance branches stay fixed, with only the patch-level version number changing as new releases are made from a maintenance branch. Thus, the next release from branch-2.0 will be 2.0.1, the set of bug-fixes contributing to the next branch-2.0 release will result in 2.0.2, etc.
New work, both bug-fixes and non-bug-fixes, is contributed to the master branch. New releases from the master branch increment the minor version number (unless they include API-breaking changes, in which case the major version number changes -- e.g. Spark 1.x.y to Spark 2.0.0). Thus the first release from the current master branch will be 2.1.0, the next will be 2.2.0, etc. There should be active "next JIRA numbers" for whatever will be the next release from the master as well as each of the maintenance branches. This is all just basic SemVer (http://semver.org/), so it surprises me some that you are finding the concepts to be new, difficult or frustrating. On Sun, Sep 25, 2016 at 8:31 AM, Jacek Laskowski <ja...@japila.pl> wrote: > Hi Sean, > > I remember a similar discussion about the releases in Spark and I must > admit it again -- I simply don't get it. I seem to not have paid > enough attention to details to appreciate it. I apologize for asking > the very same questions again and again. Sorry. > > Re the next release, I was referring to JIRA where 2.0.2 came up quite > recently for issues not included in 2.0.1. This disjoint between > releases and JIRA versions causes even more frustration whenever I'm > asked what and when the next release is going to be. It's not as > simple as I think it should be (for me). > > (I really hope it's only me with this mental issue) > > Unless I'm mistaken, -Pmesos won't get included in 2.0.x releases > unless someone adds it to branch-2.0. Correct? > > Pozdrawiam, > Jacek Laskowski > ---- > https://medium.com/@jaceklaskowski/ > Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark > Follow me at https://twitter.com/jaceklaskowski > > > On Sun, Sep 25, 2016 at 1:35 PM, Sean Owen <so...@cloudera.com> wrote: > > Master is implicitly 2.1.x right now. When branch-2.1 is cut, master > > becomes the de facto 2.2.x branch. It's not true that the next release > > is 2.0.2. You can see the master version: > > https://github.com/apache/spark/blob/master/pom.xml#L29 > > > > On Sun, Sep 25, 2016 at 12:30 PM, Jacek Laskowski <ja...@japila.pl> > wrote: > >> Hi Sean, > >> > >> So, another question would be when is the change going to be released > >> then? What's the version for the master? The next release's 2.0.2 so > >> it's not for mesos profile either :( > >> > >> Pozdrawiam, > >> Jacek Laskowski > >> ---- > >> https://medium.com/@jaceklaskowski/ > >> Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark > >> Follow me at https://twitter.com/jaceklaskowski > >> > >> > >> On Sun, Sep 25, 2016 at 1:27 PM, Sean Owen <so...@cloudera.com> wrote: > >>> It's a change to the structure of the project, and probably not > >>> appropriate for a maintenance release. 2.0.1 core would then no longer > >>> contain Mesos code while 2.0.0 did. > >>> > >>> On Sun, Sep 25, 2016 at 12:26 PM, Jacek Laskowski <ja...@japila.pl> > wrote: > >>>> Hi Sean, > >>>> > >>>> Sure, but then the question is why it's not a part of 2.0.1? I thought > >>>> it was considered ready for prime time and so should be shipped in > >>>> 2.0.1. > >>>> > >>>> Pozdrawiam, > >>>> Jacek Laskowski > >>>> ---- > >>>> https://medium.com/@jaceklaskowski/ > >>>> Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark > >>>> Follow me at https://twitter.com/jaceklaskowski > >>>> > >>>> > >>>> On Sun, Sep 25, 2016 at 1:21 PM, Sean Owen <so...@cloudera.com> > wrote: > >>>>> It was added to the master branch, and this is a release from the > 2.0.x branch. > >>>>> > >>>>> On Sun, Sep 25, 2016 at 12:12 PM, Jacek Laskowski <ja...@japila.pl> > wrote: > >>>>>> Hi, > >>>>>> > >>>>>> That's even more interesting. How's so since the profile got added a > >>>>>> week ago or later and RC2 was cut two/three days ago? Anyone know? > >>>>>> > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
