sjwiesman commented on a change in pull request #478:
URL: https://github.com/apache/flink-web/pull/478#discussion_r740504278



##########
File path: _posts/2021-11-03-flink-backward.md
##########
@@ -0,0 +1,79 @@
+---
+layout: post
+title: "Flink Backward - The Apache Flink Retrospective"
+date: 2021-11-03 00:00:00
+authors:
+- joemoe:
+  name: "Johannes Moser"
+excerpt: A look back at the development cycle for Flink 1.14 
+---
+
+It has now been a month since [Apache Flink 
1.14](https://flink.apache.org/downloads.html#apache-flink-1140) has been 
released into the wild. :partying_face: We had a comprehensive look at the 
enhancements, additions, and fixups in the [release announcement blog 
post](https://flink.apache.org/news/2021/09/29/release-1.14.0.html) and now we 
will have a look at the development cycle from a different angle. Based on 
feedback collected from contributors involved in this release, we will explore 
the experiences and processes behind it all.  
+
+{% toc %}
+
+# A retrospective on the release cycle
+
+From the team, we collected emotions that have been attributed to points in 
time of the 1.14 release cycle:
+
+<center>
+<img 
src="{{site.baseurl}}/img/blog/2021-11-03-flink-backward/1.14-weather.png" 
width="70%"/>
+</center>
+
+The overall sentiment seems to be quite good. A ship crushed a robot two 
times, someone felt sick towards the end, an octopus causing negative emotions 
appeared in June...
+
+We looked at the origin of these emotions and came up with an analysis of what 
went well and what could be improved. We also incorporated some feedback 
gathered from the community.
+
+## Problems faced
+
+From a content perspective, the community is still ironing out processes 
around documentation and blog posts. There have been a lot of test 
instabilities and issues with some of the efforts to fix them. We also had to 
push the feature freeze by two weeks, which might actually be considered early 
and not actually be living up to the Apache Flink release tradition. :p
+

Review comment:
       I now see I've added some overlap to what's written below, so happy to 
change this but I think it needs more than what was already there. 




-- 
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