Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your patience here, I was touching grass.
A proposal starts with a Google doc, for example, the Geo support: https://docs.google.com/document/d/1iVFbrRNEzZl8tDcZC81GFt01QJkLJsI9E2NBOt21IRI
Once there is consensus, the process of splitting it out into separate issues starts. I'm doubtful if having this additional checkbox and TODO label clarifies the process.
In addition to that, we started in Python (apache/iceberg-python#736) and Rust (apache/iceberg-rust#348) to have tracking issues as suggested a while ago on the dev-list, which also seem in conflict with having a tracking issue per proposal.
If the tracking issue works for the partitioned stats, I'm fully okay with that, just not sure if we should add this to the template (since it is easy to add a lot of additional checkboxes here, which might raise the bar of proposing something at all).