If it hasn't been published, please consider my vote for the tally as well.

+1 (Binding)

* Built from source
* Verified Checksums
* Verified Signatures
* Verified LICENSE & NOTICE file
* Verified the output of `ozone version`
* Verified source files having ASF header
* Skimmed over the contents of staging repo

Thanx Wei-Chiu for driving the release!!!

-Ayush

On Wed, 16 Sept 2026 at 16:38, Sammi Chen <[email protected]> wrote:
>
> +1
>
>  -  Verified commit hash matches
>  -  Verified signing key hash matches
>  -  Download release artifacts
>  -  Verified GPG signatures
>   - Verified SHA512 checksums (.sha512 and .mds files)
>   - Binary package: verified docs are present in the tarball
>   - Binary package: run bin/ozone version and validated release metadata
>   - Source package: extract tarball, verified no pom.xml.versionsBackup
> files, and build
>   - Binary package: run compose/upgrade/test.sh compatibility tests and
> passed
>
> Thanks Wei-Chiu!
>
> Sammi
>
>
> On Tue, 15 Sept 2026 at 02:00, Wei-Chiu Chuang <[email protected]> wrote:
>
> > Thanks all for the vote. This vote concludes with three +1s (including my
> > binding +1).. I'll proceed to release the bits.
> >
> > On Mon, Sep 14, 2026 at 3:02 AM Attila Doroszlai <[email protected]>
> > wrote:
> >
> > > > https://github.com/apache/ozone/releases/tag/ozone-2.1.2-RC1
> > > > https://dist.apache.org/repos/dist/dev/ozone/2.1.2-rc1/
> > >
> > > +1
> > >
> > > - Verified checksums, signatures
> > > - Compared source tarball to git repo at 2.1.2-rc1 tag
> > > - Checked license, notice
> > > - Verified ozone version
> > > - Verified docs are present in binary tarball
> > > - Confirmed CI result
> > >
> > > -Attila
> > >
> > > ---------------------------------------------------------------------
> > > 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