<div class="gmail_quote">On Mon, Nov 16, 2009 at 12:51 AM, Andreas Pakulat <span dir="ltr"><<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
with the feature freeze being close we need to find a good strategy for<br>
the bugfixing phase so we're sure to address the most important/annoying<br>
bugs.<br>
<br>
To start with that I went through the open bugreports against kdevelop<br>
(will do kdevplatform in the next days) and reviewed them. I've tagged<br>
all that _I_ think should be done for 4.0 with the proper target<br>
release. Additionally I've tried to set priority to HI or VHI depending<br>
on how big the impact on users is (or if we already seen it ourselves).<br>
I've also tagged and prioritized some that simply need the "responsible"<br>
developer to have a second look to judge about it.<br>
<br>
I suggest that once everybody has his features done (or at 25th)<br>
everybody looks at the list of bugs in bugzilla using this query:<br>
<br>
<a href="https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdevelop&product=kdevplatform&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=" target="_blank">https://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=kdevelop&product=kdevplatform&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=critical&bug_severity=grave&bug_severity=major&bug_severity=crash&bug_severity=normal&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=</a><br>

<br>
Of course we can also discuss about moving some out of the "to-be-fixed"<br>
list. IMHO everything with priority VHI needs to be fixed before we can<br>
do a release, ultimately delaying it (if not done by the date RC1 is<br>
tagged). HI priority for me means I'll try very hard to fix these,<br>
but they won't block the release. Everything below that is simply<br>
nice-to-have.<br>
<br>
Andreas<br>
<br>
--<br>
Caution: breathing may be hazardous to your health.<br>
<font color="#888888"><br>
--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</font></blockquote></div><br>Good thing to have!<br>
I always have trouble to look for bugs in bugzilla :)<br>
<br>
Thanks,<br>
Aleix<br>