zhongjiajie commented on code in PR #832:
URL: 
https://github.com/apache/dolphinscheduler-website/pull/832#discussion_r994200128


##########
blog/en-us/Apache_dolphinScheduler_3.0.1.md:
##########
@@ -0,0 +1,154 @@
+---
+title:Apache DolphinScheduler 3.0.1 released, with the scheduling kernel and 
UI optimized
+keywords: Apache,DolphinScheduler,scheduler,big 
data,ETL,airflow,hadoop,orchestration,dataops,Meetup
+description: hanks to this Release Manager — @zhuangchong, who led the release 
of the 3.0.1...
+---
+# Apache DolphinScheduler 3.0.1 released, with the scheduling kernel and UI 
optimized
+
+![](https://miro.medium.com/max/1400/1*zgkZk3lhn3UhLAKkHM9wzQ.png)
+
+Thanks to this Release Manager — zhuangchong, who led the release of the 3.0.1 
version of Apache DolphinScheduler, guided the community to communicate about 
the version optimization, tracked issues before the release, dealt with 
blocking issues, and version quality management, etc. Thanks to his 
contribution to the community, we also expect more Committers and PMCs to play 
the role of **Release Manager**.
+
+More than a month after the official version 3.0.0 was released, the community 
engaged intensively in preparing for the iteration of the new version. We took 
the advice and feedback from the user interviews(including multiple company 
users) as the core development point of version 3.0.1, companies, together with 
hundreds of issue PRs, and nearly 30 contributors’ participation, finally 
launched the long-awaited 3.0.1 version. The new version made some adjustments 
to the UI and scheduling kernel, and at the same time, some bugs in version 
3.0.0 have also been fixed.
+
+Release note:
+
+[https://github.com/apache/dolphinscheduler/releases/tag/3.0.1](https://github.com/apache/dolphinscheduler/releases/tag/3.0.1)
+
+## 1 Scheduling kernel fixes
+
+* Workflow execution runnable trapped an infinite loop
+* The alert of database fields is problematic when upgrading
+* Common users cannot create dependent tasks
+
+Task, workflow instance priority causes NPE(Null Pointer Exception)
+
+* Dependent downstream error trigger
+* Fixed workflow instance possibly cause failing over multiple times
+* The task group gets the task status as running error
+* Fix the issue of triggering OOM( Out of Memory) when the worker kills the 
task

Review Comment:
   ```suggestion
   * Fix the issue of triggering OOM(Out of Memory) when the worker kills the 
task
   ```



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