Hi All,
We are evolving guidelines for managing maintainer lifecycle and will
be sharing the document here soon. Let us adhere to the new process
outlined there for all changes to MAINTAINERS going forward.
Thanks!
Vijay
On Wed, May 18, 2016 at 2:28 AM, Saravanakumar Arumugam
Hi,
On 05/13/2016 11:19 AM, Venky Shankar wrote:
On 16-05-11 11:55:10, Aravinda wrote:
I would like to propose Kotresh. +2 from my side.
Thanks Aravinda. Noted.
It would be great to also have a backup maintainer. Anyone for that?
I am volunteering for backup maintainer.
Thanks,
Saravana
On 16-05-11 11:55:10, Aravinda wrote:
> I would like to propose Kotresh. +2 from my side.
Thanks Aravinda. Noted.
It would be great to also have a backup maintainer. Anyone for that?
>
> regards
> Aravinda
>
> On 05/11/2016 10:25 AM, Venky Shankar wrote:
> >Hello,
> >
> >I'm wanting to
I would like to propose Kotresh. +2 from my side.
regards
Aravinda
On 05/11/2016 10:25 AM, Venky Shankar wrote:
Hello,
I'm wanting to relinquish maintainership for changelog[1] translator.
For the uninformed, changelog xlator is the supporting infrastructure for
features
such as
Hello,
I'm wanting to relinquish maintainership for changelog[1] translator.
For the uninformed, changelog xlator is the supporting infrastructure for
features
such as Geo-replication, Bitrot and glusterfind. However, this would eventually
be
replaced by FDL[2] when it's ready and the
