liurenjie1024 commented on code in PR #11772: URL: https://github.com/apache/iceberg/pull/11772#discussion_r1884756239
########## site/docs/status.md: ########## @@ -0,0 +1,362 @@ +--- +title: "Implementation Status" +--- +<!-- + - Licensed to the Apache Software Foundation (ASF) under one or more + - contributor license agreements. See the NOTICE file distributed with + - this work for additional information regarding copyright ownership. + - The ASF licenses this file to You under the Apache License, Version 2.0 + - (the "License"); you may not use this file except in compliance with + - the License. You may obtain a copy of the License at + - + - http://www.apache.org/licenses/LICENSE-2.0 + - + - Unless required by applicable law or agreed to in writing, software + - distributed under the License is distributed on an "AS IS" BASIS, + - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + - See the License for the specific language governing permissions and + - limitations under the License. + --> + +# Implementations Status + +Apache iceberg now has implementations of the iceberg spec in multiple languages. This page provides a summary of the +current status of these implementations. + +## Versions Review Comment: The original design was that the release manager take care of updating this page for each release. > I'm always a bit reluctant with this kind of table since it is easy to forget to update them (PyIceberg is at 0.8.1). Having outdated tables looks bad on the project. What about pointing to the convenience artifacts instead? With this approach it means that the status page maybe outdated compared with actual capability if release manager forgot to update this page. But this seems not a big problem if the release manager could catchup with it. > Do we also want to note when the following table was last updated, or should we just have people check the commit time. How often this the doc site updated? If it's updated for every commit, it seems not a big problem. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
