As far as I know, there is no documentation about how we're supposed to be using the Open/Closed and Planned Release fields in Savannah.
Ingo closes bugs whose status he sets to Invalid, but that's not the case I'm interested in. I'd like to propose that: 1. A Fixed bug be Closed immediately[1] if it was only ever extant in git, and not in an actual release (not counting release candidates). 2. The Planned Release field be used and set to the forthcoming release for Fixed bugs that were extant in the most recent actual release. 3. That the Owner of a Fixed bug in a Planned Release Close the bug when that Planned Release is actually released. My rationales are: A. I am owner of a bunch of fixed groff bugs in Savannah and I'd like to tidy them up in some respect. B. From repeated personal negative experiences, I have come to hate it when a project slams a bug closed as soon as a commit fixing it is made, no matter how many months or years may pass before a release is made. If the bug exists in the latest release version of a software project, that bug should be easy to find. This also helps prevent the filing of duplicate reports. C. This keeps the cost of experimentation low on git HEAD. There's no reason to wear our (my[2]) shame on the bug tracker for screwups that never made it into an actual release. Getting yelled at on the mailing list is a good enough deterrent. Thoughts? [1] Meaning: as soon as the commit is pushed, or reasonably soon thereafter, or as soon as someone notices this is the case. [2] :) -- Regards, Branden
signature.asc
Description: PGP signature
