Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: 
 <CAAswR-5siaqmeGJmCY=N2KM5y=EP4_1w43ZAwvERaTTcTzFArQ@mail.gmail.com>
References: 
 <CAMAsSdKsDwXJLpEM+oS4AxV=WQgW3iUDm7xUN0r4-TT7YFJ9AQ@mail.gmail.com>
 <CAAswR-5siaqmeGJmCY=N2KM5y=EP4_1w43ZAwvERaTTcTzFArQ@mail.gmail.com>
From: Sean Busbey <busbey@cloudera.com>
Date: Wed, 2 Dec 2015 15:19:04 -0600
Message-ID: 
 <CAGHyZ6JPdMHbLeixO-Rc1kDX4vy4Ca7JzGVr3BK3QooEEnGDrg@mail.gmail.com>
Subject: Re: When to cut RCs
To: Michael Armbrust <michael@databricks.com>
Cc: Sean Owen <sowen@cloudera.com>, dev <dev@spark.apache.org>
Content-Type: multipart/alternative; boundary=001a11c37c540be9a60525f0d440

--001a11c37c540be9a60525f0d440
Content-Type: text/plain; charset=UTF-8

On Wed, Dec 2, 2015 at 3:06 PM, Michael Armbrust <michael@databricks.com>
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 have told me that there were known
> issues with branch-1.6 that would cause them to -1 the release.  Whenever
> this happened, I asked them to ensure there was a properly targeted blocker
> JIRA open so people could publicly track the status of the release.  As
> long as such issues were open, I only published a preview since making an
> RC is pretty high cost.
>
> I'm sorry that it felt sudden to you, but as of last night all such known
> issues were resolved and thus I cut a release as soon as this was the case.
>
>

It would help me, and I'm sure other less-active folks, if this kind of
feedback cycle were visible on dev@spark. It would also have the benefit of
getting feedback from non-committers who might e.g. have some issue that
they see in their own production deployments.


-- 
Sean

--001a11c37c540be9a60525f0d440
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Dec 2, 2015 at 3:06 PM, Michael Armbrust <span dir=3D"ltr">&lt;=
<a href=3D"mailto:michael@databricks.com" target=3D"_blank">michael@databri=
cks.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><span class=3D"=
"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><br></blockquote></span><span class=3D""><=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
The release is theoretically several weeks behind plan on what&#39;s<br>
intended to be a fixed release cycle too. This is why I&#39;m not sure why<=
br>
today it&#39;s suddenly potentially ready for release.<br></blockquote><div=
>=C2=A0</div></span><div>Up until today various committers have told me tha=
t there were known issues with branch-1.6 that would cause them to -1 the r=
elease.=C2=A0 Whenever this happened, I asked them to ensure there was a pr=
operly targeted blocker JIRA open so people could publicly track the status=
 of the release.=C2=A0 As long as such issues were open, I only published a=
 preview since making an RC is pretty high cost.</div><div><br></div><div>I=
&#39;m sorry that it felt sudden to you, but as of last night all such know=
n issues were resolved and thus I cut a release as soon as this was the cas=
e.</div><span class=3D""><div><br></div></span></div></div></div></blockquo=
te><div><br></div><div><br></div><div>It would help me, and I&#39;m sure ot=
her less-active folks, if this kind of feedback cycle were visible on dev@s=
park. It would also have the benefit of getting feedback from non-committer=
s who might e.g. have some issue that they see in their own production depl=
oyments.</div><div><br></div></div><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature"><div dir=3D"ltr">Sean</div></div>
</div></div>

--001a11c37c540be9a60525f0d440--