Hey all, I want to revive this thread one more time to try and close down the 0.12.0 release. Since no one has volunteered to manage the release I am volunteering for that as well.
To summarize where we are: 1. We have about 14 outstanding issues marked for 0.12.0 (I am using the fixVersion attribute in JIRA). 2. We have resolved about 45 issues for this release. There are a lot of neat features and improvements worthy of a release at this point. We also have a new release module for the KnoxShell that we need to make available. Therefore I propose the following: 1. Let’s close down the release by end of next week by the latest (it really should be sooner) - that is March 3rd. 2. Any new JIRA issues should be filed against 0.13.0 unless they are considered show stopper issues for the 0.12.0 release. Thoughts? Sumit. On 1/20/17, 10:22 AM, "larry mccay" <[email protected]> wrote: >I agree, Sumit. > >In fact, I have a local feature branch for client changes that enable the >use of a token based authentication through KnoxShell along with command >lines for acquiring and storing a token from a new KnoxToken service to be >found by the KnoxShell. This will provide us with an SSO session at the >terminal that is similar to kerberos. > >I believe that this sort of client tooling requires some client-only >release vehicle and/or download capability. > >I planned to bring this up as a DISCUSS thread itself but we can make it >part of the scoping thread that you propose here. > >On Fri, Jan 20, 2017 at 10:12 AM, Sumit Gupta ><[email protected]> >wrote: > >> Hey everyone, >> >> I wanted to circle back to this discussion on the next release. As I am >> writing this email there are 39 open issues marked up for 0.12.0. About >>10 >> of them have patches available but still need to be tested and merged. >> That still leaves us with a lot of open issues to get to with the >>original >> time frame in mind. I propose that we spend some more time rationalizing >> what we want to go into the next release and come up with a new target >> release date. >> >> If we want to remain focused on KnoxShell improvements we probably also >> need to have a separate DISCUSS thread on scoping that effort for the >>next >> release and talk about what it will mean to get it out of beta mode. >> >> Sumit. >> >> On 12/27/16, 4:29 PM, "Sumit Gupta" <[email protected]> wrote: >> >> >Sounds great! I am impressed with the uptake of the KnoxShell in the >> >community and just KIP-4 is probably worthy of a quick release. So I >> >second the focus as well as the release timeframe. We should also talk >> >about how to take the client shell and its programming capabilities >>out of >> >the Œbeta¹ type of positioning we have in docs and maybe highlight it >>as a >> >prominent feature of Knox. >> > >> >Good stuff! I look forward to 0.12.0! >> > >> >Sumit >> > >> > >> > >> >On 12/27/16, 3:27 PM, "larry mccay" <[email protected]> wrote: >> > >> >>All - >> >> >> >>As we are wrapping up the VOTE for 0.11.0, we should start to consider >> >>the >> >>focus of the 0.12.0 release. >> >> >> >>We already have a sizable collection of JIRAs assigned to 0.12.0, ~30 >> >>actually. >> >>Nearly 10 already have patches available and are largely if not >>entirely >> >>focused on the KIP-4 KnoxShell Improvements [1] space. >> >> >> >>I propose that we make KIP-4 the driving focus of 0.12.0 with the >> >>continued >> >>work on outstanding issues from previous releases and KIPs. >> >> >> >>Additionally, there are some continued improvements that could be >>added >> >>to >> >>the Admin UI such as surfacing some of the metrics work done in 0.10.0 >> >>and >> >>perhaps gateway-site.xml config. >> >> >> >>As for timing, I would like to suggest the end of January (31st) for >>now >> >>and see what we can get done in that timeframe. >> >> >> >>Thoughts? >> >> >> >>thanks, >> >> >> >>--larry >> >> >> >> >> >>1. >> >>https://cwiki.apache.org/confluence/display/KNOX/KIP-4+ >> KnoxShell+Improvem >> >>e >> >>nts >> > >> > >> >>
