Master, branches and versioning

[Sean Owen <so...@cloudera.com>]

(Renaming thread to keep it separate from RC vote)

If you're asking why there's a version 2.0.2 in JIRA, it's because we
have to have that entity in order to target anything to version 2.0.2.
2.2.0 exists as well as version labels in JIRA. None are marked as
'released' because there is no such release, but it makes perfect
sense to have a noun to talk about in JIRA.

There may never be a 2.0.2 software release. But anything committed to
2.0.x after this point will be released in 2.0.2 _if it does get
released_.
If 2.0.2 happens it may happen before or after 2.1.0; that's normal. I
suspect it would happen after, if ever, and I expect the next actual
software release chronologically will be 2.1.0.

I think this is all standard software procedure; what's the confusion?

There is no formal plan for when which releases happen, so I don't
think anyone can answer that definitively. I happens when it happens
by loose consensus.

The -Pmesos change is not in branch-2.0 and therefore would not be in
any 2.0.x release.


On Sun, Sep 25, 2016 at 4:31 PM, 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

---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscribe@spark.apache.org