Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react

2012-10-28 Thread Thomas Goirand
On 10/27/2012 04:47 AM, Dmitry Smirnov wrote: For example if package is not maintained for years we can certainly wait for a month or two before orphaning even though there may be no need to wait that long. This unfortunately cannot be set as a rule. Sometimes, a package that was left

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react

2012-10-28 Thread Dmitry Smirnov
On Mon, 29 Oct 2012 00:21:41 Thomas Goirand wrote: On 10/27/2012 04:47 AM, Dmitry Smirnov wrote: For example if package is not maintained for years we can certainly wait for a month or two before orphaning even though there may be no need to wait that long. This unfortunately cannot be

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react

2012-10-26 Thread Dmitry Smirnov
On Fri, 26 Oct 2012 16:56:02 Bart Martens wrote: On Fri, Oct 26, 2012 at 08:06:57AM +1100, Dmitry Smirnov wrote: If bug was unanswered for let's say two months the package is free to orphan Some prefer no delay, some prefer one month, some prefer two months. I originally wanted one

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react

2012-10-25 Thread Bart Martens
On Fri, Oct 26, 2012 at 08:06:57AM +1100, Dmitry Smirnov wrote: If bug was unanswered for let's say two months the package is free to orphan Some prefer no delay, some prefer one month, some prefer two months. I originally wanted one month, but I got convinced by others to drop the delay. Now