Strictly speaking the vote has not concluded on the PPMC vote. 72hrs
has not elapsed and the result has not been declared.
I don't object to starting the IPMC vote, I just want to correct the record.

On Thu, 3 Sept 2026 at 10:11, tison <[email protected]> wrote:
>
> Hi Incubator PMC,
>
> The Apache Asyncband PPMC has voted to release Apache Asyncband
> (Incubating) 0.7.0 RC1.
>
> The PPMC vote has received 6 +1 votes and no +0 or -1 votes. Four of the +1
> votes were from IPMC members.
>
> PPMC vote thread:
> https://lists.apache.org/thread/stmtcjsgpzt2vl8mlklf5zovbp9o4nr7
>
> PPMC vote result:
> (no objection now; I should conclude it in hours, but let's see whether
> running votes in parallel works)
>
> I am now calling for an IPMC vote on this release.
>
> The release candidate is based on commit:
> 02b30dd7d74f17b1ae6d83e05b4ac0877932dd3d
>
> Source artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/asyncband/0.7.0-rc.1/
>
> Signed Git tag:
> https://github.com/apache/asyncband/tree/v0.7.0-rc.1
>
> Changelog:
> https://github.com/apache/asyncband/blob/v0.7.0-rc.1/CHANGELOG.md
>
> KEYS:
> https://downloads.apache.org/incubator/asyncband/KEYS
>
> Signing key fingerprint:
> 8B37 4472 FAD3 28E1 7F47 9863 B379 691F C6E2 98DD
>
> SHA-512:
> e525b68397a624b49fc1c642ec4d8354ab6ee63616682b00140b8cbdadf2d5e038e824794db464a01a2a8263663b4f8d78f7167d93164241cb0624cce1a1c3fc
>  apache-asyncband-0.7.0-incubating-src.tar.gz
>
> The candidate has been verified for its checksum, signature, legal files,
> unexpected binary files, workspace tests, doctests, and Cargo package
> dry-run.
>
> Please vote:
>
> [ ] +1 Approve the release
> [ ] +0 No opinion
> [ ] -1 Do not approve the release, with a reason
>
> Only votes from IPMC members are binding, but everyone is welcome to vote.
>
> The vote will remain open until 2026-09-06 09:00 UTC, for at least 72 hours.
>
> Best,
> tison.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to