Re: Trac default milestone

2008-08-06 Thread Simon Schampijer
Michael Stone wrote: > On Thu, Jul 31, 2008 at 06:48:32PM +0200, Marco Pesenti Gritti wrote: >> On Mon, Jul 28, 2008 at 11:38 PM, Marco Pesenti Gritti >> <[EMAIL PROTECTED]> wrote: >>> Trac default milestone is currently 8.2. Is that a good idea? We are >>>

Re: Trac default milestone

2008-08-06 Thread Simon Schampijer
Michael Stone wrote: > On Thu, Jul 31, 2008 at 06:53:26PM +0200, Marco Pesenti Gritti wrote: >> On Tue, Jul 29, 2008 at 2:52 AM, Marco Pesenti Gritti >> <[EMAIL PROTECTED]> wrote: >>> Also I'm not convinced "not specified" as default component is a good >>> idea, unless we have someone taking care

Re: Trac default milestone

2008-07-31 Thread Marco Pesenti Gritti
Michael Stone wrote: > On Thu, Jul 31, 2008 at 08:21:23PM +0200, Marco Pesenti Gritti wrote: >> Because I'm not confident someone will regularly take care of >> assigning the not-specified tickets, and I don't want lose useful >> bug reports because of that. I've been reading all the coming in

Re: Trac default milestone

2008-07-31 Thread Michael Stone
On Thu, Jul 31, 2008 at 08:21:23PM +0200, Marco Pesenti Gritti wrote: > Because I'm not confident someone will regularly take care of assigning > the not-specified tickets, and I don't want lose useful bug reports > because of that. I've been reading all the coming in tickets in the last > fe

Re: Trac default milestone

2008-07-31 Thread Marco Pesenti Gritti
Michael Stone wrote: > On Thu, Jul 31, 2008 at 06:53:26PM +0200, Marco Pesenti Gritti wrote: >> On Tue, Jul 29, 2008 at 2:52 AM, Marco Pesenti Gritti >> <[EMAIL PROTECTED]> wrote: >>> Also I'm not convinced "not specified" as default component is a good >>> idea, unless we have someone taking care

Re: Trac default milestone

2008-07-31 Thread Michael Stone
On Thu, Jul 31, 2008 at 06:53:26PM +0200, Marco Pesenti Gritti wrote: >On Tue, Jul 29, 2008 at 2:52 AM, Marco Pesenti Gritti ><[EMAIL PROTECTED]> wrote: >> Also I'm not convinced "not specified" as default component is a good >> idea, unless we have someone taking care of triaging that component. >

Re: Trac default milestone

2008-07-31 Thread Marco Pesenti Gritti
On Thu, Jul 31, 2008 at 7:06 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > I'm don't feel strongly either way but it's clearly important to Marco. > My concern is that we have a lot of unresponsive module maintainers. The only way to get around the unresponsive maintainers problems is to get othe

Re: Trac default milestone

2008-07-31 Thread Michael Stone
On Thu, Jul 31, 2008 at 06:48:32PM +0200, Marco Pesenti Gritti wrote: >On Mon, Jul 28, 2008 at 11:38 PM, Marco Pesenti Gritti ><[EMAIL PROTECTED]> wrote: >> Trac default milestone is currently 8.2. Is that a good idea? We are >> trying to punt down the Sugar 8.2 bugs, bu

Re: Trac default milestone

2008-07-31 Thread Marco Pesenti Gritti
On Tue, Jul 29, 2008 at 2:52 AM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > Also I'm not convinced "not specified" as default component is a good > idea, unless we have someone taking care of triaging that component. Can we go back to require the submitter to provide a component? In many ca

Re: Trac default milestone

2008-07-31 Thread Marco Pesenti Gritti
On Mon, Jul 28, 2008 at 11:38 PM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > Trac default milestone is currently 8.2. Is that a good idea? We are > trying to punt down the Sugar 8.2 bugs, but with these default the > list keep growing. I'd prefer to go through the list

Re: Trac default milestone

2008-07-28 Thread Marco Pesenti Gritti
Also I'm not convinced "not specified" as default component is a good idea, unless we have someone taking care of triaging that component. Marco On Mon, Jul 28, 2008 at 11:38 PM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > Trac default milestone is currently 8.2.

Trac default milestone

2008-07-28 Thread Marco Pesenti Gritti
Trac default milestone is currently 8.2. Is that a good idea? We are trying to punt down the Sugar 8.2 bugs, but with these default the list keep growing. I'd prefer to go through the list of unassigned bugs every few days and make 8.2 only those that really needs to be...