Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
References: <CAJ5_7E+zVP0OGmHHK9wOv7M8Jm=JfF51FEeD2BpzdGdS4dcUhg@mail.gmail.com>
 <CAFu6yH1WuJtGZP1Y0ROenY02aU+qA1JjSNe3PsLyC5wSEXdTBQ@mail.gmail.com>
In-Reply-To: <CAFu6yH1WuJtGZP1Y0ROenY02aU+qA1JjSNe3PsLyC5wSEXdTBQ@mail.gmail.com>
From: Nick Pentreath <nick.pentreath@gmail.com>
Date: Wed, 30 Aug 2017 15:21:11 +0000
Message-ID: <CALD+6GOAn5YxCnmpi3YZGWh0mSMYA0V702339ga8M_84xwpH_g@mail.gmail.com>
Subject: Re: Updates on migration guides
To: "user@spark.apache.org" <user@spark.apache.org>
Cc: "user@spark.apache.org" <dev@spark.apache.org>
Content-Type: multipart/alternative; boundary="001a114b0f8e9ec89f0557fa1473"
archived-at: Wed, 30 Aug 2017 15:21:30 -0000

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

MLlib has tried quite hard to ensure the migration guide is up to date for
each release. I think generally we catch all breaking and most major
behavior changes

On Wed, 30 Aug 2017 at 17:02, Dongjoon Hyun <dongjoon.hyun@gmail.com> wrote:

> +1
>
> On Wed, Aug 30, 2017 at 7:54 AM, Xiao Li <gatorsmile@gmail.com> wrote:
>
>> Hi, Devs,
>>
>> Many questions from the open source community are actually caused by the
>> behavior changes we made in each release. So far, the migration guides
>> (e.g.,
>> https://spark.apache.org/docs/latest/sql-programming-guide.html#migration-guide)
>> were not being properly updated. In the last few releases, multiple
>> behavior changes are not documented in migration guides and even release
>> notes. I propose to do the document updates in the same PRs that introduce
>> the behavior changes. If the contributors can't make it, the committers who
>> merge the PRs need to do it instead. We also can create a dedicated page
>> for migration guides of all the components. Hopefully, this can assist the
>> migration efforts.
>>
>> Thanks,
>>
>> Xiao Li
>>
>
>

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

<div><div dir=3D"auto">MLlib has tried quite hard to ensure the migration g=
uide is up to date for each release. I think generally we catch all breakin=
g and most major behavior changes</div><br><div class=3D"gmail_quote"><div>=
On Wed, 30 Aug 2017 at 17:02, Dongjoon Hyun &lt;<a href=3D"mailto:dongjoon.=
hyun@gmail.com">dongjoon.hyun@gmail.com</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div>+1</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Wed, Aug 30, 2017 at 7:54 AM, Xiao Li <span>&lt;<a href=
=3D"mailto:gatorsmile@gmail.com" target=3D"_blank">gatorsmile@gmail.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><div>Hi, Devs,</d=
iv><div><br></div><div>Many questions from the open source community are ac=
tually caused by the behavior changes we made in each release. So far, the =
migration guides (e.g., <a href=3D"https://spark.apache.org/docs/latest/sql=
-programming-guide.html#migration-guide" target=3D"_blank">https://spark.ap=
ache.org/docs/latest/sql-programming-guide.html#migration-guide</a>) were n=
ot being properly updated. In the last few releases, multiple behavior chan=
ges are not documented in migration guides and even release notes. I propos=
e to do the document updates in the same PRs that introduce the behavior ch=
anges. If the contributors can&#39;t make it, the committers who merge the =
PRs need to do it instead. We also can create a dedicated page for migratio=
n guides of all the components. Hopefully, this can assist the migration ef=
forts.=C2=A0</div><div><br></div><div>Thanks,</div><div><br></div><div>Xiao=
 Li</div></div>
</blockquote></div><br></div>
</blockquote></div></div>

--001a114b0f8e9ec89f0557fa1473--