In terms of advertising to people the status of the release and whether an
RC is likely to go out, the best mechanism I can think of is our current
mechanism of using JIRA and respecting the semantics of a blocker JIRA. We
could do a better job though creating a JIRA dashboard for each release and
>
> Sorry for a second email so soon. I meant to also ask, what keeps the cost
> of making an RC high? Can we bring it down with better tooling?
>
There is a lot of tooling:
https://amplab.cs.berkeley.edu/jenkins/view/Spark-Packaging/
Still you have check JIRA, sync with people who have been work
On Wed, Dec 2, 2015 at 9:06 PM, Michael Armbrust wrote:
> This can be debated, but I explicitly ignored test and documentation issues.
> Since the docs are published separately and easy to update, I don't think
> its worth further disturbing the release cadence for these JIRAs.
It makes sense to
On Wed, Dec 2, 2015 at 3:19 PM, Sean Busbey wrote:
>
>
> On Wed, Dec 2, 2015 at 3:06 PM, Michael Armbrust
> wrote:
>
>>
>>>
>> The release is theoretically several weeks behind plan on what's
>>> intended to be a fixed release cycle too. This is why I'm not sure why
>>> today it's suddenly poten
On Wed, Dec 2, 2015 at 3:06 PM, Michael Armbrust
wrote:
>
>>
> The release is theoretically several weeks behind plan on what's
>> intended to be a fixed release cycle too. This is why I'm not sure why
>> today it's suddenly potentially ready for release.
>>
>
> Up until today various committers
Thanks for bringing this up Sean. I think we are all happy to adopt
concrete suggestions to make the release process more transparent,
including pinging the list before kicking off the release build.
Technically there's still a Blocker bug:
> https://issues.apache.org/jira/browse/SPARK-12000
Sor
Moving this to dev --
That's good, that'll help. Technically there's still a Blocker bug:
https://issues.apache.org/jira/browse/SPARK-12000
The 'race' doesn't matter that much, but release planning remains the
real bug-bear here. There are still, for instance, 52 issues targeted
at 1.6.0, 42 of w
