Re: [VOTE] Release Apache Hamilton - apache-hamilton-contrib 0.0.9-incubating (RC1)

Alin Jerpelea <[email protected]> Mon, 13 Jul 2026 09:09:05 +0200
Newsgroups gmane.comp.apache.incubator.general
Message-ID <CA+9ODHErnMEwqDSszUU91JqUK-HPjQBCPc0FKrsgh8J+h0Ge8g@mail.gmail.com>
--000000000000b315ea065678c4de
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

+1 (binding)

checked that exist
-LICENSE
-DISCLAIMER
-NOTICE

Best regards
Alin J

On Fri, Jul 10, 2026 at 3:27=E2=80=AFPM Jarek Potiuk <[email protected]> wro=
te:

> To be explicit about my vote =E2=80=94 my earlier reply only responded to=
 the
> naming concern:
>
> +1 (binding) to release apache-hamilton-contrib 0.0.9-incubating RC1.
>
> I verified it in full (scripts/verify-sub-packages/verify_contrib.sh
> 0.0.9): GPG signature good (key
> FE668E857E89A11C5E5C000CA8D3D15600545C61), SHA512 match, Apache RAT
> clean, builds from source (flit), hamilton.contrib namespace imports
> OK, LICENSE / NOTICE / DISCLAIMER present, "incubating" in the
> artifact names.
>
> On PJ's point (#1652): I agree the per-user /user/<name>/ contrib
> layout isn't ideal for an ASF project and should move to feature-based
> naming. But, like PJ, I don't treat it as a blocker for this release =E2=
=80=94
> it's a rename that can land in a follow-up, and the vote is on the
> artifacts' provenance and licensing, which check out. So my +1 stands,
> with a request that the naming be addressed in a subsequent release.
>
> Thanks,
> Jarek
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

--000000000000b315ea065678c4de--