@Dmitri: how close to completion is #6031? We're planning to release more frequently than we have done in the past and 1.1.0 will contain the latest changes from master btw. I don't think we want to hold off too long with the release as there are quite a big amount of new things that we'd like to ship. That's why I'm curious whether #6031 is "almost" done? If it doesn't make it into 1.1.0, then there will be a 1.2.0 release soonish as well.
On Fri, Oct 21, 2022 at 4:55 PM Dmitri Bourlatchkov < dmitri.bourlatch...@dremio.com> wrote: > I'd like to add https://github.com/apache/iceberg/issues/6031 to the 1.1 > milestone (I believe permissions are indeed required for that). > > Most of the work will happen on the Nessie side. When the new API is > ready, the expectation is that Iceberg will simply need to compile with a > new version of Nessie client jars (well, perhaps minor code changes may be > required). > > Thanks, > Dmitri. > > On Fri, Oct 21, 2022 at 6:00 AM Gabor Kaszab <gaborkas...@apache.org> > wrote: > >> Hey Iceberg community, >> >> During the last community sync it came up that we might want to release >> 1.1.0 soon and I volunteered to be the release manager. >> >> As a first step I'd like to collect the issues/PRs that are meant to be >> part of 1.1.0 but not merged yet. I found a milestone already created to >> keep track of these: >> https://github.com/apache/iceberg/milestone/24 >> >> Feel free to send the link for your ongoing PRs you'd like to put into >> 1.1.0 replying to this mail thread or add it to the milestone linked above. >> (I'm not sure if it requires some extra, e.g. administrator rights on >> Iceberg github to do so) >> >> Cheers, >> Gabor >> >>
