Re: Bug tracker?

Stephen> Hans de Graaff writes: Stephen> SF Tracker is what Python decided was so unbearable that they Stephen> decided *anything* would be better. Having decided that, they Stephen> went to work on beating Roundup into shape, that being what Stephen> they got the most serious volunteers to work on. True, but for better or for worse SF served the Python community's needs for several years. You could have a reasonable (not perfect, not horrible) tracker in use today if you wanted. Martin v. Loewis indicated that Python's Roundup schema was heavily influenced by the SF schema: ... the schema was heavily influenced by the SF schema - so if you migrate from SF, using the bugs.python.org schema might be a good idea. Otherwise, I cannot see it as better or worse than the classic schema. Stephen> - Urgency is not a user or developer variable, and should be Stephen> suppressed unless there's a manager with authority to decide such Stephen> things. SF suffers from this as well. No matter how many times we asked people to not diddle the priority field someone would invariably submit a bug report for something pretty trivial right before a Python release was due to go out the door and mark it high priority. That would cause the release train to briefly grind to a halt as a number of people stopped what they were doing to check it out. The submitter should generally not be able to set the urgency of a bug report. That's for whoever is performing triage at the time. Skip _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta