+1 (non-binding) - Validated signatures / checksums - Checked license
- Ran some code examples in Python 3.12 André Anastácio On Monday, July 29th, 2024 at 2:42 PM, Kevin Liu <kevin.jq....@gmail.com> wrote: > +1 (non-binding) > Verified signatures/checksums/license. Ran unit and integration tests. Logs > are attached to this email. > > Sidenote, the [Pyiceberg > website](https://py.iceberg.apache.org/verify-release/) docs have not been > updated, so I follow the [GitHub > docs](https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/verify-release.md#verifying-a-release) > instead. > > On Mon, Jul 29, 2024 at 8:19 AM Chinmay Bhat <csbha...@gmail.com> wrote: > >> Tested 0.7.0rc2. >> >> +1 (non-binding) >> - validated signatures & checksums >> - checked license - RAT checks passed >> - ran tests and test-coverage with Python 3.9 >> >> Thank you everyone for the hard work! >> >> Best, >> Chinmay >> >> On Sat, Jul 27, 2024 at 3:39 PM Sung Yun <sungwy...@gmail.com> wrote: >> >>> Thank you Fokko for your help in setting the next steps for the course of >>> resolution. >>> >>> To clarify as a follow up to Fokko' suggestion: the PyPi release under test >>> for 0.7.0rc2 can now be found here: >>> https://pypi.org/project/pyiceberg/0.7.0rc2/ >>> >>> We will leave this VOTE thread open for votes to decide on the next steps >>> for this release. >>> >>> Thank you very much, and sorry for the inconvenience caused due to this >>> issue! >>> Sung >>> >>> On Sat, Jul 27, 2024 at 5:00 AM Fokko Driesprong <fo...@apache.org> wrote: >>> >>>> Hey everyone, >>>> >>>> I just yanked the release from PyPi. I still encourage everyone to test >>>> out PyIceberg 0.7.0rc1 to check if everything works on their end and give >>>> all the awesome new features a go. >>>> >>>> Since the release has been yanked, and releases are immutable in PyPi, >>>> there are two ways forward: >>>> >>>> - If the vote passes for this RC, we can unyank the release >>>> - If there are things found that need fixing, we can bump the version to >>>> 0.7.1 >>>> >>>> Wish you all a great weekend, >>>> >>>> Kind regards, >>>> Fokko >>>> >>>> Kind regards, >>>> Fokko >>>> >>>> Op za 27 jul 2024 om 03:45 schreef Sung Yun <sungwy...@gmail.com>: >>>> >>>>> Hi ndrluis, >>>>> >>>>> Thank you VERY much for flagging this. I really appreciate you bringing >>>>> this to our attention so quickly. >>>>> >>>>> This is the first time I'm running the release front to end, and I missed >>>>> one small detail that led to this mishap. >>>>> >>>>> I will cancel this vote, and remove the artifact from PyPi before >>>>> starting a new vote. >>>>> >>>>> Sung >>>>> >>>>> On Fri, Jul 26, 2024 at 9:02 PM <ndrl...@proton.me.invalid> wrote: >>>>> >>>>>> Hey Sung Yun, >>>>>> >>>>>> Thank you for starting the release. >>>>>> >>>>>> I was checking PyPI, and it looks like the release candidate was >>>>>> published as version 0.7.0 (https://pypi.org/project/pyiceberg/0.7.0/). >>>>>> >>>>>> On Friday, July 26th, 2024 at 7:35 PM, Sung Yun <sungwy...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Everyone, >>>>>>> >>>>>>> I propose that we release the following RC as the official PyIceberg >>>>>>> 0.7.0 release. >>>>>>> >>>>>>> This is a large release featuring many amazing contributions from the >>>>>>> community, and here’s a summary of the features introduced on a high >>>>>>> level: >>>>>>> >>>>>>> * Write support to partitioned tables with IdentityTransform and >>>>>>> TimeTransform partitions >>>>>>> >>>>>>> * Support for deletes using predicates. It will drop whole files when >>>>>>> it is able to based on the Iceberg statistics, otherwise it will >>>>>>> perform a copy-on-write. >>>>>>> * Parallelizing writes for a given partition based on a target file size >>>>>>> * A new API for rendering PyArrow tables that show metadata about the >>>>>>> tables’ manifests, partitions, etc >>>>>>> * Support for evolving table partitions >>>>>>> * Updated schema compatibility check to be more permissive, by >>>>>>> supporting promotable types and subset of schemas on write >>>>>>> * Option to merge manifests on write when number of manifests exceeds a >>>>>>> threshold >>>>>>> * Support staging a table for creation and building a transaction >>>>>>> * A new table scan API to return an Arrow RecordBatchReader as opposed >>>>>>> to a fully materialized Arrow table >>>>>>> * Support for categorical and large PyArrow types on write >>>>>>> * A new API to add existing parquet files to a table without rewriting >>>>>>> them >>>>>>> * Support for loading custom catalog >>>>>>> >>>>>>> Note: We are skipping the vote on RC1 because we had already started >>>>>>> the release process last Friday, but didn't want to send out the VOTE >>>>>>> just before the weekend. During that time, bugs were reported, fixes of >>>>>>> which are included in RC2. >>>>>>> >>>>>>> The commit ID is be5c42649914e71e8366c22558f8234ce062b145 >>>>>>> >>>>>>> * This corresponds to the tag: pyiceberg-0.7.0rc2 >>>>>>> (a9c69003bafd1ae03ca27537cdc3e13ff1d9e502) >>>>>>> >>>>>>> * >>>>>>> https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.7.0rc2 >>>>>>> >>>>>>> * >>>>>>> https://github.com/apache/iceberg-python/tree/be5c42649914e71e8366c22558f8234ce062b145 >>>>>>> >>>>>>> The release tarball, signature, and checksums are here: >>>>>>> >>>>>>> * https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.7.0rc2/ >>>>>>> >>>>>>> You can find the KEYS file here: >>>>>>> >>>>>>> * https://dist.apache.org/repos/dist/dev/iceberg/KEYS >>>>>>> >>>>>>> Convenience binary artifacts are staged on pypi: >>>>>>> >>>>>>> https://pypi.org/project/pyiceberg/0.7.0rc2/ >>>>>>> >>>>>>> And can be installed using: pip3 install pyiceberg==0.7.0rc2 >>>>>>> >>>>>>> Please download, verify, and test. >>>>>>> >>>>>>> Please vote in the next 72 hours. >>>>>>> >>>>>>> [ ] +1 Release this as PyIceberg 0.7.0 >>>>>>> >>>>>>> [ ] +0 >>>>>>> >>>>>>> [ ] -1 Do not release this because...
