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.h...@gmail.com> wrote: > +1 > > On Wed, Aug 30, 2017 at 7:54 AM, Xiao Li <gatorsm...@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 >> > >
