+1 (binding)

The source release:
LICENSE and NOTICE [ok]
signatures and hashes [ok]
could compile from source: mvn clean install [ok]

On 2024/02/19 08:07:43 Haonan Hou wrote:
> +1 
> 
> LICENSE and NOTICE [ok]
> signatures and hashes [ok]
> could compile from source: mvn clean install [ok]
> 
> Thanks,
> Haonan 
> 
> On 2024/02/18 11:10:54 Christofer Dutz wrote:
> > +1 (binding)
> > 
> > Chris
> > 
> > [OK] Download all staged artifacts under the url specified in the release 
> > vote email.
> > [OK] Verify the signature is correct.
> > 
> >   *   No trust-chain … possibly worth attending an Apache Key-Signing event.
> > [OK] Check if the signature references an Apache email address.
> > [OK] Verify the SHA512 hashes.
> > [OK] Unzip the archive.
> > [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files 
> > in the extracted source bundle.
> > [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in 
> > the extracted source bundle.
> > [OK] [RM] Verify the staged source README, RELEASE_NOTE files correspond to 
> > those in the extracted source bundle.
> > [OK] [RM] Run RAT externally to ensure there are no surprises.
> > [OK] Search for SNAPSHOT references
> > [OK] Search for Copyright references, and if they are in headers, make sure 
> > these files containing them are mentioned in the LICENSE file.
> > [OK] Build the project according to the information in the README.md file.
> > 
> > Von: Haonan Hou <[email protected]>
> > Datum: Samstag, 17. Februar 2024 um 02:32
> > An: [email protected] <[email protected]>
> > Betreff: [VOTE] Apache TsFile 1.0.0 RC1 release
> > Hi all,
> > 
> > Apache TsFile 1.0.0 has been staged under [2] and it’s time to vote
> > on accepting it for release. All Maven artifacts are available under [1].
> > Voting will be open for 72hr.
> > A minimum of 3 binding +1 votes and more binding +1 than binding -1
> > are required to pass.
> > 
> > Release tag: v1.0.0
> > Hash for the release tag: c5c348430004109cdba3d4b255031e833d37a932
> > 
> > Before voting +1, PMC members are required to download
> > the signed source code package, compile it as provided, and test
> > the resulting executable on their own platform, along with also
> > verifying that the package meets the requirements of the ASF policy
> > on releases. [3]
> > 
> > You can achieve the above by following [4].
> > 
> > [ ] +1 accept (indicate what you validated - e.g. performed the
> > non-RM items in [4])
> > [ ] -1 reject (explanation required)
> > 
> > 
> > [1] https://repository.apache.org/content/repositories/orgapachetsfile-1000
> > [2] https://dist.apache.org/repos/dist/dev/tsfile/1.0.0/rc1
> > [3] https://www.apache.org/dev/release.html#approving-a-release
> > [4] 
> > https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
> > [5] https://dist.apache.org/repos/dist/dev/tsfile/1.0.0/rc1/RELEASE_NOTES.md
> > [6] https://dist.apache.org/repos/dist/dev/tsfile/KEYS
> > 
> > Best,
> > 
> > Haonan Hou
> > 
> 

Reply via email to