Mike Hansen wrote: > On Sun, Nov 22, 2009 at 9:24 PM, Dr. David Kirkby > <david.kir...@onetel.net> wrote: >> Well, we would need agreement on exactly what to have on the pull-down until >> I >> could do that. >> >> I assume the necessary code to add to the configuration file would be very >> similar to that used on Type, Milestone, Priority and Build, all of which are >> pulldown menus, where the user selects one from a number of choices offered. >> >> That said, I've never even looked at the configuration file. Perhaps you >> have, >> and can tell me its not as simple as I thought it would be. > > I just went ahead and added all the options you mentioned above to > trac. If people want them changed, then I can change them. Often, > it's easier just to do things if you want them done :-) > > --Mike >
Mike, Having made quite extensive use of this now (I believe 95% of my tickets now use it), I believe two options could usefully be added. to the current list of: 1) N/A - Not an upstream bug 2) Not yet reported upstream; Will do shortly. 3) Reported upstream. Little or no feedback. 4) Reported upstream. Developers acknowledge bug. 5) Reported upstream. Developers deny it's a bug. 6) Fixed upstream, in a later stable release. 7) Fixed upstream, but not in a stable release. 8) Workaround found; Bug reported upstream. 9) Completely fixed; Fix reported upstream 10) None of the above - read trac for reasoning. These would be * Needs reporting, but I don't know where to report. (insert between 1 and 2) above * Useful feedback, but not fully resolved. (insert between 3 and 4). I feel a bit guilty when an upstream developer has tried quite hard to fix a problem, but the Sage ticket shows "Little or no feedback". Currently the issue with PolyBoRi not building with Sun's compiler is in this category, despite the fact that Alexander Dreyer has made quite an effort to resolve it. Is there a way I can search for specific ones of these? I'd particularly like to find any where I myself have "Not yet reported upstream; Will do shortly." I'm sure a search of those and "Needs reporting, but I don't know where to report" could be quite useful to William. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
