'Tester's bugs: NEW or UNCONFIRMED'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Tester's bugs: NEW or UNCONFIRMED
From:       Inge Wallin <inge () lysator ! liu ! se>
Date:       2010-07-26 10:54:34
Message-ID: 201007261254.34318.inge () lysator ! liu ! se
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

For a long time, it has been the case that when people with accounts on 
bugs.kde.org reports a bug the default status of the new bug is NEW.  When an 
anonymous (non-account holder) person reports a bug the status gets set to 
UNCONFIRMED by default.  The idea is that probably a person without an account 
is not as knowledgeable as an account holder, since these have always 
comprised developers only.

Since a few weeks we have a new category of BKO account holders: the testers.  
I don't know many KDE projects that have professional testers on board, but 
KOffice is lucky enough to do now.  See for instance the introduction done by 
Nandita Suri on the 14th this month.

Now we have a situation that I think we should discuss in the community.  
Since the testers are account holders, their bugs get the status NEW by 
default. This is not popular among everybody, see for instance these bugs:

https://bugs.kde.org/show_bug.cgi?id=244843
https://bugs.kde.org/show_bug.cgi?id=245448
https://bugs.kde.org/show_bug.cgi?id=244851

I would like to have this issue cleared up.  My own opinion is that the 
testers have a good understanding of what is a bug or not and should have 
their bugs set to NEW immediately. I understand that it may be difficult to 
understand exactly which component a bug belongs to, and that it sometimes 
needs to be moved.  

I would like to have the whole KOffice community agree on a way to treat bugs 
and establish a process for them.  A long time ago, we agreed that missing ODF 
features are indeed bugs and should not be closed.  I don't think we finished 
the discussion about the rules at that time and that we should do that now.

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" \
content="1" /><style type="text/css"> p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Arial'; font-size:11pt; font-weight:400; \
font-style:normal;"> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">For a long \
time, it has been the case that when people with accounts on bugs.kde.org reports a \
bug the default status of the new bug is NEW.  When an anonymous (non-account holder) \
person reports a bug the status gets set to UNCONFIRMED by default.  The idea is that \
probably a person without an account is not as knowledgeable as an account holder, \
since these have always comprised developers only.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Since a few weeks we have a \
new category of BKO account holders: the testers.  I don't know many KDE projects \
that have professional testers on board, but KOffice is lucky enough to do now.  See \
for instance the introduction done by Nandita Suri on the 14th this month.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Now we have a situation that \
I think we should discuss in the community.  Since the testers are account holders, \
their bugs get the status NEW by default. This is not popular among everybody, see \
for instance these bugs:</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"><a \
href="https://bugs.kde.org/show_bug.cgi?id=244843"><span style=" text-decoration: \
underline; color:#0000ff;">https://bugs.kde.org/show_bug.cgi?id=244843</span></a></p> \
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><a \
href="https://bugs.kde.org/show_bug.cgi?id=245448"><span style=" text-decoration: \
underline; color:#0000ff;">https://bugs.kde.org/show_bug.cgi?id=245448</span></a></p> \
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><a \
href="https://bugs.kde.org/show_bug.cgi?id=244851"><span style=" text-decoration: \
underline; color:#0000ff;">https://bugs.kde.org/show_bug.cgi?id=244851</span></a></p> \
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">I would like to have this issue cleared up.  My own opinion is \
that the testers have a good understanding of what is a bug or not and should have \
their bugs set to NEW immediately. I understand that it may be difficult to \
understand exactly which component a bug belongs to, and that it sometimes needs to \
be moved.  </p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">I would like to have the whole KOffice community \
agree on a way to treat bugs and establish a process for them.  A long time ago, we \
agreed that missing ODF features are indeed bugs and should not be closed.  I don't \
think we finished the discussion about the rules at that time and that we should do \
that now.</p></body></html>

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

[prev in list] [next in list] [prev in thread] [next in thread] 