Great, thanks for the fix.

Anything marked as fixed for 1.4.2 should now be marked as fixed for
1.4.1 right? I saw you were already updating many of those; OK to
finish that?

>From skimming them, it looks like mostly bug fixes and docs, which are
pretty safe. A few things are kind of minor behavior changes like
https://issues.apache.org/jira/browse/SPARK-8630  Still probably not
wrong to include.

Ideally these would not be merged in branch 1.4 while the RC process
is in progress, but then, that bottlenecks things. Once the RC for
1.4.1 is cut, should be mark everything else merged into branch 1.4 as
fixed for 1.4.2? and then if a new RC is cut, mark them as fixed for
1.4.1 instead? that's a nice easy convention.

Anything that might be mergeable for a later 1.4.x release but
shouldn't go into 1.4.1 could be left out of branch 1.4 and marked as
backport-needed. That should be a rare occasion for late in the RC
process.

Obviously, the faster the RC process goes the smaller this issue is -
the smaller and more disciplined the list of target issues is when the
process is, the better.

On Thu, Jul 2, 2015 at 7:11 PM, Andrew Or <and...@databricks.com> wrote:
> @Sean I believe that is a real issue. I have submitted a patch to fix it:
> https://github.com/apache/spark/pull/7193. Unfortunately this would mean we
> need to cut a new RC to include it. When we do so we should also do another
> careful pass over the commits that are merged since the first RC.
>
> -1
>
> 2015-07-02 9:10 GMT-07:00 Shivaram Venkataraman
> <shiva...@eecs.berkeley.edu>:
>>
>> +1 Tested the EC2 launch scripts and the Spark version and EC2 branch etc.
>> look good.
>>
>> Shivaram
>>
>> On Thu, Jul 2, 2015 at 8:22 AM, Patrick Wendell <pwend...@gmail.com>
>> wrote:
>>>
>>> Hey Sean - yes I think that is an issue. Our published poms need to
>>> have the dependency versions inlined.
>>>
>>> We probably need to revert that bit of the build patch.
>>>
>>> - Patrick
>>>
>>> On Thu, Jul 2, 2015 at 7:21 AM, vaquar khan <vaquar.k...@gmail.com>
>>> wrote:
>>> > +1
>>> >
>>> > On 2 Jul 2015 18:03, "shenyan zhen" <shenya...@gmail.com> wrote:
>>> >>
>>> >> +1
>>> >>
>>> >> On Jun 30, 2015 8:28 PM, "Reynold Xin" <r...@databricks.com> wrote:
>>> >>>
>>> >>> +1
>>> >>>
>>> >>> On Tue, Jun 23, 2015 at 10:37 PM, Patrick Wendell
>>> >>> <pwend...@gmail.com>
>>> >>> wrote:
>>> >>>>
>>> >>>> Please vote on releasing the following candidate as Apache Spark
>>> >>>> version
>>> >>>> 1.4.1!
>>> >>>>
>>> >>>> This release fixes a handful of known issues in Spark 1.4.0, listed
>>> >>>> here:
>>> >>>> http://s.apache.org/spark-1.4.1
>>> >>>>
>>> >>>> The tag to be voted on is v1.4.1-rc1 (commit 60e08e5):
>>> >>>> https://git-wip-us.apache.org/repos/asf?p=spark.git;a=commit;h=
>>> >>>> 60e08e50751fe3929156de956d62faea79f5b801
>>> >>>>
>>> >>>> The release files, including signatures, digests, etc. can be found
>>> >>>> at:
>>> >>>>
>>> >>>> http://people.apache.org/~pwendell/spark-releases/spark-1.4.1-rc1-bin/
>>> >>>>
>>> >>>> Release artifacts are signed with the following key:
>>> >>>> https://people.apache.org/keys/committer/pwendell.asc
>>> >>>>
>>> >>>> The staging repository for this release can be found at:
>>> >>>> [published as version: 1.4.1]
>>> >>>>
>>> >>>> https://repository.apache.org/content/repositories/orgapachespark-1118/
>>> >>>> [published as version: 1.4.1-rc1]
>>> >>>>
>>> >>>> https://repository.apache.org/content/repositories/orgapachespark-1119/
>>> >>>>
>>> >>>> The documentation corresponding to this release can be found at:
>>> >>>>
>>> >>>> http://people.apache.org/~pwendell/spark-releases/spark-1.4.1-rc1-docs/
>>> >>>>
>>> >>>> Please vote on releasing this package as Apache Spark 1.4.1!
>>> >>>>
>>> >>>> The vote is open until Saturday, June 27, at 06:32 UTC and passes
>>> >>>> if a majority of at least 3 +1 PMC votes are cast.
>>> >>>>
>>> >>>> [ ] +1 Release this package as Apache Spark 1.4.1
>>> >>>> [ ] -1 Do not release this package because ...
>>> >>>>
>>> >>>> To learn more about Apache Spark, please see
>>> >>>> http://spark.apache.org/
>>> >>>>
>>> >>>>
>>> >>>> ---------------------------------------------------------------------
>>> >>>> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
>>> >>>> For additional commands, e-mail: dev-h...@spark.apache.org
>>> >>>>
>>> >>>
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
>>> For additional commands, e-mail: dev-h...@spark.apache.org
>>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e-mail: dev-h...@spark.apache.org

Reply via email to