Hello Community,

Apache DolphinScheduler (incubating) has learned and grown a lot since our
incubation in Aug 2019.

I’d like to start a discussion about graduation as TLP for Apache 
DolphinScheduler(Incubating).

I've summarized some of the data below:
- There are 1904 emails sent by 197 people in dev mailing-list excepted GitBox 
forwarded
- Released 8 Apache releases, through 5 different release managers
- Invited 14 new committers (all accepted)
- Invited 2 new PPMC members (all accepted)
- There are 169 contributors for now
- 2064 Issues created during ASF incubating, 1571 Issues resolved during ASF 
incubating
- 2493 PRs created during ASF incubating, 2036 PRs merged during ASF incubating
- finished the Podling Maturity Assessment for DolphinScheduler [1], all items 
are passed
- have created the issue [2] to ensure whether "Apache DolphinScheduler" is a 
suitable name

After talking about prepare graduation in the email thread [7],we have finished 
the following checks.

1.    We updated our Website [3] content,document and so on according to Apache 
rules,we used the url [4] to check and found no potential issue.

2.    The status file [5] has been completed.
For more details,see the checklist [6],welcome to check and add what need doing.

I think we are ready for graduation as Apache TLP.

What do you think?


[1] 
https://cwiki.apache.org/confluence/display/DOLPHINSCHEDULER/Podling+Maturity+Assessment+for+DolphinScheduler
[2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-186
[3] https://dolphinscheduler.apache.org/
[4] https://incubator.apache.org/clutch/dolphinscheduler.html
[5] http://incubator.apache.org/projects/dolphinscheduler.html
[6] 
https://cwiki.apache.org/confluence/display/DOLPHINSCHEDULER/DolphinScheduler+Graduation+Checklist
[7] 
https://lists.apache.org/thread.html/r79381a3fd38d112b5ccb0be67675547e187497135853b0fe999f813a%40%3Cdev.dolphinscheduler.apache.org%3E


Best Regards

------------------------------------------------------
DolphinScheduler(Incubator) PPMC
Gang Li 李岗

[email protected]




Reply via email to