[GitHub] [iceberg-go] nastra merged pull request #1: feat: schema and types

nastra merged PR #1: URL: https://github.com/apache/iceberg-go/pull/1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@iceberg.apache.org

[GitHub] [iceberg-go] nastra commented on a diff in pull request #1: feat: schema and types

nastra commented on code in PR #1: URL: https://github.com/apache/iceberg-go/pull/1#discussion_r1295404949 ## .gitignore: ## @@ -0,0 +1,39 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distribu

Re: Thoughts on EOL Strategy for Our Releases?

Thanks JB and Ryan. Makes sense to not have a EOL policy since a vote-based new release is always possible for Apache projects. Other than that, a single Iceberg release includes the new changes for multiple Spark/Flink versions. For example, the 1.3.0 release covers Spark 3.1, Spark 3.2, Spark 3.3

[GitHub] [iceberg-go] zeroshade opened a new pull request, #1: feat: schema and types

zeroshade opened a new pull request, #1: URL: https://github.com/apache/iceberg-go/pull/1 Initial dev setup scripts / github actions configs etc. Plus initial schema and types implementation -- This is an automated message from the Apache Git Service. To respond to the message, plea

PyIceberg 0.5.0 release

Hi everyone, As mentioned in the latest Iceberg sync, I'd love to do another Python release. I would like to reach out to the community to see if there is anything we should include. I know that it was promised that the next release would have to write support, but so many features have already a