Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Software

+ - Public Bug Tracking and Open-source Policy->

Submitted by Observer
Observer writes: Bugs in software are nothing new, but when they're discussed in the open, how do open source projects adapt policy? A major regression in the Gnome project's session manager has seen some major distributions choose to refuse to follow the update rather then drop a major feature. Between Gnome's public bug tracker those of distributions which released (and still distribute) the buggy version anyways, months of debate provide an interesting case-study in the way front-line users and developers interact for better or for worse. What lessons can be learned in release planning, bug triage, and marketing for a major open source project?
Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Public Bug Tracking and Open-source Policy

Comments Filter:

Real Programmers don't write in FORTRAN. FORTRAN is for pipe stress freaks and crystallography weenies. FORTRAN is for wimp engineers who wear white socks.

Working...