|
From: Tom H. <to...@co...> - 2005-08-03 17:47:20
|
In message <200...@ja...>
sv...@va... wrote:
> + Bugzilla. It's unclear how to do this consistently. The approach
> + taken for 3.0.0 was to go to this page in KDE's bugzilla:
> + http://bugs.kde.org/query.cgi
> + and to create a search where
> + "Status and severity" / Status field is set to RESOLVED
> + and
> + "Involved People" / Email, bug-owner contains "jseward"
> + since I believe js...@ac... is the owner of all bugs.
> + This creates a long list of bugs which does not conveniently stop
> + at the previous release. Work backwards through this list until
> + either (1) you run out of patience, or (2) most of the bugs seem
> + to pertain to previous releases and are now irrelevant. In short
> + this is not a very scientific or robust way to collect up all
> + bugs fixed since last time.
They are all owned by you to start with, but they do sometimes get
transferred to other people. Setting product to "valgrind" should
be a better method.
You could probably also filter on the change date of the resolution
and/or status fields to narrow things down a bit more.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|