+1

On Tue, Apr 14, 2026, at 4:54 PM, Dinesh Joshi wrote:
> +1
> 
> On Mon, Apr 13, 2026 at 12:58 PM Nate McCall <[email protected]> wrote:
>> +1
>> 
>> On Tue, Apr 14, 2026 at 6:49 AM Brad <[email protected]> wrote:
>>> +1 
>>> 
>>> On Thu, Apr 9, 2026 at 2:28 AM Bret McGuire <[email protected]> wrote:
>>>>    Greetings all!  I believe the issues encountered in the earlier attempt 
>>>> to vote on this release have been addressed so we're going to give this 
>>>> another go.
>>>> 
>>>>    I'm proposing the test build of Cassandra Python Driver 3.30.0 for 
>>>> release.
>>>> 
>>>> sha1: 6fbcacba057defd068c417b96f8a46f5c0d3285c
>>>> Git: https://github.com/apache/cassandra-python-driver/releases/tag/3.30.0
>>>> Source release:
>>>> https://dist.apache.org/repos/dist/dev/cassandra/cassandra-python-driver/3.30.0/
>>>> Changelog:
>>>> https://github.com/apache/cassandra-python-driver/blob/trunk/CHANGELOG.rst#3300
>>>> 
>>>>    The changelog has been updated to include the work done for 
>>>> CASSPYTHON-17.  The content on dist.apache.org has also been updated to 
>>>> include a source build as well as SHA256, SHA512 and PGP signatures (hat 
>>>> tip to Nate for pointing out that they were missing the first time 
>>>> around).  Unfortunately we can't deploy this release to test.pypi.org; 
>>>> releases deployed there are immutable and we've already deployed a 
>>>> "3.30.0" as part of the initial release attempt.  To offset this issue 
>>>> I've included a "wheels" directory in the source release containing the 
>>>> full set of wheels we aim to deploy to PyPI if the vote is successful.  
>>>> With these wheels you can re-create a test.pypi.org install, albeit with a 
>>>> manual install of the wheel via pip.
>>>> 
>>>>    The earlier vote attempt has also forced us to update the "3.30.0" tag 
>>>> for this repository.  We anticipate this to be a one-off event; while we 
>>>> were working on CASSPYTHON-17 a different model for managing branches, 
>>>> tags and wheel builds was suggested by Jarek Potiuk based on his 
>>>> experience with other Python projects.  This model will allow us to handle 
>>>> these types of changes without changing tags.  We plan on moving towards 
>>>> something like this for future releases; we're definitely still learning 
>>>> as we go.  Big hat tip to Jarek for his help here!
>>>> 
>>>>    We're coming up on a weekend so the vote will be open for 120 hours 
>>>> (longer if needed) until ~5:30am GMT on 14 April 2026. Everyone who has 
>>>> tested the build is invited to vote.
>>>> Votes by PMC members are considered binding. A vote passes if there are at
>>>> least three binding +1s and no -1's.
>>>> 
>>>>    Thanks all!
>>>> 
>>>>       - Bret -

Reply via email to