| |||||||||||||
|
| |||||||||||||
Bug trackers and kernel developmentBug trackers and kernel developmentPosted Jul 17, 2003 16:46 UTC (Thu) by cpeterso (subscriber, #305)In reply to: Bug trackers and kernel development by hp Parent article: Bug trackers and kernel development btw, I have reported a few bugs in the FreeBSD bug database. They were all fixed or proven to be "by design" behaviour within a couple weeks. My GNOME bugs have received no attention what so ever for the past six months. JWZ describes his experience reporting GNOME bugs as follows (http://www.livejournal.com/users/jwz/154529.html): Today a bunch of the outstanding bugs I'd reported to the Gnome propellerheads in the last couple of years were closed as follows: Because of the release of GNOME 2.0 and 2.2, and the lack of interest in maintainership of GNOME 1.4, the gnome-core product is being closed. If y0u feel your bug is still of relevance to GNOME 2, please reopen it and refile it against a more appropriate component. Thanks... This is, I think, the most common way for my bug reports to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch -- and the new maintainer can't be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version. I'm so totally impressed at this Way New Development Paradigm. Let's call it the "cascade of attention-deficit teenagers" model.
(Log in to post comments)
Bug trackers and kernel development Posted Jul 17, 2003 16:59 UTC (Thu) by hp (subscriber, #5220) [Link] jwz whines a lot. All his issues have been fixed, just not backported to GNOME 1.4. No volunteers or companies have shown interest in still supporting 1.4, so it isn't happening. Equivalent of expecting kernel 2.6 features in kernel 2.0.
|
|
||||||||||||