Konqueror bugs - a few questions

["Gérard Talbot"]

> Hi all,
>
> you might have seen the recent flood of closed bugs in your inbox (or
> on konqueror-bugs at kde.org if you don't look at that folder too often).
> I briefly talked to David Faure today in #:kde-devel and he agreed
> that it is of not much use to keep old KDE3 bugs open since it is not
> actively maintained anymore.
>
> So just in case you are worried about what is going on: I am cleaning
> up a bit :)
>
> For the future:
>
> - I intend to go through old reports and since distributions don't
> ship anything older than KDE version 4.5 it would make sense to close
> those and ask people to reopen if they can reproduce the issue with
> version 4.8.4 or newer. Please tell me if this seems too early.


I would be for closing anything that is older than KDE 4.7 . So, KDE
version 4.5 is not too early to me, as far as I'm concerned.


> - Please use the commit hooks BUG:, CCBUG: and FIXED-IN: in your
> commits, this allows to not only close the report and avoid some
> manual cleaning but also allows to provide continuous information on
> bug handling with the CCBUG: hook so people don't feel like nothing is
> happening. A commit link will be automatically added to the report.
>
> - When the bug is reproducible

By the way, the word "reproducible" as a keyword
https://bugs.kde.org/describekeywords.cgi
does not exist. It's "reproduceable". Since a lot of us use reproducible,
I wish both keyword spellings would be allowed.


> with a more recent version, please
> change the version field to reflect that status.

If we do that, the bug reporter may feel that we ignore for how long the
bug has been lingering on and on...


> Since you neither
> maintain several branches nor backport changes to older versions than
> the current SC release it is not useful to keep the version field
> inaccurate. It also allows to filter bug reports much easier.
>
> - As a rule: please don't forget the reports you set as NEEDSINFO,
> that status should not be used as a garbage bin for bugs reports.
> Without feedback those should be close in a regular manner, also
> something you can ask us to do for you.
>
> Please tell me if you need component or version changes done on
> Bugzilla, I am usually around in CET and rather an owl when it comes
> to sleeping time.
>
> There also is the possibility to set up reminders for release blocker,
> regressions etc., to be sent to this list or to one or several
> individuals, please ask if you need this set up, you can have it from
> once a day to a weekly, bi-weekly, monthly up to a yearly schedule,
> your choice :)
>
> Regards, Myriam


Myriam,

I once sent you an email wrt your
"When is a bug report useful?"
http://blogs.fsfe.org/myriam/archives/415
but I think you never received it.

Gérard
-- 
Konqueror Implementation Report of CSS 2.1 test suite (RC6): 9418 testcases
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/Konq-IR-CSS21TestSuite.html
55 Bugs in Konqueror 4.7
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/
Contributions to the CSS 2.1 test suite
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/
CSS 2.1 Test suite RC6, March 23rd 2011
http://test.csswg.org/suites/css2.1/20110323/html4/toc.html