Thanks Jia, for catching that. 

I've added the NOTICE file to both branch-0.2.0 and main:
https://github.com/apache/sedona-spatialbench/commit/1277402

I'll start a new vote thread for RC2.

Best,
Pranav

> On Feb 17, 2026, at 10:10 PM, Jia Yu <[email protected]> wrote:
> 
> -1 (binding)
> 
> Sorry I guess we have to make another release candidate
> 
> I ran the test script
> 
> dev/release/verify-release-candidate.sh 0.2.0 1
> 
> [X] Download links are valid
> [X] Checksums and PGP signatures are valid
> [X] Source code artifacts have correct names matching the current release
> [-] LICENSE and NOTICE files are present and correct
> [X] All files have ASF license headers (verified via Apache RAT)
> [X] Source builds and tests pass
> 
> The NOTICE file didn't exist in the SpatialBench repository. We should
> add it. See SedonaDB:
> https://github.com/apache/sedona-db/blob/main/NOTICE
> 
> In fact, we should have found this issue in the SpatialBench 0.1.0
> release but I guess we all forgot at that point:
> https://www.apache.org/legal/src-headers.html#notice
> 
> Thanks,
> Jia
> 
> 
> 
> On Tue, Feb 17, 2026 at 6:22 PM Pranav Toggi <[email protected]> wrote:
>> 
>> Hi all,
>> 
>> I'd like to call a vote on releasing Apache Sedona SpatialBench 0.2.0-rc1.
>> 
>> Source release artifacts:
>> https://dist.apache.org/repos/dist/dev/sedona/sedona-spatialbench-0.2.0-rc1/
>> 
>> GitHub tag:
>> https://github.com/apache/sedona-spatialbench/releases/tag/sedona-spatialbench-0.2.0-rc1
>> 
>> GPG KEYS file:
>> https://downloads.apache.org/sedona/KEYS
>> 
>> Build and contributor guide:
>> https://sedona.apache.org/spatialbench/contributors-guide/
>> 
>> Release verification instructions:
>> https://github.com/apache/sedona-spatialbench/blob/sedona-spatialbench-0.2.0-rc1/dev/release/README.md#verifying-a-release-candidate
>> 
>> The vote is open for at least 72 hours or until at least 3 "+1" PMC votes
>> are cast.
>> Please include your checklist when voting.
>> 
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (with reason)
>> 
>> Checklist for verification:
>> [ ] Download links are valid
>> [ ] Checksums and PGP signatures are valid
>> [ ] Source code artifacts have correct names matching the current release
>> [ ] LICENSE and NOTICE files are present and correct
>> [ ] All files have ASF license headers (verified via Apache RAT)
>> [ ] Source builds and tests pass
>> 
>> For a detailed checklist, see:
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>> 
>> Thanks,
>> Pranav

Reply via email to