sfc-gh-emaynard commented on code in PR #1890:
URL: https://github.com/apache/polaris/pull/1890#discussion_r2152560871


##########
site/content/in-dev/unreleased/evolution.md:
##########
@@ -0,0 +1,115 @@
+---
+#
+# 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.
+#
+title: Polaris Evolution
+type: docs
+weight: 1000
+---
+
+This page discusses what can be expected from Apache Polaris as the project 
evolves.
+
+## Using Polaris as a Catalog
+
+Polaris is primarily intended to be used as a Catalog of Tables and Views. As 
such, 
+it implements the Iceberg REST Catalog API and its own REST APIs.
+
+Revisions of the Iceberg REST Catalog API are controlled by the [Apache 
Iceberg](https://iceberg.apache.org/)
+community. Polaris attempts to accurately implement this specification. 
Nonetheless,
+optional REST Catalog features may or may not be supported immediately. In 
general,
+there is no guarantee that Polaris releases always implement the latest 
version of
+the Iceberg REST Catalog API.
+
+Any API under Polaris control that is not in an "experimental" or "beta" state 
+(e.g. the Management API) is maintained as a versioned REST API. New releases 
of Polaris
+may include changes to the current version of the API. When that happens those 
changes
+are intended to be compatible with prior versions of Polaris clients. Certain 
endpoints
+and parameters may be deprecated.
+
+In case a major change is required to the Management API that cannot be 
implemented in a

Review Comment:
   ```suggestion
   In case a major change is required to an API that cannot be implemented in a
   ```
   
   This isn't specific to management, right?



##########
site/content/in-dev/unreleased/evolution.md:
##########
@@ -0,0 +1,115 @@
+---
+#
+# 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.
+#
+title: Polaris Evolution
+type: docs
+weight: 1000
+---
+
+This page discusses what can be expected from Apache Polaris as the project 
evolves.
+
+## Using Polaris as a Catalog
+
+Polaris is primarily intended to be used as a Catalog of Tables and Views. As 
such, 
+it implements the Iceberg REST Catalog API and its own REST APIs.
+
+Revisions of the Iceberg REST Catalog API are controlled by the [Apache 
Iceberg](https://iceberg.apache.org/)
+community. Polaris attempts to accurately implement this specification. 
Nonetheless,
+optional REST Catalog features may or may not be supported immediately. In 
general,
+there is no guarantee that Polaris releases always implement the latest 
version of
+the Iceberg REST Catalog API.
+
+Any API under Polaris control that is not in an "experimental" or "beta" state 
+(e.g. the Management API) is maintained as a versioned REST API. New releases 
of Polaris
+may include changes to the current version of the API. When that happens those 
changes
+are intended to be compatible with prior versions of Polaris clients. Certain 
endpoints
+and parameters may be deprecated.
+
+In case a major change is required to the Management API that cannot be 
implemented in a

Review Comment:
   ```suggestion
   In case a major change is required to an API that cannot be implemented in a
   ```
   
   This isn't specific to management, right?



-- 
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...@polaris.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to