lindong28 commented on a change in pull request #57:
URL: https://github.com/apache/flink-ml/pull/57#discussion_r805822290



##########
File path: docs/content/posts/release-ml-2.0.0.md
##########
@@ -0,0 +1,272 @@
+---
+layout: post 
+title:  "Apache Flink ML 2.0.0 Release Announcement"
+date: 2022-01-07T08:00:00.000Z
+type: docs
+categories: news
+authors:
+- lindong:
+  name: "Dong Lin"
+- gaoyun:
+  name: "Yun Gao"
+
+excerpt: The Apache Flink community is excited to announce the release of 
Flink ML 2.0.0! This release involves a major refactor of the earlier Flink ML 
library and introduces major features that extend the Flink ML API and the 
iteration runtime, such as supporting stages with multi-input multi-output, 
graph-based stage composition, and a new stream-batch unified iteration library.
+
+---
+<!--
+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.
+-->
+
+The Apache Flink community is excited to announce the release of Flink ML

Review comment:
       Could we avoid copy/paste the entire blog post from flink-web? We can 
use URL if needed.




-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to