Thank you Ali. However the release manager has be an Apache committer first, since it requires permissions to access ASF infrastructure for the whole release process.
- Sijie On Mon, Aug 20, 2018 at 2:50 PM Ali Ahmed <ahmal...@gmail.com> wrote: > I will volunteer. > > -Ali > > On Mon, Aug 20, 2018 at 2:45 PM Sijie Guo <guosi...@gmail.com> wrote: > > > Anyone volunteer for releasing 2.2? > > > > - Sijie > > > > On Thu, Aug 16, 2018 at 12:02 AM Sijie Guo <guosi...@gmail.com> wrote: > > > > > Any committer volunteer for releasing 2.2? > > > > > > - Sijie > > > > > > On Wed, Aug 8, 2018 at 11:43 AM Sanjeev Kulkarni <sanjee...@gmail.com> > > > wrote: > > > > > >> The timeline sounds good! > > >> One more thing that users have asked about is feature parity between > > >> python > > >> and java clients so we should have some work items associated with > this > > >> task as well. > > >> > > >> > > >> On Wed, Aug 8, 2018 at 11:40 AM Sijie Guo <guosi...@gmail.com> wrote: > > >> > > >> > Hi all, > > >> > > > >> > Although we just announced 2.1, we already have a lot of new > features > > >> > merged since 2.1 candidate is cut. For example, Pulsar SQL, GCS > > support > > >> as > > >> > tiered storage and such. Shall we target at releasing 2.2 at the end > > of > > >> > August? Since releasing usually takes 1~2 weeks, that would be > > released > > >> > around Mid September. > > >> > > > >> > What are the thoughts around this? > > >> > > > >> > Any committers volunteer to drive 2.2 release? > > >> > > > >> > - Sijie > > >> > > > >> > > > > > > > > -- > -Ali >
