You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Andor Molnar <an...@apache.org> on 2019/10/11 20:33:58 UTC
New feature in 3.5: Audit logging
Hi devs,
Mohammad would like to add Audit logging to 3.5 branch as a new feature once the patch is ready.
3.5 is already locked for adding new features, so I would say it should be added to 3.6 only, but that’s only me. What do you think about that?
Shall we backport audit logging to 3.5 branch?
Andor
RE: New feature in 3.5: Audit logging
Posted by Mohammad arshad <mo...@huawei.com>.
No problem, we can push only to master branch.
Thanks & Regards
Mohammad Arshad
System Architect
Enterprise Intelligence, IT & Cloud BL
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru, Karnataka - 560066
Tel: + 91-80-49160700 Ext 71575 II Mob: 9886451400 Email: mohammad.arshad@huawei.com
This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
-----Original Message-----
From: Brian Nixon [mailto:brian.nixon.cs@gmail.com]
Sent: Wednesday, October 16, 2019 5:43 AM
To: dev@zookeeper.apache.org
Subject: Re: New feature in 3.5: Audit logging
I'd say 3.6 and not 3.5 in order to maintain the stable character of the latter.
On Sat, Oct 12, 2019 at 12:05 PM Enrico Olivelli <eo...@gmail.com>
wrote:
> Il ven 11 ott 2019, 23:48 Patrick Hunt <ph...@apache.org> ha scritto:
>
> > Per recent discussions we should really push for 3.6+, esp given
> > lessons learned from 3.5 and the plan to get 3.6stable out there quickly.
> >
> > Is there a strong reason for 3.5? What are the implications of 3.5,
> > ie
> does
> > it break b/w compat or just additive? (etc...)
> >
>
> It is just additive but it is not a trivial change.
>
> In my opinion we should put it in 3.6.
>
> I guess we will see 3.6.0 delivered before the end of this year.
>
>
> Enrico
>
> >
> > Patrick
> >
> > On Fri, Oct 11, 2019 at 1:34 PM Andor Molnar <an...@apache.org> wrote:
> >
> > > Hi devs,
> > >
> > > Mohammad would like to add Audit logging to 3.5 branch as a new
> > > feature once the patch is ready.
> > >
> > > 3.5 is already locked for adding new features, so I would say it
> > > should
> > be
> > > added to 3.6 only, but that’s only me. What do you think about that?
> > >
> > > Shall we backport audit logging to 3.5 branch?
> > >
> > > Andor
> > >
> > >
> > >
> >
>
Re: New feature in 3.5: Audit logging
Posted by Brian Nixon <br...@gmail.com>.
I'd say 3.6 and not 3.5 in order to maintain the stable character of the
latter.
On Sat, Oct 12, 2019 at 12:05 PM Enrico Olivelli <eo...@gmail.com>
wrote:
> Il ven 11 ott 2019, 23:48 Patrick Hunt <ph...@apache.org> ha scritto:
>
> > Per recent discussions we should really push for 3.6+, esp given lessons
> > learned from 3.5 and the plan to get 3.6stable out there quickly.
> >
> > Is there a strong reason for 3.5? What are the implications of 3.5, ie
> does
> > it break b/w compat or just additive? (etc...)
> >
>
> It is just additive but it is not a trivial change.
>
> In my opinion we should put it in 3.6.
>
> I guess we will see 3.6.0 delivered before the end of this year.
>
>
> Enrico
>
> >
> > Patrick
> >
> > On Fri, Oct 11, 2019 at 1:34 PM Andor Molnar <an...@apache.org> wrote:
> >
> > > Hi devs,
> > >
> > > Mohammad would like to add Audit logging to 3.5 branch as a new feature
> > > once the patch is ready.
> > >
> > > 3.5 is already locked for adding new features, so I would say it should
> > be
> > > added to 3.6 only, but that’s only me. What do you think about that?
> > >
> > > Shall we backport audit logging to 3.5 branch?
> > >
> > > Andor
> > >
> > >
> > >
> >
>
Re: New feature in 3.5: Audit logging
Posted by Enrico Olivelli <eo...@gmail.com>.
Il ven 11 ott 2019, 23:48 Patrick Hunt <ph...@apache.org> ha scritto:
> Per recent discussions we should really push for 3.6+, esp given lessons
> learned from 3.5 and the plan to get 3.6stable out there quickly.
>
> Is there a strong reason for 3.5? What are the implications of 3.5, ie does
> it break b/w compat or just additive? (etc...)
>
It is just additive but it is not a trivial change.
In my opinion we should put it in 3.6.
I guess we will see 3.6.0 delivered before the end of this year.
Enrico
>
> Patrick
>
> On Fri, Oct 11, 2019 at 1:34 PM Andor Molnar <an...@apache.org> wrote:
>
> > Hi devs,
> >
> > Mohammad would like to add Audit logging to 3.5 branch as a new feature
> > once the patch is ready.
> >
> > 3.5 is already locked for adding new features, so I would say it should
> be
> > added to 3.6 only, but that’s only me. What do you think about that?
> >
> > Shall we backport audit logging to 3.5 branch?
> >
> > Andor
> >
> >
> >
>
Re: New feature in 3.5: Audit logging
Posted by Patrick Hunt <ph...@apache.org>.
Per recent discussions we should really push for 3.6+, esp given lessons
learned from 3.5 and the plan to get 3.6stable out there quickly.
Is there a strong reason for 3.5? What are the implications of 3.5, ie does
it break b/w compat or just additive? (etc...)
Patrick
On Fri, Oct 11, 2019 at 1:34 PM Andor Molnar <an...@apache.org> wrote:
> Hi devs,
>
> Mohammad would like to add Audit logging to 3.5 branch as a new feature
> once the patch is ready.
>
> 3.5 is already locked for adding new features, so I would say it should be
> added to 3.6 only, but that’s only me. What do you think about that?
>
> Shall we backport audit logging to 3.5 branch?
>
> Andor
>
>
>