+1 binding

[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] No unexpected binary files
[x] All source files have ASF headers
[x] Can compile from source

Some minor issues:
1. Please check the 'Hash for the release tag' again. It seems that there is 
inconsistency.
2. The end year in the NOTICE document should be updated to 2026.


On 2026/02/12 07:38:44 lxfeng wrote:
> Hi Seata Community,
> 
> This is a call for vote to release Apache Seata-go(incubating) v2.1.0.
> 
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/seata/incubator-seata-go/v2.1.0/
> 
> Git tag for the release:
> https://github.com/apache/incubator-seata-go/releases/tag/v2.1.0
> 
> Hash for the release tag:
> 9e0227c76e825a63e67d0fa4e5f1d098e6a77a61
> 
> Release Notes:
> https://github.com/apache/incubator-seata-go/releases/tag/v2.1.0
> 
> The artifacts have been signed with Key [ B29581E977CD3E1E ], mail 
> [[email protected]]
> 
> which can be found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/seata/KEYS
> 
> Build Environment: Golang 1.20+.
> Build Command: make build
> 
> CI Test Workflow:
> https://github.com/apache/incubator-seata-go/actions/runs/21799106087/job/62891504502
> 
> The vote will be open for at least 72 hours.
> 
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
> 
> 
> To learn more about Apache Seata , please see https://seata.apache.org/
> 
> Warm regards,
> 
> lxfeng
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to