+1 to release RC2 as Apache Knox 1.3.0

   - Built from source
   - Ran a bunch of the samples (Admin API, WebHdfs, etc...)
   - Exercised some proxied UIs (e.g., yarnuiv2, oozie, sparkhistoryui,
   jobhistoryui, rangerui)
   - Tested ClouderaManager-based discovery and the associated UI changes

I've only found issues with CM-based discovery, the support for which isn't
complete yet anyway, so this is expected.


On Wed, Jul 17, 2019 at 3:14 PM Jeffrey Rodriguez <[email protected]>
wrote:

> Excellent job!! Thank you.
>
> I am able to build on the scenario where I had problems.
>
> Also tested a few of the scenarios where I use Knox.
>
> +1 Release this package as Knox 1.3.0 is my vote.
>
> Jeffrey E Rodriguez
>
> On Wed, Jul 17, 2019 at 5:37 AM larry mccay <[email protected]> wrote:
> >
> > All -
> >
> > A candidate for the Apache Knox 1.3.0 release is available at:
> >
> > https://dist.apache.org/repos/dist/dev/knox/knox-1.3.0/
> >
> > This RC addresses multiple issues identified in the testing of RC 1:
> >   1. Build problem related to DNS and SAN within the self signed cert
> >   2. libpam4j issue
> >   3. Upgrade to latest LTS of npm
> >
> > The release candidate is a zip archive of the sources in:
> >
> > https://https://gitbox.apache.org/repos/asf/knox.git
> > Branch v1.3.0 (git checkout -b v1.3.0)
> >
> > The KEYS file for signature validation is available at:
> > https://dist.apache.org/repos/dist/release/knox/KEYS
> >
> > Please vote on releasing this package as Apache Knox 1.3.0.
> > The vote is open for the next 72 hours and passes if a majority of at
> > least three +1 Apache Knox PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Knox 1.3.0
> > [ ] -1 Do not release this package because...
> >
> > thanks,
> >
> > --larry
>

Reply via email to