Thanks Zhankun and everybody who helped this release.

Could you share the link to the user doc?

Best,
Wangda

On Thu, Jun 6, 2019 at 8:55 AM Xun Liu <neliu...@163.com> wrote:

> Zhankun,
>
> Thank you release submarine 0.2.0
>
> I tested it with submarine-0.2.0-rc0. The functions can be used normally.
> But I found a little problem, The command parameter --verbose does not
> take effect.
> But this does not affect the use, It is recommended that after
> submarine-0.2.0-rc0 is released, Can be improved.
>
> +1
>
>
> > On Jun 6, 2019, at 9:23 PM, Zhankun Tang <zt...@apache.org> wrote:
> >
> > Hi folks,
> >
> > Thanks to all of you who have contributed in this submarine 0.2.0
> release.
> > We now have a release candidate (RC0) for Apache Hadoop Submarine 0.2.0.
> >
> >
> > The Artifacts for this Submarine-0.2.0 RC0 are available here:
> >
> > https://home.apache.org/~ztang/submarine-0.2.0-rc0/
> >
> >
> > It's RC tag in git is "submarine-0.2.0-RC0".
> >
> >
> >
> > The maven artifacts are available via repository.apache.org at
> > https://repository.apache.org/content/repositories/orgapachehadoop-1221/
> >
> >
> > This vote will run 7 days (5 weekdays), ending on 13th June at 11:59 pm
> PST.
> >
> >
> >
> > The highlights of this release.
> >
> > 1. Linkedin's TonY runtime support in Submarine
> >
> > 2. PyTorch enabled in Submarine with both YARN native service runtime
> > (single node) and TonY runtime
> >
> > 3. Support uber jar of Submarine to submit the job
> >
> > 4. The YAML file to describe a job
> >
> > 5. The Notebook support (by Apache Zeppelin Submarine interpreter)
> >
> >
> > Thanks to Sunil, Wangda, Xun, Zac, Keqiu, Szilard for helping me in
> > preparing the release.
> >
> > I have done a few testing with my pseudo cluster. My +1 (non-binding) to
> > start.
> >
> >
> >
> > Regards,
> > Zhankun
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
>
>

Reply via email to