Do we have a feature list or release notes for 2.0 like before?
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Apache-Spark-2-0-0-RC1-tp18019p18182.html
Sent from the Apache Spark Developers List mailing list archive at Nabble.com.
-
On Sun, Jul 3, 2016 at 7:03 PM, Jacek Laskowski wrote:
> On Sun, Jul 3, 2016 at 3:49 PM, Sean Owen wrote:
>> On Sun, Jul 3, 2016 at 2:42 PM, Jacek Laskowski wrote:
>>> 2. Add new features to master (versions - master: 2.0.0-SNAPSHOT
>>> branch: 2.0.0-RC1)
>>
>> Either:
>> a) you prohibit anyone
On Sun, Jul 3, 2016 at 3:49 PM, Sean Owen wrote:
> On Sun, Jul 3, 2016 at 2:42 PM, Jacek Laskowski wrote:
>> 2. Add new features to master (versions - master: 2.0.0-SNAPSHOT
>> branch: 2.0.0-RC1)
>
> Either:
> a) you prohibit anyone from committing anything to master that can't
> go into 2.0.0 at
Hello,
Any ideas about this one https://issues.apache.org/jira/browse/SPARK-13979
?
Does others see the same issues?
Thanks
Gil.
On Sun, Jul 3, 2016 at 2:42 PM, Jacek Laskowski wrote:
> 2. Add new features to master (versions - master: 2.0.0-SNAPSHOT
> branch: 2.0.0-RC1)
Either:
a) you prohibit anyone from committing anything to master that can't
go into 2.0.0 at this point until it's released, holding up
development, or
b
Hi Sean,
What's wrong with the following release procedure?
1. Use master to create RC (versions - master: 2.0.0-SNAPSHOT branch: 2.0.0-RC1)
2. Add new features to master (versions - master: 2.0.0-SNAPSHOT
branch: 2.0.0-RC1)
3. RC passes a vote => ship it (versions - master: 2.1.0-SNAPSHOT
branc
It's not that you're starting 2.1 per se, but, that you're committing
things that are not in 2.0. Releases are never made from master in
moderately complex projects. It has nothing to do with pace of
release.
On Sun, Jul 3, 2016 at 1:24 PM, Jacek Laskowski wrote:
> Hi,
>
> Why would I need to sta
Hi,
Why would I need to start 2.1? If it's ready for master, why could it be
not part of 2.0? "Release early and often" is what would benefit Spark a
lot. The time to ship 2.0 is far too long I think. And I know companies
that won't use 2.0 because...it's "0" version :-(
Jacek
On 3 Jul 2016 2:59
