You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by * yaalsn <ya...@gmail.com> on 2022/02/23 08:26:44 UTC
RE: [DISCUSS] Add icebox label for issues and PRs that have been inactive for more than 4 weeks
Hi All,
This pr https://github.com/apache/pulsar/pull/14390 can help us. If any issue or pr had no activity for 30 days, Github action will tag a Stale label with it.
On 2022/01/12 16:15:16 PengHui Li wrote:
> Hi Pulsar Community,
>
> I want to start a discussion about introducing an icebox label that can be
> added to
> the issue or PR by pulsar bot automatically to help us can focus on the
> active PRs
> and issue. To avoid missing merge PRs, review PRs, triage issues.
>
> It looks like the following:
>
> 1. If the issue or PR is inactive for more than 4 weeks, the pulsar bot add
> the icebox label
> 2. If the issue or PR is re-active again, the pulsar bot remove the icebox
> label
>
> How to determine the PR or issue is inactive?
>
> 1. No comments for 4 weeks.
> 2. No code review(approve, comment, or change request) for 4 weeks.
> 3. No commits for 4 weeks.
> 4. No description update for 4 weeks.
>
> How to determine the PR or issue is re-inactive?
>
> With the icebox label first and:
>
> 1. New comment added
> 2. New commits pushed
> 3. Description updated
> 4. New code review updates
>
> Note: all the approved PRs we should not add the icebox label
>
> This will help us to focus on the active issues and PRs so that we can
> track the active issues and PRs better first. After we get this part done
> (maybe keep active opened PR under 20 and active opened issue under 50?),
> we can move forward to continue to handle the stale PRs (already discussed
> in https://lists.apache.org/thread/k7lyw0q0fyc729w0fqlj5vqng5ny63f2).
>
> Thanks,
> Penghui
>
Re: [DISCUSS] Add icebox label for issues and PRs that have been inactive for more than 4 weeks
Posted by PengHui Li <pe...@apache.org>.
Hi all,
We have completed the Stale label for the PRs and issues.
So that, we can focus on the active PRs[1] and active issues[2].
Thanks for the great work, yaaln.
If you are interested in the PR review and give an answer to the issue,
it's a good start to let us focus on the active PRs and issues.
[1]
https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+-label%3AStale
[2]
https://github.com/apache/pulsar/issues?q=is%3Aissue+is%3Aopen+-label%3AStale+
Penghui
On Thu, Feb 24, 2022 at 9:18 AM PengHui Li <pe...@apache.org> wrote:
> > This pr https://github.com/apache/pulsar/pull/14390 can help us. If any
> issue or pr had no activity for 30 days, Github action will tag a Stale
> label with it.
>
> Thanks for the great work, I have merged the PR.
>
> Penghui
>
> On Thu, Feb 24, 2022 at 1:11 AM * yaalsn <ya...@gmail.com> wrote:
>
>> Hi All,
>>
>> This pr https://github.com/apache/pulsar/pull/14390 can help us. If any
>> issue or pr had no activity for 30 days, Github action will tag a Stale
>> label with it.
>>
>> On 2022/01/12 16:15:16 PengHui Li wrote:
>> > Hi Pulsar Community,
>> >
>> > I want to start a discussion about introducing an icebox label that can
>> be
>> > added to
>> > the issue or PR by pulsar bot automatically to help us can focus on the
>> > active PRs
>> > and issue. To avoid missing merge PRs, review PRs, triage issues.
>> >
>> > It looks like the following:
>> >
>> > 1. If the issue or PR is inactive for more than 4 weeks, the pulsar bot
>> add
>> > the icebox label
>> > 2. If the issue or PR is re-active again, the pulsar bot remove the
>> icebox
>> > label
>> >
>> > How to determine the PR or issue is inactive?
>> >
>> > 1. No comments for 4 weeks.
>> > 2. No code review(approve, comment, or change request) for 4 weeks.
>> > 3. No commits for 4 weeks.
>> > 4. No description update for 4 weeks.
>> >
>> > How to determine the PR or issue is re-inactive?
>> >
>> > With the icebox label first and:
>> >
>> > 1. New comment added
>> > 2. New commits pushed
>> > 3. Description updated
>> > 4. New code review updates
>> >
>> > Note: all the approved PRs we should not add the icebox label
>> >
>> > This will help us to focus on the active issues and PRs so that we can
>> > track the active issues and PRs better first. After we get this part
>> done
>> > (maybe keep active opened PR under 20 and active opened issue under
>> 50?),
>> > we can move forward to continue to handle the stale PRs (already
>> discussed
>> > in https://lists.apache.org/thread/k7lyw0q0fyc729w0fqlj5vqng5ny63f2).
>> >
>> > Thanks,
>> > Penghui
>> >
>
>
Re: [DISCUSS] Add icebox label for issues and PRs that have been inactive for more than 4 weeks
Posted by PengHui Li <pe...@apache.org>.
> This pr https://github.com/apache/pulsar/pull/14390 can help us. If any
issue or pr had no activity for 30 days, Github action will tag a Stale
label with it.
Thanks for the great work, I have merged the PR.
Penghui
On Thu, Feb 24, 2022 at 1:11 AM * yaalsn <ya...@gmail.com> wrote:
> Hi All,
>
> This pr https://github.com/apache/pulsar/pull/14390 can help us. If any
> issue or pr had no activity for 30 days, Github action will tag a Stale
> label with it.
>
> On 2022/01/12 16:15:16 PengHui Li wrote:
> > Hi Pulsar Community,
> >
> > I want to start a discussion about introducing an icebox label that can
> be
> > added to
> > the issue or PR by pulsar bot automatically to help us can focus on the
> > active PRs
> > and issue. To avoid missing merge PRs, review PRs, triage issues.
> >
> > It looks like the following:
> >
> > 1. If the issue or PR is inactive for more than 4 weeks, the pulsar bot
> add
> > the icebox label
> > 2. If the issue or PR is re-active again, the pulsar bot remove the
> icebox
> > label
> >
> > How to determine the PR or issue is inactive?
> >
> > 1. No comments for 4 weeks.
> > 2. No code review(approve, comment, or change request) for 4 weeks.
> > 3. No commits for 4 weeks.
> > 4. No description update for 4 weeks.
> >
> > How to determine the PR or issue is re-inactive?
> >
> > With the icebox label first and:
> >
> > 1. New comment added
> > 2. New commits pushed
> > 3. Description updated
> > 4. New code review updates
> >
> > Note: all the approved PRs we should not add the icebox label
> >
> > This will help us to focus on the active issues and PRs so that we can
> > track the active issues and PRs better first. After we get this part done
> > (maybe keep active opened PR under 20 and active opened issue under 50?),
> > we can move forward to continue to handle the stale PRs (already
> discussed
> > in https://lists.apache.org/thread/k7lyw0q0fyc729w0fqlj5vqng5ny63f2).
> >
> > Thanks,
> > Penghui
> >