Re: New release of GTK+ libraries (1.3.5)

Jamie Strachan <frostfreek yahoo com> writes:

> At the risk of sounding like a manager,
> Shouldn't the list of bugs at bugzilla be updated when a new release is generated?
> There are plenty of bug reports under 2.0.0 and 2.0 API Freeze that are
> fixed, obsoleted, or patched, but still listed as NEW
> If you need volunteers to go through the buglist and indicate which bugs
> have been fixed or are now obsolete, I would be glad to help out.

To the best of our knowledge, every open bug for GTK+ represents
an active issue. Now, it could certainly be that a few resolved
bugs have slipped through the cracks, but I'd be quite suprised
if that number was more than 10 or so. 

Sometimes bugs are not closed because the issues they are about
have only partially been fixed, and there is still remaining
work to do on the issue.

Some of us spend considable amounts of our time staring at the 
GTK+/Pango/GLib bug list. Rest assured, if there were lots of
obvious bugs that could be closed, we'd have closed them.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]