Hi,
Just random thought about the discussion. Please ignore me if it didn't
sounds good.
How about "discontinued" instead of "abandoned", with some automatic
message to describe why it is discontinued.
Note that sometimes user just fail and can't find procedure to reproduce on
his own.
For
Hi,
On Fri, Nov 13, 2015 at 12:33:47AM +0100, Bjoern Michaelsen wrote:
> On Fri, Nov 13, 2015 at 12:00:16AM +0100, Eike Rathke wrote:
> > Hi Wols,
> >
> > On Wednesday, 2015-11-11 19:09:39 +, Wols Lists wrote:
> >
> > > It's getting more wordy but INSUFFICIENT DATA AVAILABLE is a bit more
>
Hi Wols,
On Wednesday, 2015-11-11 19:09:39 +, Wols Lists wrote:
> It's getting more wordy but INSUFFICIENT DATA AVAILABLE is a bit more
> neutral.
insufficient data can not be available
scnr ;-)
Eike
--
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
On Fri, Nov 13, 2015 at 12:00:16AM +0100, Eike Rathke wrote:
> Hi Wols,
>
> On Wednesday, 2015-11-11 19:09:39 +, Wols Lists wrote:
>
> > It's getting more wordy but INSUFFICIENT DATA AVAILABLE is a bit more
> > neutral.
>
>
> insufficient data can not be available
>
Nitpick, but true
On 09/11/15 19:33, Eike Rathke wrote:
> Hu? No. What I meant is have INSUFFICIENTDATA on the same level as
> WORKSFORME and INVALID, a status attribute, not a status. So if a bug
> was in status NEEDINFO for some time and info wasn't provided it can be
> set to RESOLVED INSUFFICIENTDATA and then
On 09.11.2015 23:11, Tommy wrote:
> Joel Madero wrote:
>>
>>>
>>>
>>> I think we should keep labeling those as INVALID
>>>
>>> IMHO the time spent to implement this new
>>> ABANDONED/EXPIRED/WHATEVERstate will be almost useless...
>>>
>>> in both cases the fault of the bug closure is the reporting
Hi,
Just random thought about the discussion. Please ignore me if it didn't
sounds good.
How about "discontinued" instead of "abandoned", with some automatic
message to describe why it is discontinued.
Note that sometimes user just fail and can't find procedure to reproduce on
his own.
For
Joel Madero wrote:
I think we should keep labeling those as INVALID
IMHO the time spent to implement this new
ABANDONED/EXPIRED/WHATEVERstate will be almost useless...
in both cases the fault of the bug closure is the reporting user
so I really do not care at all being diplomatic with
On Mon, Nov 9, 2015 at 12:13 PM, Joel Madero wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>>
>> Insufficient Data though can also be used for situations where a bug can
>> not be reproduced due to, well, insufficient data.. i.e. happened one
>> time crash
On Mon, Nov 9, 2015 at 12:13 PM, Joel Madero wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>>
>> Insufficient Data though can also be used for situations where a bug can
>> not be reproduced due to, well, insufficient data.. i.e. happened one
>> time crash
> * ABANDONED
> * INSUFFICIENT DATA (RedHat)
> * EXPIRED (Launchpad)
Of these I like ABANDONED as it indicates that the user abandoned
his/her own bug. Insufficient Data is really wordy to me, Expired
indicates that the user could just set the bug back to UNCONFIRMED and
say "this is still a
> * ABANDONED
> * INSUFFICIENT DATA (RedHat)
> * EXPIRED (Launchpad)
Of these I like ABANDONED as it indicates that the user abandoned
his/her own bug. Insufficient Data is really wordy to me, Expired
indicates that the user could just set the bug back to UNCONFIRMED and
say "this is still a
Hi Joel,
On Monday, 2015-11-09 09:23:20 -0800, Joel Madero wrote:
> > * ABANDONED
> > * INSUFFICIENT DATA (RedHat)
> > * EXPIRED (Launchpad)
>
> Of these I like ABANDONED as it indicates that the user abandoned
> his/her own bug. Insufficient Data is really wordy to me,
Insufficient Data
Hi Joel,
On Monday, 2015-11-09 09:23:20 -0800, Joel Madero wrote:
> > * ABANDONED
> > * INSUFFICIENT DATA (RedHat)
> > * EXPIRED (Launchpad)
>
> Of these I like ABANDONED as it indicates that the user abandoned
> his/her own bug. Insufficient Data is really wordy to me,
Insufficient Data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Insufficient Data though can also be used for situations where a bug can
> not be reproduced due to, well, insufficient data.. i.e. happened one
> time crash and no stack trace, no exact steps to reproduce, even if the
> reporter was or would be
On 11/09/2015 11:15 AM, Bjoern Michaelsen wrote:
> On Mon, Nov 09, 2015 at 07:10:44PM +0100, Eike Rathke wrote:
>> Insufficient Data though can also be used for situations where a bug can
>> not be reproduced due to, well, insufficient data.. i.e. happened one
>> time crash and no stack trace,
On 11/09/2015 11:15 AM, Bjoern Michaelsen wrote:
> On Mon, Nov 09, 2015 at 07:10:44PM +0100, Eike Rathke wrote:
>> Insufficient Data though can also be used for situations where a bug can
>> not be reproduced due to, well, insufficient data.. i.e. happened one
>> time crash and no stack trace,
Hi,
On Mon, Nov 09, 2015 at 09:23:20AM -0800, Joel Madero wrote:
> > * ABANDONED
> > * INSUFFICIENT DATA (RedHat)
> > * EXPIRED (Launchpad)
>
> Of these I like ABANDONED as it indicates that the user abandoned
> his/her own bug. Insufficient Data is really wordy to me, Expired
> indicates that
On Mon, Nov 09, 2015 at 07:10:44PM +0100, Eike Rathke wrote:
> Insufficient Data though can also be used for situations where a bug can
> not be reproduced due to, well, insufficient data.. i.e. happened one
> time crash and no stack trace, no exact steps to reproduce, even if the
> reporter was
On Mon, Nov 09, 2015 at 07:10:44PM +0100, Eike Rathke wrote:
> Insufficient Data though can also be used for situations where a bug can
> not be reproduced due to, well, insufficient data.. i.e. happened one
> time crash and no stack trace, no exact steps to reproduce, even if the
> reporter was
>
>
> I think we should keep labeling those as INVALID
>
> IMHO the time spent to implement this new
> ABANDONED/EXPIRED/WHATEVERstate will be almost useless...
>
> in both cases the fault of the bug closure is the reporting user
> so I really do not care at all being diplomatic with people who
>
>
> I think we should keep labeling those as INVALID
>
> IMHO the time spent to implement this new
> ABANDONED/EXPIRED/WHATEVERstate will be almost useless...
>
> in both cases the fault of the bug closure is the reporting user
> so I really do not care at all being diplomatic with people who
Hi Bjoern,
On Monday, 2015-11-09 20:15:39 +0100, Bjoern Michaelsen wrote:
> On Mon, Nov 09, 2015 at 07:10:44PM +0100, Eike Rathke wrote:
> > Insufficient Data though can also be used for situations where a bug can
> > not be reproduced due to, well, insufficient data.. i.e. happened one
> > time
Hi Bjoern,
On Monday, 2015-11-09 20:15:39 +0100, Bjoern Michaelsen wrote:
> On Mon, Nov 09, 2015 at 07:10:44PM +0100, Eike Rathke wrote:
> > Insufficient Data though can also be used for situations where a bug can
> > not be reproduced due to, well, insufficient data.. i.e. happened one
> > time
Robinson Tryon wrote:
Hi all,
As mentioned in the ESC call, it could be helpful to add a new
Bugzilla Status that encompasses bugs that have been abandoned/don't
have enough data.
=> What type of bugs would this cover?
* User isn't willing to share private document with anyone, and we
can't
25 matches
Mail list logo