I'd be happy to manage the 2.1.2 maintenance release (and 2.2.1 after that) if people are ok with a committer / me running the release process rather than a full PMC member.
On Thu, Sep 7, 2017 at 1:05 PM, Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > +1! > > As of today, > > For 2.1.2, we have 87 commits. (2.1.1 was released 4 months ago) > For 2.2.1, we have 95 commits. (2.2.0 was released 2 months ago) > > Can we have 2.2.1, too? > > Bests, > Dongjoon. > > > On Thu, Sep 7, 2017 at 2:14 AM, Sean Owen <so...@cloudera.com> wrote: > >> In a separate conversation about bugs and a security issue fixed in 2.1.x >> and 2.0.x, Marcelo suggested it could be time for a maintenance release. >> I'm not sure what our stance on 2.0.x is, but 2.1.2 seems like it could be >> valuable to release. >> >> Thoughts? I believe Holden had expressed interest in even managing the >> release process, but maybe others are interested as well. That is, this >> could also be a chance to share that burden and spread release experience >> around a bit. >> >> Sean >> > > -- Cell : 425-233-8271 Twitter: https://twitter.com/holdenkarau
