Loading...
 

Tikiwiki-devel (mailman list mirror)


dev.tiki.org issue tracker: category for bugs

Hi Brendan,
https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are examples.
Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues or conflict between 2 features.

> -----Message d’origine-----
> De : Dr. Sassafras mailto:drsassafras@gmail.com
> Envoyé : 17 juillet 2017 13:43
> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>
> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
> would work?
>
> Brendan
>

> > On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

> mffp.gouv.qc.ca> wrote:
> >
> > Hi,
> > Our issue tracker has the following categories for bugs:
> > Bug: Consistency
> > Bug: Error
> > Bug: Regression
> > Bug: Security
> > Bug: Usability
> > Bug: conflict of two features (each works well independently)
> >
> > But it appears to lack a category for bugs in general. I am considering to create either “Bug: general”
> or “Bug”. If anyone opposes, please speak up.
> >
> >

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

posts: 683 Canada

Could a “bug: Unexpected Behaviour”, “Bug: User Interface” fix this?

I hesitate to give the option for people not not select an option.

Maybe “Bug: Other”, so it’s really clear that they need to select the another option before using that one?

Brendan

> On Jul 17, 2017, at 2:48 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-mffp.gouv.qc.ca> wrote:

>
> Hi Brendan,
> https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are examples.
> Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues or conflict between 2 features.
>
>> -----Message d’origine-----
>> De : Dr. Sassafras mailto:drsassafras@gmail.com
>> Envoyé : 17 juillet 2017 13:43
>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>
>> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
>> would work?
>>
>> Brendan
>>

>>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

>> mffp.gouv.qc.ca> wrote:
>>>
>>> Hi,
>>> Our issue tracker has the following categories for bugs:
>>> Bug: Consistency
>>> Bug: Error
>>> Bug: Regression
>>> Bug: Security
>>> Bug: Usability
>>> Bug: conflict of two features (each works well independently)
>>>
>>> But it appears to lack a category for bugs in general. I am considering to create either “Bug: general”
>> or “Bug”. If anyone opposes, please speak up.
>>>
>>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

Don’t pretty much all bugs arguably cause unexpected behaviour?
Bug: User Interface can reduce the number of uncategorizable bugs, but it does not fit all the rest. And it is fairly vague.

I understand your reluctance and considered myself “Bug: Miscellaneous”. But if you have both “Bug: Regression” and “Bug: Miscellaneous”, there’s a logical expectation that “Bug: Miscellaneous” won’t contain regressions. Yet we can’t expect users to always know whether a bug is a regression.

> -----Message d’origine-----
> De : Dr. Sassafras mailto:drsassafras@gmail.com
> Envoyé : 17 juillet 2017 15:04
> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>
> Could a “bug: Unexpected Behaviour”, “Bug: User Interface” fix this?
>
> I hesitate to give the option for people not not select an option.
>
> Maybe “Bug: Other”, so it’s really clear that they need to select the another option before using that
> one?
>
> Brendan
>

> > On Jul 17, 2017, at 2:48 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

> mffp.gouv.qc.ca> wrote:
> >
> > Hi Brendan,
> > https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are
> examples.
> > Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues
> or conflict between 2 features.
> >
> >> -----Message d’origine-----
> >> De : Dr. Sassafras mailto:drsassafras@gmail.com
> >> Envoyé : 17 juillet 2017 13:43
> >> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> >> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
> >>
> >> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
> >> would work?
> >>
> >> Brendan
> >>
> >>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant)

> <Philippe.Cloutier.externe@mern-

> >> mffp.gouv.qc.ca> wrote:
> >>>
> >>> Hi,
> >>> Our issue tracker has the following categories for bugs:
> >>> Bug: Consistency
> >>> Bug: Error
> >>> Bug: Regression
> >>> Bug: Security
> >>> Bug: Usability
> >>> Bug: conflict of two features (each works well independently)
> >>>
> >>> But it appears to lack a category for bugs in general. I am considering to create either “Bug:
> general”
> >> or “Bug”. If anyone opposes, please speak up.
> >>>
> >>>
> >
> > ------------------------------------------------------------------------------
> > Check out the vibrant tech community on one of the world’s most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___
> > TikiWiki-devel mailing list
> > TikiWiki-devel at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

posts: 683 Canada


> Don’t pretty much all bugs arguably cause unexpected behaviour?

That’s an interesting point. But in contrast to “Bug: Error” I would say no. The class of bugs your talking about here are bugs where there is no error message, (or clear error) but the result is not expected.... otherwise it could be classified as bug: error

I guess the other way to handle this is to change them to check boxes. It kinda doesn’t make sense to have to choose between “bug:error, and bug:regression” cause it could be both, or maybe 3.

> Bug: User Interface can reduce the number of uncategorizable bugs, but it does not fit all the rest. And it is fairly vague.

It’s less vague than “bug” though.
>
> I understand your reluctance and considered myself “Bug: Miscellaneous”. But if you have both “Bug: Regression” and “Bug: Miscellaneous”, there’s a logical expectation that “Bug: Miscellaneous” won’t contain regressions. Yet we can’t expect users to always know whether a bug is a regression.

That’s right, but the same argument could be applied against all of our non-regression categories.

Brendan

>
>> -----Message d’origine-----
>> De : Dr. Sassafras mailto:drsassafras@gmail.com
>> Envoyé : 17 juillet 2017 15:04
>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>
>> Could a “bug: Unexpected Behaviour”, “Bug: User Interface” fix this?
>>
>> I hesitate to give the option for people not not select an option.
>>
>> Maybe “Bug: Other”, so it’s really clear that they need to select the another option before using that
>> one?
>>
>> Brendan
>>

>>> On Jul 17, 2017, at 2:48 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

>> mffp.gouv.qc.ca> wrote:
>>>
>>> Hi Brendan,
>>> https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are
>> examples.
>>> Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues
>> or conflict between 2 features.
>>>
>>>> -----Message d’origine-----
>>>> De : Dr. Sassafras mailto:drsassafras@gmail.com
>>>> Envoyé : 17 juillet 2017 13:43
>>>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>>>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>>>
>>>> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
>>>> would work?
>>>>
>>>> Brendan
>>>>
>>>>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant)

>> <Philippe.Cloutier.externe@mern-

>>>> mffp.gouv.qc.ca> wrote:
>>>>>
>>>>> Hi,
>>>>> Our issue tracker has the following categories for bugs:
>>>>> Bug: Consistency
>>>>> Bug: Error
>>>>> Bug: Regression
>>>>> Bug: Security
>>>>> Bug: Usability
>>>>> Bug: conflict of two features (each works well independently)
>>>>>
>>>>> But it appears to lack a category for bugs in general. I am considering to create either “Bug:
>> general”
>>>> or “Bug”. If anyone opposes, please speak up.
>>>>>
>>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world’s most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> TikiWiki-devel mailing list
>>> TikiWiki-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world’s most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> TikiWiki-devel mailing list
>> TikiWiki-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

Hi Brendan,

> -----Message d’origine-----
> De : Dr. Sassafras mailto:drsassafras@gmail.com
> Envoyé : 17 juillet 2017 17:23
> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>
>
> > Don’t pretty much all bugs arguably cause unexpected behaviour?
>
> That’s an interesting point. But in contrast to “Bug: Error” I would say no. The class of bugs your talking
> about here are bugs where there is no error message, (or clear error) but the result is not expected....
> otherwise it could be classified as bug: error

If so, that is not clear from the name, but in any case, I was saying that pretty much all bugs arguably cause unexpected behavior.

>
> I guess the other way to handle this is to change them to check boxes. It kinda doesn’t make sense to
> have to choose between “bug:error, and bug:regression” cause it could be both, or maybe 3.

I agree that multiple states can apply, but multiple categories can already be selected.

> > Bug: User Interface can reduce the number of uncategorizable bugs, but it does not fit all the rest.
> And it is fairly vague.
>
> It’s less vague than “bug” though.

Right, I should have written “subjective”, sorry. What I meant is that it’s not necessarily easy for a user to say if a bug is a UI bug. If the user sees wrong data displayed by the UI, he can only guess if the problem is in the front-end or the back-end.

> > I understand your reluctance and considered myself “Bug: Miscellaneous”. But if you have both
> “Bug: Regression” and “Bug: Miscellaneous”, there’s a logical expectation that “Bug: Miscellaneous”
> won’t contain regressions. Yet we can’t expect users to always know whether a bug is a regression.
>
> That’s right, but the same argument could be applied against all of our non-regression categories.

Indeed.

>
> Brendan
>
> >
> >> -----Message d’origine-----
> >> De : Dr. Sassafras mailto:drsassafras@gmail.com
> >> Envoyé : 17 juillet 2017 15:04
> >> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> >> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
> >>
> >> Could a “bug: Unexpected Behaviour”, “Bug: User Interface” fix this?
> >>
> >> I hesitate to give the option for people not not select an option.
> >>
> >> Maybe “Bug: Other”, so it’s really clear that they need to select the another option before using
> that
> >> one?
> >>
> >> Brendan
> >>
> >>> On Jul 17, 2017, at 2:48 PM, Cloutier, Philippe (DGARI-Consultant)

> <Philippe.Cloutier.externe@mern-

> >> mffp.gouv.qc.ca> wrote:
> >>>
> >>> Hi Brendan,
> >>> https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401
> are
> >> examples.
> >>> Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability
> issues
> >> or conflict between 2 features.
> >>>
> >>>> -----Message d’origine-----
> >>>> De : Dr. Sassafras mailto:drsassafras@gmail.com
> >>>> Envoyé : 17 juillet 2017 13:43
> >>>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> >>>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
> >>>>
> >>>> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another
> category
> >>>> would work?
> >>>>
> >>>> Brendan
> >>>>
> >>>>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant)

> >> <Philippe.Cloutier.externe@mern-

> >>>> mffp.gouv.qc.ca> wrote:
> >>>>>
> >>>>> Hi,
> >>>>> Our issue tracker has the following categories for bugs:
> >>>>> Bug: Consistency
> >>>>> Bug: Error
> >>>>> Bug: Regression
> >>>>> Bug: Security
> >>>>> Bug: Usability
> >>>>> Bug: conflict of two features (each works well independently)
> >>>>>
> >>>>> But it appears to lack a category for bugs in general. I am considering to create either “Bug:
> >> general”
> >>>> or “Bug”. If anyone opposes, please speak up.
> >>>>>
> >>>>>
> >>>
> >>> ------------------------------------------------------------------------------
> >>> Check out the vibrant tech community on one of the world’s most
> >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >>> ___
> >>> TikiWiki-devel mailing list
> >>> TikiWiki-devel at lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> >>
> >> ------------------------------------------------------------------------------
> >> Check out the vibrant tech community on one of the world’s most
> >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >> ___
> >> TikiWiki-devel mailing list
> >> TikiWiki-devel at lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
> > ------------------------------------------------------------------------------
> > Check out the vibrant tech community on one of the world’s most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___
> > TikiWiki-devel mailing list
> > TikiWiki-devel at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel


posts: 3053 United Kingdom


Aren’t they both regressions?

jb


> On 17 Jul 2017, at 19:48, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-mffp.gouv.qc.ca> wrote:

>
> Hi Brendan,
> https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are examples.
> Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues or conflict between 2 features.
>
>> -----Message d’origine-----
>> De : Dr. Sassafras mailto:drsassafras@gmail.com
>> Envoyé : 17 juillet 2017 13:43
>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>
>> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
>> would work?
>>
>> Brendan
>>

>>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

>> mffp.gouv.qc.ca> wrote:
>>>
>>> Hi,
>>> Our issue tracker has the following categories for bugs:
>>> Bug: Consistency
>>> Bug: Error
>>> Bug: Regression
>>> Bug: Security
>>> Bug: Usability
>>> Bug: conflict of two features (each works well independently)
>>>
>>> But it appears to lack a category for bugs in general. I am considering to create either “Bug: general”
>> or “Bug”. If anyone opposes, please speak up.
>>>
>>>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

Hi Jonny,
Heh, good point.

I don’t know if #6394 is a regression.

But #6401 can certainly be considered as a regression. Although one could argue the opposite since this new insertion screen did not exist before, so an instance can be configured to remain as reliable as before. I nearly mentioned in my last mail that the distinction between regressions and non-regressions is additionally not always clear-cut.

> -----Message d’origine-----
> De : Jonny Bradley mailto:jonny@tiki.org
> Envoyé : 17 juillet 2017 15:17
> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>
>
> Aren’t they both regressions?
>
> jb
>
>
>

> > On 17 Jul 2017, at 19:48, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

> mffp.gouv.qc.ca> wrote:
> >
> > Hi Brendan,
> > https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are
> examples.
> > Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues
> or conflict between 2 features.
> >
> >> -----Message d’origine-----
> >> De : Dr. Sassafras mailto:drsassafras@gmail.com
> >> Envoyé : 17 juillet 2017 13:43
> >> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
> >> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
> >>
> >> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
> >> would work?
> >>
> >> Brendan
> >>
> >>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant)

> <Philippe.Cloutier.externe@mern-

> >> mffp.gouv.qc.ca> wrote:
> >>>
> >>> Hi,
> >>> Our issue tracker has the following categories for bugs:
> >>> Bug: Consistency
> >>> Bug: Error
> >>> Bug: Regression
> >>> Bug: Security
> >>> Bug: Usability
> >>> Bug: conflict of two features (each works well independently)
> >>>
> >>> But it appears to lack a category for bugs in general. I am considering to create either “Bug:
> general”
> >> or “Bug”. If anyone opposes, please speak up.
> >>>
> >>>
> >
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

posts: 683 Canada

Maybe we should separate regression from the big type. We could have a radio: regression “unknown, yes, no, n/a”

Then we select what kind of bug it is, and in addition select if it’s known if it is a regression than it can be selected separately.

One consideration is that we already have a separate place where regression can be selected, and that’s when choosing the version.

Brendan

> On Jul 17, 2017, at 3:24 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-mffp.gouv.qc.ca> wrote:

>
> Hi Jonny,
> Heh, good point.
>
> I don’t know if #6394 is a regression.
>
> But #6401 can certainly be considered as a regression. Although one could argue the opposite since this new insertion screen did not exist before, so an instance can be configured to remain as reliable as before. I nearly mentioned in my last mail that the distinction between regressions and non-regressions is additionally not always clear-cut.
>
>> -----Message d’origine-----
>> De : Jonny Bradley mailto:jonny@tiki.org
>> Envoyé : 17 juillet 2017 15:17
>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>
>>
>> Aren’t they both regressions?
>>
>> jb
>>
>>
>>

>>> On 17 Jul 2017, at 19:48, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

>> mffp.gouv.qc.ca> wrote:
>>>
>>> Hi Brendan,
>>> https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are
>> examples.
>>> Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues
>> or conflict between 2 features.
>>>
>>>> -----Message d’origine-----
>>>> De : Dr. Sassafras mailto:drsassafras@gmail.com
>>>> Envoyé : 17 juillet 2017 13:43
>>>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>>>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>>>
>>>> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
>>>> would work?
>>>>
>>>> Brendan
>>>>
>>>>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant)

>> <Philippe.Cloutier.externe@mern-

>>>> mffp.gouv.qc.ca> wrote:
>>>>>
>>>>> Hi,
>>>>> Our issue tracker has the following categories for bugs:
>>>>> Bug: Consistency
>>>>> Bug: Error
>>>>> Bug: Regression
>>>>> Bug: Security
>>>>> Bug: Usability
>>>>> Bug: conflict of two features (each works well independently)
>>>>>
>>>>> But it appears to lack a category for bugs in general. I am considering to create either “Bug:
>> general”
>>>> or “Bug”. If anyone opposes, please speak up.
>>>>>
>>>>>
>>>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

posts: 3053 United Kingdom

No (sorry), I think it’s the pointless duplicate version numbers plus regression that should be removed, no idea why it’s thee in the first place.

The other bug type is a multiple select category field so doesn’t need a separate radio button field imho (what would be the advantage? And who would do data reprocessing? Not me I’m afraid ;)

jonny


> On 17 Jul 2017, at 22:28, Dr. Sassafras <drsassafras@gmail.com> wrote:
>
> Maybe we should separate regression from the big type. We could have a radio: regression “unknown, yes, no, n/a”
>
> Then we select what kind of bug it is, and in addition select if it’s known if it is a regression than it can be selected separately.
>
> One consideration is that we already have a separate place where regression can be selected, and that’s when choosing the version.
>
> Brendan
>

>> On Jul 17, 2017, at 3:24 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-mffp.gouv.qc.ca> wrote:

>>
>> Hi Jonny,
>> Heh, good point.
>>
>> I don’t know if #6394 is a regression.
>>
>> But #6401 can certainly be considered as a regression. Although one could argue the opposite since this new insertion screen did not exist before, so an instance can be configured to remain as reliable as before. I nearly mentioned in my last mail that the distinction between regressions and non-regressions is additionally not always clear-cut.
>>
>>> -----Message d’origine-----
>>> De : Jonny Bradley mailto:jonny@tiki.org
>>> Envoyé : 17 juillet 2017 15:17
>>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>>
>>>
>>> Aren’t they both regressions?
>>>
>>> jb
>>>
>>>
>>>

>>>> On 17 Jul 2017, at 19:48, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

>>> mffp.gouv.qc.ca> wrote:
>>>>
>>>> Hi Brendan,
>>>> https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are
>>> examples.
>>>> Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues
>>> or conflict between 2 features.
>>>>
>>>>> -----Message d’origine-----
>>>>> De : Dr. Sassafras mailto:drsassafras@gmail.com
>>>>> Envoyé : 17 juillet 2017 13:43
>>>>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>>>>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>>>>
>>>>> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
>>>>> would work?
>>>>>
>>>>> Brendan
>>>>>
>>>>>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant)

>>> <Philippe.Cloutier.externe@mern-

>>>>> mffp.gouv.qc.ca> wrote:
>>>>>>
>>>>>> Hi,
>>>>>> Our issue tracker has the following categories for bugs:
>>>>>> Bug: Consistency
>>>>>> Bug: Error
>>>>>> Bug: Regression
>>>>>> Bug: Security
>>>>>> Bug: Usability
>>>>>> Bug: conflict of two features (each works well independently)
>>>>>>
>>>>>> But it appears to lack a category for bugs in general. I am considering to create either “Bug:
>>> general”
>>>>> or “Bug”. If anyone opposes, please speak up.
>>>>>>
>>>>>>
>>>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world’s most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> TikiWiki-devel mailing list
>> TikiWiki-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

posts: 1751

Hi Jonny,


On 17.7.2017 23:39, Jonny Bradley wrote:
> No (sorry), I think it’s the pointless duplicate version numbers plus regression that should be removed, no idea why it’s thee in the first place.

wasn’t me but I think the idea was if known in which version the
regression happened to indicate that version.

luci


> The other bug type is a multiple select category field so doesn’t need a separate radio button field imho (what would be the advantage? And who would do data reprocessing? Not me I’m afraid ;)
>
> jonny
>
>
>> On 17 Jul 2017, at 22:28, Dr. Sassafras <drsassafras@gmail.com> wrote:
>>
>> Maybe we should separate regression from the big type. We could have a radio: regression “unknown, yes, no, n/a”
>>
>> Then we select what kind of bug it is, and in addition select if it’s known if it is a regression than it can be selected separately.
>>
>> One consideration is that we already have a separate place where regression can be selected, and that’s when choosing the version.
>>
>> Brendan
>>

>>> On Jul 17, 2017, at 3:24 PM, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-mffp.gouv.qc.ca> wrote:

>>>
>>> Hi Jonny,
>>> Heh, good point.
>>>
>>> I don’t know if #6394 is a regression.
>>>
>>> But #6401 can certainly be considered as a regression. Although one could argue the opposite since this new insertion screen did not exist before, so an instance can be configured to remain as reliable as before. I nearly mentioned in my last mail that the distinction between regressions and non-regressions is additionally not always clear-cut.
>>>
>>>> -----Message d’origine-----
>>>> De : Jonny Bradley mailto:jonny@tiki.org
>>>> Envoyé : 17 juillet 2017 15:17
>>>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>>>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>>>
>>>>
>>>> Aren’t they both regressions?
>>>>
>>>> jb
>>>>
>>>>
>>>>

>>>>> On 17 Jul 2017, at 19:48, Cloutier, Philippe (DGARI-Consultant) <Philippe.Cloutier.externe@mern-

>>>> mffp.gouv.qc.ca> wrote:
>>>>> Hi Brendan,
>>>>> https://dev.tiki.org/tiki-view_tracker_item.php?itemId=6394 and https://dev.tiki.org/item6401 are
>>>> examples.
>>>>> Clearly, not all bugs without errors are consistency bugs, regressions, security issues, usability issues
>>>> or conflict between 2 features.
>>>>>> -----Message d’origine-----
>>>>>> De : Dr. Sassafras mailto:drsassafras@gmail.com
>>>>>> Envoyé : 17 juillet 2017 13:43
>>>>>> À : Tiki developers <tikiwiki-devel@lists.sourceforge.net>
>>>>>> Objet : Re: Tiki-devel dev.tiki.org issue tracker: category for bugs
>>>>>>
>>>>>> Can you give an example of a bug that doesn’t fit into those categories? Perhaps another category
>>>>>> would work?
>>>>>>
>>>>>> Brendan
>>>>>>
>>>>>>> On Jul 17, 2017, at 1:32 PM, Cloutier, Philippe (DGARI-Consultant)

>>>> <Philippe.Cloutier.externe@mern-

>>>>>> mffp.gouv.qc.ca> wrote:
>>>>>>> Hi,
>>>>>>> Our issue tracker has the following categories for bugs:
>>>>>>> Bug: Consistency
>>>>>>> Bug: Error
>>>>>>> Bug: Regression
>>>>>>> Bug: Security
>>>>>>> Bug: Usability
>>>>>>> Bug: conflict of two features (each works well independently)
>>>>>>>
>>>>>>> But it appears to lack a category for bugs in general. I am considering to create either “Bug:
>>>> general”
>>>>>> or “Bug”. If anyone opposes, please speak up.
>>>>>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world’s most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> TikiWiki-devel mailing list
>>> TikiWiki-devel at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world’s most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> TikiWiki-devel mailing list
>> TikiWiki-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world’s most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
TikiWiki-devel mailing list
TikiWiki-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel


Why Register?

Register at tiki.org and you'll be able to use it at any *.tiki.org site, thanks to the InterTiki feature. A valid email address is required to receive site notifications and occasional newsletters. You can opt out of these items at any time.