Hi Jordan, Alejandro,

This is not a mistake, security is not on my proposed roadmap for 1.0. The reasoning for 1.0 is that "enough people" would want to deploy it in production, obviously some are already doing it, so the other side of this is that some folks wouldn't be able to deploy it yet. Speculating a little, I could see security as a 2.0 feature.

But, as I said in my email, if anyone shows up with different priorities (and more importantly patches), it could shape a different 1.0.

Hope this helps,


On Tue, Feb 23, 2016 at 11:52 AM, Alejandro de la Vina <a.delavina@globant.com> wrote:
Myself and my employing company share Jordans feeling on this perspective. 
I am most likely missing a particular issue/request on this matter since I still have a late Fall/early Winter expectation.

On Tue, Feb 23, 2016 at 4:45 PM, Jordan Birdsell <jordan.birdsell.kdvm@statefarm.com> wrote:

Is there any intention to add some form of security with 1.0?  I did not see any mention of this in the thread.  I think this would be a must have for most adopters, including my company.


From: Jean-Daniel Cryans [mailto:jdcryans@apache.org]
Sent: Tuesday, February 23, 2016 12:38 PM
To: user@kudu.incubator.apache.org
Subject: Re: Kudu Release


Thanks Ben :)


Hopefully we can release 0.7.0 this week, the vote is currently happening on the incubator general mailing list and closes tomorrow.




On Tue, Feb 23, 2016 at 9:27 AM, Benjamin Kim <bbuild11@gmail.com> wrote:



Very organized outline. Looking forward to the 0.7 release. I am hoping that most of your points are addressed and completed by 1.0 release this fall.






On Feb 23, 2016, at 8:31 AM, Jean-Daniel Cryans <jdcryans@apache.org> wrote:



On Tue, Feb 23, 2016 at 8:23 AM, Benjamin Kim <bbuild11@gmail.com> wrote:

Any word as to the release roadmap?





The information contained in this e-mail may be confidential. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution or copying of this communication, or any of its contents, is strictly prohibited. If you have received it by mistake please let us know by e-mail immediately and delete it from your system. Many thanks.


La información contenida en este mensaje puede ser confidencial. Ha sido enviada para el uso exclusivo del destinatario(s) previsto. Si el lector de este mensaje no fuera el destinatario previsto, por el presente queda Ud. notificado que cualquier lectura, uso, publicación, diseminación, distribución o copiado de esta comunicación o su contenido está estrictamente prohibido. En caso de que Ud. hubiera recibido este mensaje por error le agradeceremos notificarnos por e-mail inmediatamente y eliminarlo de su sistema. Muchas gracias.