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... > > >
