Hi Arturo Michel,

The Shiro authentication is already part of the Master branch, however you
will have to build it.
There is no date for next release yet, however since we are trying to
graduate as a top project, there might be one right after (to change names
etc...)

For infos on how to contribute, you should find everything in this document:
https://github.com/apache/incubator-zeppelin/blob/master/CONTRIBUTING.md

On Tue, Apr 19, 2016 at 6:21 AM, Steven Kirtzic <
steven.kirtzic.f...@statefarm.com> wrote:

> Same here. Thanks,
>
>
>
> -Steven
>
>
>
> *From:* Jordan Birdsell [mailto:jordan.birdsell.k...@statefarm.com]
> *Sent:* Monday, April 18, 2016 10:14 AM
> *To:* users@zeppelin.incubator.apache.org
> *Subject:* RE: Zeppelin 0.6.0
>
>
>
> I have the same interest in 0.6.0’s release, and for compliance reasons am
> unable to build from source internally.
>
>
>
> *From:* Arturo Michel [mailto:arturo.mic...@leotech.com.sg
> <arturo.mic...@leotech.com.sg>]
> *Sent:* Monday, April 18, 2016 10:20 AM
> *To:* users@zeppelin.incubator.apache.org
> *Subject:* FW: Zeppelin 0.6.0
>
>
>
> Hello Zeppelin,
>
>
>
> We are hoping to adopt Zeppelin for one of our customer’s data analysis
> project. But, we would need authentication to be available. I’ve noticed
> the work done with Shiro, which is great and we would develop on top of
> this.
>
>
>
> Is there an estimated date for the next Zeppelin release?
>
>
>
> Very much appreciated. Also where can I find info on how to become a
> contributor?
>
>
>
> Best Regards.
>
>
>
>
>
> This email is intended only for the individual or entity to which it is
> addressed and may contain information that is private, restricted,
> confidential or secret and exempt from disclosure under applicable law.
>
> If the reader of this disclaimer is not the intended recipient, you are
> hereby notified that any dissemination, distribution or copying of this
> document is strictly prohibited. If you received this in error, please
> notify the sender and delete it immediately after reading this disclaimer.
>
> Thank you.
>
>
>
>
>
>

Reply via email to