You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ratis.apache.org by Xinyu Tan <ta...@apache.org> on 2025/09/23 16:44:46 UTC
[VOTE] Apache Ratis Release 3.2.1 rc1
Hi Ratis community,
I’m calling a vote For Apache Ratis Release 3.2.1 rc1.
The git tag to be vote upon:
https://github.com/apache/ratis/tree/ratis-3.2.1-rc1
The git commit hash:
9156998c9be938bc5161368bf83671f72acd47e9
The source and binary tarballs can be found at:
https://dist.apache.org/repos/dist/dev/ratis/3.2.1/rc1
Fingerprint of the GPG key release artifacts are signed with:
055D2E860E43CBB155D09AA4BECD7978EE4DA7BC
My public key to verify signatures can be found in:
https://dist.apache.org/repos/dist/release/ratis/KEYS
Maven artifacts are staged at:
https://repository.apache.org/content/repositories/orgapacheratis-1170
This vote will remain open for at least 7 days.
Please vote on releasing this ratis-3.2.1-rc1. Thanks in advance.
[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)
Starting with my +1
- Verified checksums, signatures and git hash.
- Checked LICENSE and NOTICE.
- Compared the files in src tarball with the files at the given git tag.
- Built from source.
- Ran regular Ratis CI. [1]
[1] https://github.com/apache/ratis/actions/runs/17952537892
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Tsz Wo Sze <sz...@apache.org>.
Hi Xinyu,
Sounds good, let's wait for RATIS-2329.
Tsz-Wo
On Sat, Oct 4, 2025 at 8:59 PM Xinyu Tan <ta...@apache.org> wrote:
> Hi, Tsz Wo
>
> Let’s patiently wait for the merge of Ratis 2329 to ensure that the
> Celeborn community can fix this replication stuck issue in the 3.2.1
> release. I think it can be completed and merged after the National holiday.
>
> Best
> -------------
> Xinyu Tan
>
> On 2025/10/02 16:46:57 Tsz Wo Sze wrote:
> > Hi Xinyu,
> >
> > I am fine either way.
> >
> > RATIS-2329 is missing super.channelInactive(ctx). If the current code is
> > working, it is okay to merge it without adding
> super.channelInactive(ctx).
> > We may add it later if there is a problem.
> >
> > Tsz-Wo
> >
> >
> > On Thu, Oct 2, 2025 at 6:15 AM Xinyu Tan <ta...@apache.org> wrote:
> >
> > > Hi
> > >
> > > As ratis 2332, 2339 and 2337 has been merged, maybe we can start
> > > releasing rc2? Or I can wait for the mergement of 2329, it's good to
> me now~
> > >
> > > Best
> > > ---------------
> > > Xinyu Tan
> > >
> > > On 2025/09/28 14:50:29 Xinyu Tan wrote:
> > > > Hi, all
> > > >
> > > > Thank you all for the reminders. It appears that I did not clean up
> the
> > > previous tag properly, which caused an issue with the tag uploaded for
> rc1.
> > > I will pay attention to this when preparing rc2.
> > > >
> > > > As for whether the tag should be pushed only before sending out the
> > > email, I do need the CI status for the corresponding tag each time I
> send a
> > > voting email. Once an rc needs to be redone, the earlier steps with
> svn and
> > > mvn must be repeated, which is unavoidable. I believe it is reasonable
> to
> > > push the release and tag together, verify that CI passes, and then
> send the
> > > email; if CI fails, we should delete the corresponding branch and tag
> and
> > > redo the process. I have opened a new PR [1] for this.
> > > >
> > > > In addition, I plan to prioritize merging 2239 and 2238, then cut rc2
> > > from the latest commit on master. If 2329 can be updated in time, it
> can be
> > > included as well. I expect to release rc2 before the National Day
> holiday.
> > > Let us review and merge these PRs these days!
> > > >
> > > > [1] https://github.com/apache/ratis/pull/1293
> > > >
> > > > Best
> > > > ----------------
> > > > Xinyu Tan
> > > >
> > > >
> > > > On 2025/09/28 07:46:51 Attila Doroszlai wrote:
> > > > > Hi Xinyu,
> > > > >
> > > > > Thanks for working on the release.
> > > > >
> > > > > Please push your local RC branch to the apache/ratis repo.
> According
> > > > > to the naming convention it should be "release-3.2.1"
> > > > > (https://github.com/apache/ratis/branches/all?query=release).
> This
> > > > > will fix the "commit does not belong to any branch on this
> repository"
> > > > > issue.
> > > > >
> > > > > The tag (ratis-3.2.1-rc1) should be pushed only before sending out
> the
> > > > > RC vote email, to avoid having to re-create it in case of any CI
> > > > > problem (which could be seen in the branch's runs).
> > > > >
> > > > > Original:
> > > > >
> > > > > tag ratis-3.2.1-rc1
> > > > > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > > > > Date: Sun Sep 7 13:15:16 2025 +0800
> > > > > ...
> > > > > commit 93632a93a6013dd9946e5297cfba61c39e1f1239 (tag:
> ratis-3.2.1-rc1)
> > > > >
> > > > > Current:
> > > > >
> > > > > tag ratis-3.2.1-rc1
> > > > > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > > > > Date: Wed Sep 24 00:04:45 2025 +0800
> > > > > ...
> > > > > commit 9156998c9be938bc5161368bf83671f72acd47e9 (tag:
> ratis-3.2.1-rc1)
> > > > >
> > > > > -Attila
> > > > >
> > > >
> > >
> >
>
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Xinyu Tan <ta...@apache.org>.
Hi, Tsz Wo
Let’s patiently wait for the merge of Ratis 2329 to ensure that the Celeborn community can fix this replication stuck issue in the 3.2.1 release. I think it can be completed and merged after the National holiday.
Best
-------------
Xinyu Tan
On 2025/10/02 16:46:57 Tsz Wo Sze wrote:
> Hi Xinyu,
>
> I am fine either way.
>
> RATIS-2329 is missing super.channelInactive(ctx). If the current code is
> working, it is okay to merge it without adding super.channelInactive(ctx).
> We may add it later if there is a problem.
>
> Tsz-Wo
>
>
> On Thu, Oct 2, 2025 at 6:15 AM Xinyu Tan <ta...@apache.org> wrote:
>
> > Hi
> >
> > As ratis 2332, 2339 and 2337 has been merged, maybe we can start
> > releasing rc2? Or I can wait for the mergement of 2329, it's good to me now~
> >
> > Best
> > ---------------
> > Xinyu Tan
> >
> > On 2025/09/28 14:50:29 Xinyu Tan wrote:
> > > Hi, all
> > >
> > > Thank you all for the reminders. It appears that I did not clean up the
> > previous tag properly, which caused an issue with the tag uploaded for rc1.
> > I will pay attention to this when preparing rc2.
> > >
> > > As for whether the tag should be pushed only before sending out the
> > email, I do need the CI status for the corresponding tag each time I send a
> > voting email. Once an rc needs to be redone, the earlier steps with svn and
> > mvn must be repeated, which is unavoidable. I believe it is reasonable to
> > push the release and tag together, verify that CI passes, and then send the
> > email; if CI fails, we should delete the corresponding branch and tag and
> > redo the process. I have opened a new PR [1] for this.
> > >
> > > In addition, I plan to prioritize merging 2239 and 2238, then cut rc2
> > from the latest commit on master. If 2329 can be updated in time, it can be
> > included as well. I expect to release rc2 before the National Day holiday.
> > Let us review and merge these PRs these days!
> > >
> > > [1] https://github.com/apache/ratis/pull/1293
> > >
> > > Best
> > > ----------------
> > > Xinyu Tan
> > >
> > >
> > > On 2025/09/28 07:46:51 Attila Doroszlai wrote:
> > > > Hi Xinyu,
> > > >
> > > > Thanks for working on the release.
> > > >
> > > > Please push your local RC branch to the apache/ratis repo. According
> > > > to the naming convention it should be "release-3.2.1"
> > > > (https://github.com/apache/ratis/branches/all?query=release). This
> > > > will fix the "commit does not belong to any branch on this repository"
> > > > issue.
> > > >
> > > > The tag (ratis-3.2.1-rc1) should be pushed only before sending out the
> > > > RC vote email, to avoid having to re-create it in case of any CI
> > > > problem (which could be seen in the branch's runs).
> > > >
> > > > Original:
> > > >
> > > > tag ratis-3.2.1-rc1
> > > > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > > > Date: Sun Sep 7 13:15:16 2025 +0800
> > > > ...
> > > > commit 93632a93a6013dd9946e5297cfba61c39e1f1239 (tag: ratis-3.2.1-rc1)
> > > >
> > > > Current:
> > > >
> > > > tag ratis-3.2.1-rc1
> > > > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > > > Date: Wed Sep 24 00:04:45 2025 +0800
> > > > ...
> > > > commit 9156998c9be938bc5161368bf83671f72acd47e9 (tag: ratis-3.2.1-rc1)
> > > >
> > > > -Attila
> > > >
> > >
> >
>
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Tsz Wo Sze <sz...@apache.org>.
Hi Xinyu,
I am fine either way.
RATIS-2329 is missing super.channelInactive(ctx). If the current code is
working, it is okay to merge it without adding super.channelInactive(ctx).
We may add it later if there is a problem.
Tsz-Wo
On Thu, Oct 2, 2025 at 6:15 AM Xinyu Tan <ta...@apache.org> wrote:
> Hi
>
> As ratis 2332, 2339 and 2337 has been merged, maybe we can start
> releasing rc2? Or I can wait for the mergement of 2329, it's good to me now~
>
> Best
> ---------------
> Xinyu Tan
>
> On 2025/09/28 14:50:29 Xinyu Tan wrote:
> > Hi, all
> >
> > Thank you all for the reminders. It appears that I did not clean up the
> previous tag properly, which caused an issue with the tag uploaded for rc1.
> I will pay attention to this when preparing rc2.
> >
> > As for whether the tag should be pushed only before sending out the
> email, I do need the CI status for the corresponding tag each time I send a
> voting email. Once an rc needs to be redone, the earlier steps with svn and
> mvn must be repeated, which is unavoidable. I believe it is reasonable to
> push the release and tag together, verify that CI passes, and then send the
> email; if CI fails, we should delete the corresponding branch and tag and
> redo the process. I have opened a new PR [1] for this.
> >
> > In addition, I plan to prioritize merging 2239 and 2238, then cut rc2
> from the latest commit on master. If 2329 can be updated in time, it can be
> included as well. I expect to release rc2 before the National Day holiday.
> Let us review and merge these PRs these days!
> >
> > [1] https://github.com/apache/ratis/pull/1293
> >
> > Best
> > ----------------
> > Xinyu Tan
> >
> >
> > On 2025/09/28 07:46:51 Attila Doroszlai wrote:
> > > Hi Xinyu,
> > >
> > > Thanks for working on the release.
> > >
> > > Please push your local RC branch to the apache/ratis repo. According
> > > to the naming convention it should be "release-3.2.1"
> > > (https://github.com/apache/ratis/branches/all?query=release). This
> > > will fix the "commit does not belong to any branch on this repository"
> > > issue.
> > >
> > > The tag (ratis-3.2.1-rc1) should be pushed only before sending out the
> > > RC vote email, to avoid having to re-create it in case of any CI
> > > problem (which could be seen in the branch's runs).
> > >
> > > Original:
> > >
> > > tag ratis-3.2.1-rc1
> > > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > > Date: Sun Sep 7 13:15:16 2025 +0800
> > > ...
> > > commit 93632a93a6013dd9946e5297cfba61c39e1f1239 (tag: ratis-3.2.1-rc1)
> > >
> > > Current:
> > >
> > > tag ratis-3.2.1-rc1
> > > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > > Date: Wed Sep 24 00:04:45 2025 +0800
> > > ...
> > > commit 9156998c9be938bc5161368bf83671f72acd47e9 (tag: ratis-3.2.1-rc1)
> > >
> > > -Attila
> > >
> >
>
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Xinyu Tan <ta...@apache.org>.
Hi
As ratis 2332, 2339 and 2337 has been merged, maybe we can start releasing rc2? Or I can wait for the mergement of 2329, it's good to me now~
Best
---------------
Xinyu Tan
On 2025/09/28 14:50:29 Xinyu Tan wrote:
> Hi, all
>
> Thank you all for the reminders. It appears that I did not clean up the previous tag properly, which caused an issue with the tag uploaded for rc1. I will pay attention to this when preparing rc2.
>
> As for whether the tag should be pushed only before sending out the email, I do need the CI status for the corresponding tag each time I send a voting email. Once an rc needs to be redone, the earlier steps with svn and mvn must be repeated, which is unavoidable. I believe it is reasonable to push the release and tag together, verify that CI passes, and then send the email; if CI fails, we should delete the corresponding branch and tag and redo the process. I have opened a new PR [1] for this.
>
> In addition, I plan to prioritize merging 2239 and 2238, then cut rc2 from the latest commit on master. If 2329 can be updated in time, it can be included as well. I expect to release rc2 before the National Day holiday. Let us review and merge these PRs these days!
>
> [1] https://github.com/apache/ratis/pull/1293
>
> Best
> ----------------
> Xinyu Tan
>
>
> On 2025/09/28 07:46:51 Attila Doroszlai wrote:
> > Hi Xinyu,
> >
> > Thanks for working on the release.
> >
> > Please push your local RC branch to the apache/ratis repo. According
> > to the naming convention it should be "release-3.2.1"
> > (https://github.com/apache/ratis/branches/all?query=release). This
> > will fix the "commit does not belong to any branch on this repository"
> > issue.
> >
> > The tag (ratis-3.2.1-rc1) should be pushed only before sending out the
> > RC vote email, to avoid having to re-create it in case of any CI
> > problem (which could be seen in the branch's runs).
> >
> > Original:
> >
> > tag ratis-3.2.1-rc1
> > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > Date: Sun Sep 7 13:15:16 2025 +0800
> > ...
> > commit 93632a93a6013dd9946e5297cfba61c39e1f1239 (tag: ratis-3.2.1-rc1)
> >
> > Current:
> >
> > tag ratis-3.2.1-rc1
> > Tagger: OneSizeFitQuorum <ta...@apache.org>
> > Date: Wed Sep 24 00:04:45 2025 +0800
> > ...
> > commit 9156998c9be938bc5161368bf83671f72acd47e9 (tag: ratis-3.2.1-rc1)
> >
> > -Attila
> >
>
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Xinyu Tan <ta...@apache.org>.
Hi, all
Thank you all for the reminders. It appears that I did not clean up the previous tag properly, which caused an issue with the tag uploaded for rc1. I will pay attention to this when preparing rc2.
As for whether the tag should be pushed only before sending out the email, I do need the CI status for the corresponding tag each time I send a voting email. Once an rc needs to be redone, the earlier steps with svn and mvn must be repeated, which is unavoidable. I believe it is reasonable to push the release and tag together, verify that CI passes, and then send the email; if CI fails, we should delete the corresponding branch and tag and redo the process. I have opened a new PR [1] for this.
In addition, I plan to prioritize merging 2239 and 2238, then cut rc2 from the latest commit on master. If 2329 can be updated in time, it can be included as well. I expect to release rc2 before the National Day holiday. Let us review and merge these PRs these days!
[1] https://github.com/apache/ratis/pull/1293
Best
----------------
Xinyu Tan
On 2025/09/28 07:46:51 Attila Doroszlai wrote:
> Hi Xinyu,
>
> Thanks for working on the release.
>
> Please push your local RC branch to the apache/ratis repo. According
> to the naming convention it should be "release-3.2.1"
> (https://github.com/apache/ratis/branches/all?query=release). This
> will fix the "commit does not belong to any branch on this repository"
> issue.
>
> The tag (ratis-3.2.1-rc1) should be pushed only before sending out the
> RC vote email, to avoid having to re-create it in case of any CI
> problem (which could be seen in the branch's runs).
>
> Original:
>
> tag ratis-3.2.1-rc1
> Tagger: OneSizeFitQuorum <ta...@apache.org>
> Date: Sun Sep 7 13:15:16 2025 +0800
> ...
> commit 93632a93a6013dd9946e5297cfba61c39e1f1239 (tag: ratis-3.2.1-rc1)
>
> Current:
>
> tag ratis-3.2.1-rc1
> Tagger: OneSizeFitQuorum <ta...@apache.org>
> Date: Wed Sep 24 00:04:45 2025 +0800
> ...
> commit 9156998c9be938bc5161368bf83671f72acd47e9 (tag: ratis-3.2.1-rc1)
>
> -Attila
>
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Attila Doroszlai <ad...@apache.org>.
Hi Xinyu,
Thanks for working on the release.
Please push your local RC branch to the apache/ratis repo. According
to the naming convention it should be "release-3.2.1"
(https://github.com/apache/ratis/branches/all?query=release). This
will fix the "commit does not belong to any branch on this repository"
issue.
The tag (ratis-3.2.1-rc1) should be pushed only before sending out the
RC vote email, to avoid having to re-create it in case of any CI
problem (which could be seen in the branch's runs).
Original:
tag ratis-3.2.1-rc1
Tagger: OneSizeFitQuorum <ta...@apache.org>
Date: Sun Sep 7 13:15:16 2025 +0800
...
commit 93632a93a6013dd9946e5297cfba61c39e1f1239 (tag: ratis-3.2.1-rc1)
Current:
tag ratis-3.2.1-rc1
Tagger: OneSizeFitQuorum <ta...@apache.org>
Date: Wed Sep 24 00:04:45 2025 +0800
...
commit 9156998c9be938bc5161368bf83671f72acd47e9 (tag: ratis-3.2.1-rc1)
-Attila
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Tsz-Wo Nicholas Sze <sz...@gmail.com>.
Indeed, I also like to include RATIS-2338 but it is PR ready [1] but not
yet merged.
Tsz-Wo
[1] https://github.com/apache/ratis/pull/1292
On Sat, Sep 27, 2025 at 2:24 PM Tsz-Wo Nicholas Sze <sz...@gmail.com>
wrote:
> If we are going to roll out another RC, how about including the following
> 4 recent commits?
>
> d411b02 RATIS-2331. Reuse SslContext in gRPC. (#1288)
> c5a89d8 RATIS-2337. Refactor MiniRaftCluster.PeerChanges. (#1291)
> e26213a RATIS-2336. PeerProxyMap.getProxy() could return null. (#1290)
> 2e34f6e RATIS-2322. Upgrade JUnit Jupiter to 5.13.3 and Maven Surefire
> Plugin to 3.5.3. (#1281)
>
> Tsz-Wo
>
>
> On Sat, Sep 27, 2025 at 2:20 PM Tsz-Wo Nicholas Sze <sz...@gmail.com>
> wrote:
>
>> Hi Xinyu,
>>
>> Thanks a lot for working on the release!
>>
>> > The git tag to be vote upon:
>> > https://github.com/apache/ratis/tree/ratis-3.2.1-rc1
>> >
>> > The git commit hash:
>> > 9156998c9be938bc5161368bf83671f72acd47e9
>>
>> Somehow both the tag and the commit are not found:
>>
>> % git checkout 9156998c9be938bc5161368bf83671f72acd47e9
>> fatal: reference is not a tree: 9156998c9be938bc5161368bf83671f72acd47e9
>> % git checkout ratis-3.2.1-rc1
>> error: pathspec 'ratis-3.2.1-rc1' did not match any file(s) known to git
>>
>> Even the web site says, "This commit does not belong to any branch on
>> this repository, and may belong to a fork outside of the repository."
>> [image: image.png]
>>
>> Could you take a look?
>>
>> Tsz-Wo
>>
>>
>> On Tue, Sep 23, 2025 at 9:44 AM Xinyu Tan <ta...@apache.org> wrote:
>>
>>> Hi Ratis community,
>>>
>>> I’m calling a vote For Apache Ratis Release 3.2.1 rc1.
>>>
>>> The git tag to be vote upon:
>>> https://github.com/apache/ratis/tree/ratis-3.2.1-rc1
>>>
>>> The git commit hash:
>>> 9156998c9be938bc5161368bf83671f72acd47e9
>>>
>>> The source and binary tarballs can be found at:
>>> https://dist.apache.org/repos/dist/dev/ratis/3.2.1/rc1
>>>
>>> Fingerprint of the GPG key release artifacts are signed with:
>>> 055D2E860E43CBB155D09AA4BECD7978EE4DA7BC
>>>
>>> My public key to verify signatures can be found in:
>>> https://dist.apache.org/repos/dist/release/ratis/KEYS
>>>
>>> Maven artifacts are staged at:
>>> https://repository.apache.org/content/repositories/orgapacheratis-1170
>>>
>>> This vote will remain open for at least 7 days.
>>> Please vote on releasing this ratis-3.2.1-rc1. Thanks in advance.
>>>
>>> [ ] +1 approve
>>> [ ] 0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>> Starting with my +1
>>> - Verified checksums, signatures and git hash.
>>> - Checked LICENSE and NOTICE.
>>> - Compared the files in src tarball with the files at the given git tag.
>>> - Built from source.
>>> - Ran regular Ratis CI. [1]
>>>
>>> [1] https://github.com/apache/ratis/actions/runs/17952537892
>>>
>>
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Tsz-Wo Nicholas Sze <sz...@gmail.com>.
If we are going to roll out another RC, how about including the following 4
recent commits?
d411b02 RATIS-2331. Reuse SslContext in gRPC. (#1288)
c5a89d8 RATIS-2337. Refactor MiniRaftCluster.PeerChanges. (#1291)
e26213a RATIS-2336. PeerProxyMap.getProxy() could return null. (#1290)
2e34f6e RATIS-2322. Upgrade JUnit Jupiter to 5.13.3 and Maven Surefire
Plugin to 3.5.3. (#1281)
Tsz-Wo
On Sat, Sep 27, 2025 at 2:20 PM Tsz-Wo Nicholas Sze <sz...@gmail.com>
wrote:
> Hi Xinyu,
>
> Thanks a lot for working on the release!
>
> > The git tag to be vote upon:
> > https://github.com/apache/ratis/tree/ratis-3.2.1-rc1
> >
> > The git commit hash:
> > 9156998c9be938bc5161368bf83671f72acd47e9
>
> Somehow both the tag and the commit are not found:
>
> % git checkout 9156998c9be938bc5161368bf83671f72acd47e9
> fatal: reference is not a tree: 9156998c9be938bc5161368bf83671f72acd47e9
> % git checkout ratis-3.2.1-rc1
> error: pathspec 'ratis-3.2.1-rc1' did not match any file(s) known to git
>
> Even the web site says, "This commit does not belong to any branch on this
> repository, and may belong to a fork outside of the repository."
> [image: image.png]
>
> Could you take a look?
>
> Tsz-Wo
>
>
> On Tue, Sep 23, 2025 at 9:44 AM Xinyu Tan <ta...@apache.org> wrote:
>
>> Hi Ratis community,
>>
>> I’m calling a vote For Apache Ratis Release 3.2.1 rc1.
>>
>> The git tag to be vote upon:
>> https://github.com/apache/ratis/tree/ratis-3.2.1-rc1
>>
>> The git commit hash:
>> 9156998c9be938bc5161368bf83671f72acd47e9
>>
>> The source and binary tarballs can be found at:
>> https://dist.apache.org/repos/dist/dev/ratis/3.2.1/rc1
>>
>> Fingerprint of the GPG key release artifacts are signed with:
>> 055D2E860E43CBB155D09AA4BECD7978EE4DA7BC
>>
>> My public key to verify signatures can be found in:
>> https://dist.apache.org/repos/dist/release/ratis/KEYS
>>
>> Maven artifacts are staged at:
>> https://repository.apache.org/content/repositories/orgapacheratis-1170
>>
>> This vote will remain open for at least 7 days.
>> Please vote on releasing this ratis-3.2.1-rc1. Thanks in advance.
>>
>> [ ] +1 approve
>> [ ] 0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Starting with my +1
>> - Verified checksums, signatures and git hash.
>> - Checked LICENSE and NOTICE.
>> - Compared the files in src tarball with the files at the given git tag.
>> - Built from source.
>> - Ran regular Ratis CI. [1]
>>
>> [1] https://github.com/apache/ratis/actions/runs/17952537892
>>
>
Re: [VOTE] Apache Ratis Release 3.2.1 rc1
Posted by Tsz-Wo Nicholas Sze <sz...@gmail.com>.
Hi Xinyu,
Thanks a lot for working on the release!
> The git tag to be vote upon:
> https://github.com/apache/ratis/tree/ratis-3.2.1-rc1
>
> The git commit hash:
> 9156998c9be938bc5161368bf83671f72acd47e9
Somehow both the tag and the commit are not found:
% git checkout 9156998c9be938bc5161368bf83671f72acd47e9
fatal: reference is not a tree: 9156998c9be938bc5161368bf83671f72acd47e9
% git checkout ratis-3.2.1-rc1
error: pathspec 'ratis-3.2.1-rc1' did not match any file(s) known to git
Even the web site says, "This commit does not belong to any branch on this
repository, and may belong to a fork outside of the repository."
[image: image.png]
Could you take a look?
Tsz-Wo
On Tue, Sep 23, 2025 at 9:44 AM Xinyu Tan <ta...@apache.org> wrote:
> Hi Ratis community,
>
> I’m calling a vote For Apache Ratis Release 3.2.1 rc1.
>
> The git tag to be vote upon:
> https://github.com/apache/ratis/tree/ratis-3.2.1-rc1
>
> The git commit hash:
> 9156998c9be938bc5161368bf83671f72acd47e9
>
> The source and binary tarballs can be found at:
> https://dist.apache.org/repos/dist/dev/ratis/3.2.1/rc1
>
> Fingerprint of the GPG key release artifacts are signed with:
> 055D2E860E43CBB155D09AA4BECD7978EE4DA7BC
>
> My public key to verify signatures can be found in:
> https://dist.apache.org/repos/dist/release/ratis/KEYS
>
> Maven artifacts are staged at:
> https://repository.apache.org/content/repositories/orgapacheratis-1170
>
> This vote will remain open for at least 7 days.
> Please vote on releasing this ratis-3.2.1-rc1. Thanks in advance.
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Starting with my +1
> - Verified checksums, signatures and git hash.
> - Checked LICENSE and NOTICE.
> - Compared the files in src tarball with the files at the given git tag.
> - Built from source.
> - Ran regular Ratis CI. [1]
>
> [1] https://github.com/apache/ratis/actions/runs/17952537892
>