+1 (non-binding)

Verified:

   - Signatures & Checksums
   - License & Notice
   - Build from source

- Ajantha

On Thu, Nov 12, 2026 at 10:22 AM Xiaodong Deng via dev <
[email protected]> wrote:

> +1 (non-binding)
>
> - Ran tools/verify-release/verify-release.sh from the rc1 tag:
> LICENSE/NOTICE and version.txt are in place, and the signatures and SHA-512
> checksums of the source tarball all verify.
> - Python client: the wheel's signature and checksum look good.
> - Used the 1.9.0 client for an application I have been building with
> 1.8.0, and confirmed 1.9.0 could work well there too.
>
> One observation (not a blocker):
> As the CHANGELOG notes, renaming a table into another namespace now
> returns 403 unless its files lie within the destination namespace's
> location (ALLOW_UNSTRUCTURED_TABLE_LOCATION=false by default).
> Downstream code that moves tables across namespaces may need adjusting.
> This became a little surprise for my application during the testing.
> I think it may be worth highlighting in the communications when the
> release is finalized & announced.
>
> Last but not least: thanks for preparing the release!
>
>
> XD
>
>
> On 2026/11/11 18:39:34 Prithvi S wrote:
> > +1 (non-binding)
> >
> > Verified:
> > * Signatures
> > * Checksums
> > * LICENSE / NOTICE
> > * Build from source
> > * No unexpected binaries in the source archive
> > * polaris-bin starts with in-memory persistence; catalog, namespace and
> > table operations work as expected
> > * Python CLI wheel installs and runs successfully
> >
> > Thanks, JB, for driving the release.
> >
> > Thanks,
> > Prithvi
> >
> > On Wed, Nov 11, 2026 at 11:12 PM vignesh a <[email protected]>
> wrote:
> >
> > > +1 (non-binding)
> > >
> > > * Built from source
> > > * Signatures and checksums for the source tarball, polaris-bin, and
> Helm
> > >   chart
> > > * LICENSE and NOTICE in the source tarball and polaris-bin
> > > * No unexpected binaries in the source tarball
> > >
> > > Thanks JB for driving the release.
> > >
> > > Thanks,
> > > Vignesh
> > >
> >
>

Reply via email to