Thanks Larry. That's great news; 1.0.0 !
On Mon, Feb 5, 2018 at 3:26 PM, larry mccay <[email protected]> wrote: > The VOTE for 1.0.0 rc2 passes with: > > 4 binding +1's > 1 non-binding +'1 > 0 -1's > > I am very excited to finally mark our 1.0.0 release! > > I will be working on promoting RC2 to an official release shortly. > > Thank you for taking the time to test this release and contributing to the > Apache Knox community! > > On Sat, Feb 3, 2018 at 9:14 AM, larry mccay <[email protected]> wrote: > >> +1 >> >> * Built from source (with Java 1.8.0_144) >> * Checked LICENSE and NOTICE files >> * Verified signatures >> * Checked CHANGES file >> * Ran unit tests >> * Tested KnoxShell samples >> * Tested KnoxLine hive client in knoxshell [1] >> * Tested KnoxSSO with Form-based provider to LDAP >> * Tested with simple node.js webhdfs client [2] >> * Tested knoxshell init, list, destroy and KnoxToken Sessions for >> knoxshell >> >> 1. https://cwiki.apache.org/confluence/display/KNOX/SQL+Clie >> nt+Example+using+KnoxShell+in+Apache+Knox >> 2. https://github.com/lmccay/knoxfs >> >> On Sat, Feb 3, 2018 at 9:06 AM, larry mccay <[email protected]> wrote: >> >>> Hi Phil - >>> >>> I agree that this is not a blocker issue since there is a workaround and >>> it is inline with 0.14.0 anyway. >>> >>> Thanks for filing the JIRA to track it for next release! >>> >>> thanks, >>> >>> --larry >>> >>> On Fri, Feb 2, 2018 at 2:47 PM, Phil Zampino <[email protected]> >>> wrote: >>> >>>> While testing rc 2, I have discovered a bug in the Ambari cluster >>>> monitoring, which is NOT a blocker IMO. >>>> >>>> The cluster monitor caches cluster configuration version data, which it >>>> uses to compare with Ambari’s record of the active configuration. >>>> When topologies are undeployed, such that there are no remaining >>>> topologies >>>> associated with the Ambari cluster being monitored, the monitor >>>> continues >>>> to: >>>> >>>> - Monitor the cluster configuration >>>> - Notify listeners of the change >>>> - Log messages about the change >>>> >>>> >>>> I’ve filed KNOX-1169 <https://issues.apache.org/jira/browse/KNOX-1169> >>>> to >>>> address this, and I’ve already committed the fix to master. When there >>>> are >>>> no remaining topologies based on a particular cluster configuration, the >>>> monitor will remove its record; this resolves all of the items in the >>>> aforementioned list. >>>> >>>> For the 1.0.0 release, the work-around is to manually delete the >>>> corresponding file from the {KNOX_HOME}/data/clusters/ directory. >>>> >>>> >>>> >>>> On Thu, Feb 1, 2018 at 12:34 AM, larry mccay <[email protected]> wrote: >>>> >>>> > A candidate for the Apache Knox 1.0.0 release is available at: >>>> > >>>> > https://dist.apache.org/repos/dist/dev/knox/knox-1.0.0/ >>>> > >>>> > The release candidate is a zip archive of the sources in: >>>> > >>>> > https://git-wip-us.apache.org/repos/asf/knox.git >>>> > Branch v1.0.0 (git checkout -b v1.0.0) >>>> > Git Tag: v1.0.0-rc2 >>>> > >>>> > 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.0.0. >>>> > >>>> > This release is nearly identical to 0.14.0 with the exception of: >>>> > >>>> > * repackaging of the classes to remove "hadoop" from the package >>>> > names >>>> > * handful of patches for rounding out service discovery >>>> > and topology generation >>>> > * moved the Apache Hadoop dependency to Hadoop 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.0.0 >>>> > [ ] -1 Do not release this package because... >>>> > >>>> >>> >>> >> >
