Open code-magician323 opened 1 year ago
@code-magician323 Thanks for your feedback. @InvisibleProgrammer Could you please take care on it for the next?
@code-magician323 Something like this? https://github.com/apache/iceberg/issues/6249
Yes, I can.
@Fokko , what do you think about grouping the changelog? And maybe, it would be worth creating some kind of template to the changelogs to create a consistent experience in the future.
Hey @InvisibleProgrammer I like the idea. The changelog for 1.1.0 is rather big, grouping it by engine, core, etc would help a lot. I already removed all the Python PRs to reduce the noise, since PyIceberg has its own release cycle.
+1
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.
https://github.com/apache/iceberg/releases/tag/apache-iceberg-1.3.0 This changelog is not readable
@code-magician323 Agreed, I'm the new Head of Developer Relations at Tabular and This is definitely on my roadmap to fix. I'll have more details in the coming weeks. We're hiring someone who will help with the release process.
Feature Request / Improvement
The Iceberg changelog isn't quite useful, only because we can't see in a unified place all of the changes for each specific subject. Separation of changelog bullets to their component - e.g. some grouping by Spark, Core, Flink, etc., would be super helpful and much more comfortable to read.
Query engine
None