Thanks for all the feedback! Just to close out the discussion on timeline, I think it makes some sense to add a few days because we have Thanksgiving in the middle and our list of issues already marked 0.11.0 is reasonably aggressive. Let¹s call the target date as 12/19. Any later than that we of course get into Christmas holidays, so lets try and meet the date so that the release doesn¹t get pushed into next year.
As the KIPs start developing further and the JIRA issues marked for 0.11.0 solidify I¹ll send out another email with the definitive list we are targeting for the release. Thanks again and I look forward to a solid 0.11.0 release. Sumit On 11/9/16, 10:30 AM, "larry mccay" <[email protected]> wrote: >Hi Sumit - > >Thanks for volunteering to be release manager again! > >I think that the KIPs that are showing up are a great way to communicate >our roadmap and vision for the various functional areas. >We shouldn't limit the KIPs to what can be done in any given release but >provide a roadmap of incremental improvements that may be accomplished >over >the course of some number of releases. > >To that end, I plan to start a KIP for KnoxShell improvements. >As we see more and more movement to cloud deployments, I believe that we >are going to see more demand for users to be able to get their jobs done >without the need to ssh into the cluster. > >The KnoxShell provides a pretty powerful scripting and programming model >that doesn't require a Hadoop install, much if any config and little >dependence on client side jars. This could easily become a popular >programming model for Hadoop in the cloud. > >We just need to define what that programming model is, its goals and >target >user, etc. >Thus the need for the KnoxShell KIP. > >The KIP-1 (LDAP Improvements), KIP-2 (Metrics) and KIP-3 (Websockets) >documents be central in our planning for 0.11.0 and refined to reflect >what >is expected to be outstanding after 0.11.0. > >+1 on a month target for 0.11.0. > >Should we call it 12/12? > >thanks again, > >--larry > >On Wed, Nov 9, 2016 at 10:09 AM, Sandeep More <[email protected]> >wrote: > >> Thanks Sumit ! >> >> I created few JIRAs as a followup to Websocket support, they are as >> follows: >> >> KNOX-772 - Implement binary protocol support for Websocket feature >> KNOX-773 - Secure websocket support on the dispatch side and security >> enhancements >> KNOX-774 - Make websocket connections Async and Non-Blocking >> KNOX-775 - Create a generic framework that can be reused and extended by >> other protocols >> KNOX-776 - Rewrite rule handling for websockets >> KNOX-777 - Address websocket scalability >> >> I linked them to KIP-3 so that I don't lose track of it, I will update >>the >> list if I come up with others. Month long timeline for 0.11 sounds good >>to >> me ! >> >> Thanks for volunteering ! >> >> Best, >> Sandeep >> >> >> >> On Wed, Nov 9, 2016 at 9:34 AM, Sumit Gupta >><[email protected]> >> wrote: >> >> > Hey everyone, >> > >> > Now that 0.10.0 is out, we should start nailing down our plans for >>0.11.0 >> > both in terms of features/fixes as well as timeline. >> > >> > Some of the big features I am aware of from previous discussions and >>JIRA >> > activity are: >> > >> > 1. Admin UI (KNOX-749) >> > 2. Metrics implementation (KNOX-643) >> > 3. Druid support (KNOX-758, KNOX-763) >> > >> > Also, Larry has some thoughts on improvements to the client shell that >> I'm >> > sure he will share will us. There is also likely some follow on >>websocket >> > and ldap work... other thoughts and JIRAs are welcome to be added to >>the >> > list. >> > >> > In terms of timeline. We have been incrementally getting better at >> > releasing more frequently and are certainly constantly trying to get >> better >> > at it. I propose a month long timeline for 0.11.0. >> > >> > Also, I volunteer to manage this release unless someone else is keen >>to >> do >> > so. >> > >> > Thanks! >> > Sumit >> > >> > >>
