Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Bug reports should be closed when they don't need any more attention. When reporting bugs, ideally people would also search closed reports to see if the issue has ever been reported or if there has been any work or discussion related to this issue. "Closed" should not be a synonym for "Complete". There is a separate pull- down menu for that, with states like "Accepted" for patches and "Fixed" for bugs.
A bug that is "Closed" can not be(come) "Fixed" anymore.
hmm, technically it can (on the sf tracker); but i guess you are rather referring to the social aspects of it.
i agree with hans, that people reporting bugs should also look whether there bug has already been reported, and eventually been closed (and find out why the issue has been closed)
of course this does not solve the problem of two branches containing different bugfixes.
i guess it would be good practice to add a note when someone is closing an ticket when a bug has been fixed only in a certain branch.
furthermore, if release cycles were shorter (PdX-0.40 is now pending for more than one month) the problem would become less noticeable. (but of course there are only so many hours per day...)
finally this is probably a good example why Pd-extended should be split into a lot of small packages with there own release cycles. there is really no need for a [hid]-bugfix to wait for [hexloader] to be fixed in order to get propagated back into the main-trunk.
but then, other meta-packages (e.g. linux-distros like debian) have this problem too, but it is somewhat alleviated by the fact that the debian-maintainers are not necessarily involved in upstream-maintainance (which i think is the main problem here; most other devs but hans would probably have fixed the bug in the main trunk rather than some branch; but he is quite free to do so; i cannot complain that the bugfix is non-existant on the latest-and-greatest CVS head...)
fgamsdr IOhannes