Hi Maksim,

Thanks a lot for using Apache Ratis and Ozone!

Unfortunately, the Apache policy requires committers to serve as a release
manager; sorry about that.
- https://infra.apache.org/release-publishing.html#releasemanager

Tsz-Wo

On Tue, Nov 1, 2022 at 11:59 AM Maksim Myskov <[email protected]> wrote:

> Hi Apache Ratis devs,
>
> I actively use Apache Ozone and Ratis in my work, so highly interested in
> the development of these two projects.
> I’m not an official apache committer (I don’t have account on id.apche.org).
> If possible, I would love to be a release manager this time.
>
> > On 1 Nov 2022, at 07:48, Tsz Wo Sze <[email protected]> wrote:
> >
> > Let's start to roll thirdparty 1.0.3 and ratis 2.4.1 releases.  Does
> anyone
> > like to be the release manager?
> >
> > Tsz-Wo
> >
> >
> >
> > On Thu, Oct 27, 2022 at 10:58 PM Yaolong Liu <[email protected]> wrote:
> >
> >> Hi William,
> >>
> >>
> >> Thanks for starting a discussion on 2.4.1!  +1 on rolling a 2.4.1
> release.
> >>
> >>
> >> -Yaolong
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> At 2022-10-25 19:20:32, "William Song" <[email protected]> wrote:
> >>> Hi Ratis Community,
> >>>
> >>> It’s really great to see Ratis releases 2.4.0. Unfortunately, there are
> >> some important fixes missing in 2.4.0, like RATIS-1708 and RATIS-1729.
> >>>
> >>> I would like to propose a new Ratis release 2.4.1 (including
> >> ratis-thirdparty 1.0.3) with the above changes. Since Apache IoTDB 1.0
> >> release (frozen by 11.15) is waiting for Ratis, we would be really
> >> appreciate if the 2.4.1 be released in the coming weeks.
> >>>
> >>> Please help me check if there are other commits missing in 2.4.0.
> Thanks
> >> in advance!
> >>>
> >>>
> >>> Regards,
> >>> William
> >>
>
>
>

Reply via email to