Jason Grout wrote: > Dr. David Kirkby wrote: >> It's clear that Sage, unlike most other projects, makes extensive use of >> software not written by Sage developers. As such, when bugs are found in >> that >> software, they should ideally be reported upstream. >> >> I would suggest a pull-down on the track where one could select from >> >> 1) N/A - Not an upstream bug. >> 2) Not yet reported upstream, but should be. >> 3) Reported upstream. >> 4) Fixed upstream > > > +1 from me too. I've dealt with a few patches going upstream, and I can > see how it would be really nice to have a way of notating it in our trac. > > We might also have an option for "fixed in our version", as many times > we will patch an spkg and simultaneously report it upstream. When we > eventually get the upstream fix in an update, we delete our patch. > > Jason > > -- > Jason Grout
Yes, I did consider whether there should be something like a 'fixed in our version'. I recently found a fix for a gnults library bug, and reported the fix upstream. They agreed there was a problem, but intend coming up with a better solution than mine. My solution involved specifying ./configure LIBS=-lnsl but the upstream developers want to avoid that, believing the configure script should work out what libraries are needed, and not have to be told. Sometimes there is a bit of overlap. There seems to be a universal agreement it is worth implementing (about 4 people agreeing, and nobody disagreeing.) Perhaps the exact number of entries, and the exact wording needs a bit of thought. I'm not sure how much space there is available either. Most of the trac items have only one word. The longest is the 'Milestone' and that is much shorter than what I proposed, and what has been suggested. There might be an argument for * Not reported; Will fix myself, then report upstream. Anyway, there are some ideas. All we need to do is sort out the details! 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 -~----------~----~----~----~------~----~------~--~---
