Hey folks, While working on the 0.9.0 release candidate, we went through the process of finding deprecation which should be removed in the upcoming release <https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/how-to-release.md#preparing-for-a-release> .
For the 0.9.0 release, there are 3 deprecations marked for removal. * Table name reference in scan expression <https://github.com/apache/iceberg-python/blob/efc8b5ac0f16717f776e034ecf9a9e9bdabd8424/pyiceberg/expressions/parser.py#L95> * REST catalog client AUTH_URL <https://github.com/apache/iceberg-python/blob/efc8b5ac0f16717f776e034ecf9a9e9bdabd8424/pyiceberg/catalog/rest.py#L324> * Deprecate botocore session <https://github.com/apache/iceberg-python/blob/efc8b5ac0f16717f776e034ecf9a9e9bdabd8424/pyiceberg/catalog/__init__.py#L790> For the first issue, I think we should remove the deprecation message and throw an error when the table reference is used. For the second and third issue, I think we should push back the removal to the next release since we don't have a good solution yet. Would love to hear what others think about this approach. Please let us know if there are any concerns. Best, Kevin Liu On Tue, Feb 18, 2025 at 7:11 AM Fokko Driesprong <fo...@apache.org> wrote: > Hey Kevin, > > Thanks for raising this. That sounds like a great idea to me, and thanks > Drew for being the release manager for 0.9.0. > > Kind regards, > Fokko > > Op ma 17 feb 2025 om 23:41 schreef Kevin Liu <kevinjq...@apache.org>: > >> Thanks for volunteering! I'm happy to assist in any way I can. Let's >> coordinate on Slack :) >> >> Quick follow up on the commit hash pinned above, it's meant as a >> reference point and not the absolute cutoff. In fact, we merged a few PRs >> today that will be included in 0.9.0. Please chime in here if there are >> other PRs that you think should be part of this upcoming release. >> >> Best, >> Kevin Liu >> >> On Mon, Feb 17, 2025 at 9:35 AM Drew <img...@gmail.com> wrote: >> >>> Hey Kevin, >>> >>> Thanks for kicking this off. It’s exciting to see how much PyIceberg has >>> been evolving! I’d be happy to take on the Release Manager role for this >>> release! I think it would be a good opportunity to try out the new release >>> process documentation. >>> >>> Thanks, >>> >>> Drew >>> On Mon, Feb 17, 2025 at 8:55 AM Kevin Liu <kevinjq...@apache.org> wrote: >>> >>>> Hi everyone, >>>> >>>> It's been a while since we released a new version of PyIceberg! The >>>> last minor release (0.8.0) was on November 18, and the most recent patch >>>> release (0.8.1) was on December 6. Time flies! There have been >200 >>>> commits since 0.8.0 >>>> <https://github.com/apache/iceberg-python/compare/pyiceberg-0.8.0...main> >>>> and >>>> A LOT of great features contributed by the community >>>> >>>> I propose we cut a new release for version 0.9.0 based on the current >>>> HEAD of the main branch, commit 300b840 >>>> <https://github.com/apache/iceberg-python/commit/300b8405a0fe7d0111321e5644d704026af9266b> >>>> . >>>> >>>> I'm happy to serve as the Release Manager again. But since I recently >>>> rewrote the " >>>> <https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/how-to-release.md>How >>>> to Release" documentation >>>> <https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/how-to-release.md>, >>>> it would be great if someone else could follow the updated instructions to >>>> ensure they are clear. >>>> >>>> I've started a thread on Slack >>>> <https://apache-iceberg.slack.com/archives/C029EE6HQ5D/p1738367232843719> >>>> to >>>> gather feedback from the community. Please feel free to join the discussion >>>> there or share your thoughts in this thread about the upcoming release. >>>> >>>> Best, >>>> Kevin Liu >>>> >>>>
