[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Bugs against the Essen branch
From: Inge Wallin <inge () lysator ! liu ! se>
Date: 2010-09-23 8:34:14
Message-ID: 201009231034.15333.inge () lysator ! liu ! se
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Recently the Nokia testers have started to report bugs against the Essen
branch. This is part of the Nokia effort to open up the development process
and put it more into the open, something I think we should be grateful for.
However, this hasn't been well received everywhere. Thomas has moved the
resolution of these bugs to WAIT [1] and asking that the testing be done
against trunk instead. He writes:
"Please test against the main branch and not an unstable
feature branch thats not supported by the KOffice core team.
Feel free to reopen if the bug exists in the main branch. "
I can see his point, but I thought that I would ask the rest of the community
about this. Here are the facts:
- Nokia is going to test the Essen branch since that is what is being used
for their releases. Once trunk is open for features again, this will move back
to trunk.
- Most bugs exist in both the branch and trunk. Some (a few?) bugs only exist
in branch, of course.
So, I can see these alternatives:
1. Nokia is allowed to report bugs against the branch.
2. Nokia is not allowed to report bugs and will move back to the internal
Maemo.org bugzilla.
In case 1, there will be a few bugs that cannot be reproduced in trunk. That
is a cost, but in my mind not very high. In return we will get a lot of bugs
reported that would otherwise go unnoticed by us.
In case 2, we will save some work (won't have to check the bugs against trunk)
but we miss out on a lot of bugs. It will also mean a setback to the opening
up process.
So, what do you think? My own opinion is that alternative 1 is better and that
it's not very difficult to ignore the bugs that are against the branch if you
don't like them. After the freeze is lifted, they will be moved to trunk
anyway, or closed if the bug in question doesn't exist any more.
-Inge
[1]
https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr& \
short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr& \
bug_file_loc=&keywords_type=allwords&keywords=&resolution=WAITINGFORINFO&emailassigned \
_to1=1&emailreporter1=1&emailtype1=exact&email1=swathi.vegesna@wipro.com&emailtype2=su \
bstring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+so
[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:'Abyssinica SIL'; 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;">Recently the Nokia testers have started to report bugs against the \
Essen branch. This is part of the Nokia effort to open up the development process \
and put it more into the open, something I think we should be grateful for.</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;">However, this hasn't been \
well received everywhere. Thomas has moved the resolution of these bugs to WAIT [1] \
and asking that the testing be done against trunk instead. He writes:</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 \
name="comment_text_6"></a><span style=" font-family:'Courier \
New,courier';">"P</span><span style=" font-family:'Courier New,courier';">lease \
test against the main branch and not an unstable</span></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;"><span style=" \
font-family:'Courier New,courier';">feature branch thats not supported by the KOffice \
core team.</span></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;"><span \
style=" font-family:'Courier New,courier';">Feel free to reopen if the bug exists in \
the main branch. "</span></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; font-family:'Courier \
New,courier';"></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 can see \
his point, but I thought that I would ask the rest of the community about this. Here \
are the facts: </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;"> - Nokia is \
going to test the Essen branch since that is what is being used for their releases. \
Once trunk is open for features again, this will move back to trunk.</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;"> - Most bugs exist in both \
the branch and trunk. Some (a few?) bugs only exist in branch, of course.</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;">So, I can see these \
alternatives:</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;">1. Nokia is allowed to report bugs against the \
branch. </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;">2. Nokia is \
not allowed to report bugs and will move back to the internal Maemo.org bugzilla.</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;">In case 1, there will be a few bugs that cannot be reproduced in \
trunk. That is a cost, but in my mind not very high. In return we will get a lot of \
bugs reported that would otherwise go unnoticed by us.</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;">In case 2, we will save some \
work (won't have to check the bugs against trunk) but we miss out on a lot of bugs. \
It will also mean a setback to the opening up process.</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;">So, what do you think? My own \
opinion is that alternative 1 is better and that it's not very difficult to ignore \
the bugs that are against the branch if you don't like them. After the freeze is \
lifted, they will be moved to trunk anyway, or closed if the bug in question doesn't \
exist any more.</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;"> -Inge</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;">[1] <a \
href="https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwo \
rdssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_fil \
e_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&a \
mp;resolution=WAITINGFORINFO&emailassigned_to1=1&emailreporter1=1&emailtyp \
e1=exact&email1=swathi.vegesna@wipro.com&emailtype2=substring&email2=& \
bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+so"><span \
style=" text-decoration: underline; \
color:#0000ff;">https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_ \
type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&a \
mp;bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&k \
eywords=&resolution=WAITINGFORINFO&emailassigned_to1=1&emailreporter1=1&am \
p;emailtype1=exact&email1=swathi.vegesna@wipro.com&emailtype2=substring&em \
ail2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now& \
amp;chfieldvalue=&cmdtype=doit&order=Reuse+same+so</span></a></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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic