Hi Xuanwo, Thank you for sharing your thoughts! I think that makes a strong argument for coupling the releases together, and and I agree that it would be beneficial for the community to prioritize ease of troubleshooting, and maintainability.
Following the release guidelines (https://rust.iceberg.apache.org/release.html) for Iceberg-Rust, I've started a tracking issue to help work towards the 0.4.0 release: https://github.com/apache/iceberg-rust/issues/739 > I am willing to implement the release scripts needed for Sung Yun to execute > the release. And yes, I'd gladly take up on your help in codifying any process that's not easy to execute as per the release documentation! Shall we sync up through the open tracking issue / slack on those steps? Sung On 2024/11/28 16:10:08 Xuanwo wrote: > Hi, Sung Yun & Kevin Liu > > I personally believe it would be beneficial for iceberg-rust and > pyiceberg_core to be released at the same time. This approach ensures that > pyiceberg_core always references a tagged version of iceberg-rust, which is > advantageous for debugging purposes. > > I am willing to implement the release scripts needed for Sung Yun to execute > the release. Please let me know your thoughts. > > > On Thu, Nov 28, 2024, at 02:53, Fokko Driesprong wrote: > > Hey Sung, > > > > All for it, and happy to help as well. I'll add it to the agenda for > > tomorrow's Rust sync > > <https://lists.apache.org/thread/0t1w33jg9gmcwfnx9fplq48h1d4kjfn9>. We'll > > make sure to publish the notes since it is on a US holiday. > > > > Kind regards, > > Fokko > > > > Op wo 27 nov 2024 om 19:30 schreef Kevin Liu <kevinjq...@apache.org>: > >> Thanks for driving this, Sung! I'm +1 to release both iceberg-rust and > >> pyiceberg_core. It's very exciting to see pyiceberg_core and its > >> integration with PyIceberg. > >> It makes sense to decouple pyiceberg_core from iceberg-rust since the two > >> "projects" are on different tracks. We'd want to release pyiceberg_core > >> features independent of iceberg-rust features. > >> > >> Please let me know if there's anything I can do to help. > >> > >> Best, > >> Kevin Liu > >> > >> On Wed, Nov 27, 2024 at 6:13 AM Sung Yun <sun...@apache.org> wrote: > >>> Hi folks, it's been some time since we've done an Iceberg Rust release, > >>> and we've finally set up the ghactions workflow[1] that will allow us to > >>> build and publish an abi3 compatible wheel to Pypi. > >>> > >>> If we are still +1 for the release (both iceberg-rust and > >>> pyiceberg_core), I think it'll be awesome to get this release out soon as > >>> it will help the PyIceberg community test out the pyiceberg_core binding > >>> in preparation for the next release. > >>> > >>> Another option would be to introduce a workflow_dispatch trigger to the > >>> python_release.yml and run a decoupled, release for pyiceberg_core[2] > >>> > >>> I'd be happy to help run the release, if no one has started looking into > >>> it already. > >>> > >>> Sung > >>> > >>> [1] https://github.com/apache/iceberg-rust/pull/705 > >>> [2] https://lists.apache.org/thread/j22o7yktrlddrgkcy7gl88o23nyrgooc > >>> > >>> On 2024/09/05 14:06:10 xianjin wrote: > >>> > +1 for this pyiceberg_core as well. > >>> > > >>> > > >>> > > >>> > Two cents about the iceberg-rust release schedule: it seems too > >>> > aggressive to > >>> > release by 2 weeks, monthly(4 weeks) release would be a nice fit. > >>> > > >>> > Sent from my iPhone > >>> > > >>> > > >>> > > >>> > > On Sep 5, 2024, at 8:25 PM, Sung Yun <sungwy...@gmail.com> wrote: > >>> > > > >>> > > > >>> > > >>> > > > >>> > > > >>> > > Thank you for driving this Xuanwo! > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > +1 as well, as noted the 0.1.0 pyiceberg_core release will allow > >>> > > PyIceberg > >>> > > to begin integrating with the rust based core and introduce a new > >>> > > feature > >>> > > that the community is looking for. > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > On Thu, Sep 5, 2024 at 6:05 AM Renjie Liu > >>> > > <[liurenjie2...@gmail.com](mailto:liurenjie2...@gmail.com)> wrote: > >>> > > > >>> > > > >>> > > >>> > >> +1 for this release. > >>> > > > >>> > >> > >>> > > >>> > >> > >>> > > > >>> > >> > >>> > > >>> > >> As iceberg-rust is under fast development, a shorter release (3-4 > >>> > >> weeks) > >>> > schedule would benefit users so that they don't need to rely on a > >>> > snapshot > >>> > version. > >>> > > >>> > >> > >>> > > >>> > >> > >>> > > > >>> > >> > >>> > > >>> > >> On Thu, Sep 5, 2024 at 3:26 PM Xuanwo > >>> > <[xua...@apache.org](mailto:xua...@apache.org)> wrote: > >>> > > > >>> > >> > >>> > > >>> > >>> Hello, everyone > >>> > > > >>> > > I'm starting this thread to discuss the release of iceberg rust > >>> > > 0.4.0 and > >>> > > iceberg pyiceberg_core 0.1.0. > >>> > > > >>> > > There is no specific reason for this release. I just want to align > >>> > > with the > >>> > > two- to three-week release schedule of iceberg rust so users don't > >>> > > have to > >>> > > wait long or encounter too many breaking changes at once. > >>> > > > >>> > > Additionally, the pyiceberg team is awaiting our first release of > >>> > > pyiceberg_core 0.1.0 so they can integrate with it, see how it works, > >>> > > and > >>> > > explore ways to improve collaboration. > >>> > > > >>> > > What do you think? > >>> > > > >>> > > Xuanwo > >>> > > > >>> > > <https://xuanwo.io/> > >>> > > > >>> > > >>> > > Xuanwo > > https://xuanwo.io/ >
