Re: Proposal: Unassign idle issues

2022-08-02 Thread Todd Farmer
Thank you all for the feedback on the proposal. I unassigned 371 idle (not updated within past 90 days) issues on 2022-07-12 [1]. It doesn't appear that this action has caused problems or confusion - please let me know if I've missed anything. There are currently an additional 31 issues that are no

Re: Proposal: Unassign idle issues

2022-07-12 Thread Antoine Pitrou
On Fri, 8 Jul 2022 09:49:28 -0600 Todd Farmer wrote: > > In summary, here are the actions I propose: > > 1. Establish a threshold at which assigned, idle issues should be > unassigned and comment added. > 2. Define that threshold to be 90 days. > 3. Document the above as a project policy for iss

Re: Proposal: Unassign idle issues

2022-07-08 Thread Weston Pace
+1 (I'm assuming, as Neal described, I can just reassign the issue to myself and it won't confuse the assignment bot) On Fri, Jul 8, 2022 at 8:29 AM Jacob Wujciak wrote: > > I support this idea and a 90 days threshold seems good to me! > > On Fri, Jul 8, 2022 at 8:02 PM Neal Richardson > wrote:

Re: Proposal: Unassign idle issues

2022-07-08 Thread Jacob Wujciak
I support this idea and a 90 days threshold seems good to me! On Fri, Jul 8, 2022 at 8:02 PM Neal Richardson wrote: > Sounds like a good idea to me, thanks for taking the initiative on this. > > To Benson's idea about varying the timeout based on priority, IMO we could > just start with the simp

Re: Proposal: Unassign idle issues

2022-07-08 Thread Neal Richardson
Sounds like a good idea to me, thanks for taking the initiative on this. To Benson's idea about varying the timeout based on priority, IMO we could just start with the simple approach and see how that goes. Maybe that would be helpful but maybe it's not necessary. If you're truly watching an issue

Re: Proposal: Unassign idle issues

2022-07-08 Thread Benson Muite
On 7/8/22 18:49, Todd Farmer wrote: Hello, The backlog of ARROW issues currently stands at 2585 open issues [1]. The size of the backlog presents challenges to users and developers alike, and I believe the project would benefit from establishing guidance around issue handling. I'll be submitting

Proposal: Unassign idle issues

2022-07-08 Thread Todd Farmer
Hello, The backlog of ARROW issues currently stands at 2585 open issues [1]. The size of the backlog presents challenges to users and developers alike, and I believe the project would benefit from establishing guidance around issue handling. I'll be submitting a series of proposals for discussion,