Skip to content

Conversation

@Fokko
Copy link
Contributor

@Fokko Fokko commented Mar 8, 2025

While @kevinjqliu did an amazing job summarizing the new stuff in 0.9.0 in the GitHub release (https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.9.0), I think it would be good to formalize this a bit.

This also came up in #1669 where we introduced a behavioral change. cc @sungwy

I think it would be good to allow users to populate the changelog section to ensure they know about any relevant changes.

The template is pretty minimal now to avoid being a big barrier to opening a PR.

@Fokko Fokko force-pushed the fd-add-changelog branch from e32f6cc to b7fe332 Compare March 8, 2025 20:22
@Fokko Fokko force-pushed the fd-add-changelog branch from c638bc2 to b461488 Compare March 8, 2025 20:56
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need the Apache license headers in the file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we don't include the .github/* directory in the source release tar, we can ignore this. I don't like that people have to scroll across the license.

image

@kevinjqliu
Copy link
Contributor

Thanks! This should make summarizing the release note easier

@@ -1,3 +1,4 @@
.github/*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's very strange, how .github/* worked and .github/pull_request_template.md didn't 🤔

@kevinjqliu kevinjqliu merged commit 1c0e2b0 into apache:main Mar 15, 2025
8 checks passed
gabeiglio pushed a commit to Netflix/iceberg-python that referenced this pull request Aug 13, 2025
While @kevinjqliu did an amazing job summarizing the new stuff in 0.9.0
in the GitHub release
(https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.9.0),
I think it would be good to formalize this a bit.

This also came up in apache#1669
where we introduced a behavioral change. cc @sungwy

I think it would be good to allow users to populate the changelog
section to ensure they know about any relevant changes.

The template is pretty minimal now to avoid being a big barrier to
opening a PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants