Hey,
IMHO 1.8 should definitely include the Auth-Manager work, which tackles
actual bugs in the Iceberg code base wrt OAuth implementation. That work
was originally intended to go into 1.7 and now it shall be delayed again
for 1.9. The PR was originally opened in July 2024, about half a year
ago and is still getting reviewed. In the meantime there were more than
600 other PRs that got reviewed and merged.
The overall agreement around spring 2024, please correct me if I am
wrong, was the whole REST/OAuth area needs to be improved, and the oauth
endpoint removed entirely.
Generally speaking, and I know I'm not alone, getting reviews from
Iceberg committers is extremely hard. A lot of issues and PRs just get
closed (by that stale bot) without having gotten _any_ attention from an
Iceberg committer. This is not a new situation but going on for a long
time. I have been talking to two Iceberg PMC members in person many
months ago that this is a very disappointing situation that needs to be
fixed. The reply was always "we are already working on it" - but at
least from my personal POV the situation did not improve.
Robert
On 16.01.25 10:56, Jean-Baptiste Onofré wrote:
Hi folks,
Following the Community Meeting yesterday, I would like to propose the
following plan regarding releases:
0. As a prerequisite to any release (1.7.2, 1.8.0, 1.9.0), as said by
Ryan, we have to double check the NOTICE/LICENSE. Interestingly, I
discussed this point with Fokko at the beginning of this week, because
I have some doubts about LICENSE/NOTICE content in the "uber" jar
artifacts where we shade dependencies. I'm doing a complete pass on
all artifacts in 1.7.2-SNAPSHOT and 1.8.0-SNAPSHOT. I should have a
complete analysis by tomorrow. This is potentially a blocker for
release votes.
1. As soon as (0) is done, 1.7.2 can be submitted to vote. I will work
with Fokko on this one.
2. We plan to do 1.8.0 in a couple of weeks (Amogh is the release
manager). Due to still some WIP, we "revisited" the 1.8.0 release
content: for instance, as best effort, we wanted to include REST Auth
Manager improvement (OAuth2 Manager) but we preferred to postpone to
1.9.0. That's totally fine to me, however, I would propose to strongly
focus on pending PRs for 1.9.0. Imho, we should "target" (again as
clear best effort) on variant, partition stats and Auth Manager.
3. Assuming 1.8.0 will be released at the end of Jan/beginning of Feb,
according to our "release cadence", what do you think about planning
1.9.0 in April ? Again with the main targets listed in (2).
I tried to sum up what we discussed yesterday :)
Thoughts ?
Regards
JB
On Thu, Jan 9, 2025 at 7:51 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
Hi folks,
We did Apache Iceberg 1.7.0 release on Nov 8, 2024. If we want to keep
our release "pace", 1.8.0 should be released around mid February.
I think we already have a good "train" of merged PRs (or should be
merged soon): default values, REST auth improvements, dependencies
updates, etc.
WDYT about 1.8.0 mid Feb ? If so, I propose we update GitHub Issues
and PRs we would like to "target" to 1.8.0.
Thoughts ?
Regards
JB
--
Robert Stupp
@snazy
