+1 At the same time, it is also important to establish appropriate labels for issues and pull requests. Such as LGTM, watiing review, pr_size, priority and so on. He will make us more efficient in dealing with problems
Best wishes！ CalvinKirs On 09/14/2020 16:53，wu shaoj<[email protected]> wrote： Yes, if the issues only exist before 1.2.0, we should close them directly. On 2020/9/14, 16:45, "lidong dai" <[email protected]> wrote: I think we could speed up the review and merge PR， for now the open issues include 200 features, I think this issues could be excluded what we should focus on the issue(bug or question and so on) , some issues we can close if user no feedback, at the same time some issues could close if question has been solved, some no sense issue also could be closed，some issues is not apache version(before 1.2.0) could be closed how do you think? please leave message, thx Best Regards --------------- DolphinScheduler(Incubator) PPMC Lidong Dai 代立冬 [email protected] --------------- Yichao Yang <[email protected]> 于2020年9月13日周日 下午10:49写道： +1 I think we should leave behind the most important dozens of issues so as to make the development of the project more directional. Best, Yichao Yang ------------------ Original ------------------ From: CalvinKirs <[email protected]> Date: Sun,Sep 13,2020 10:16 PM To: dev <[email protected]> Subject: Re: We need to find a time to focus on the current issue and pr We have accumulated too many PRs and Issues. Up to now, there are 546 open issues and 49 PRs (a small part of it can be merged, and it is not reviewed by users of the committee; some need to be modified, but the author It has not been updated for a long time. In this case, we should close it; some are not responding). The accumulation of too many PRs and issues will affect the trust of users in the community and also affect the continuous contribution of contributors. Please Refer to Open Source Society: Measuring the health of open source projects. Best wishes！ CalvinKirs
