On Jun 9, 2010, at 9:19 AM, Dr. David Kirkby wrote:
On 06/ 9/10 04:58 PM, Robert Bradshaw wrote:
On Jun 9, 2010, at 7:29 AM, Dr. David Kirkby wrote:
I often find it annoying to be updating a standard package, only to
find someone else is working on the same package, and so two people
produce patches and two different spkg files with the same version
number.
I thought it would be useful if there was a way to indicate to other
Sage developers what packages you are working on. The Wiki seemed
like
the obvious place.
Does this page look useful? Could it be improved, or should it
just be
scrapped.
http://wiki.sagemath.org/spgs-soon-to-be-updated
I don't know if its possible to create a better system of linking
the
trac to the Wiki, as the method I used here will not put a line
through the trac ticket once it is closed.
Hmm... this is the kind of thing that should be easily searchable
from
trac. (That's the canonical place to go to see what else is being
worked
on at least.)
- Robert
Agreed, though it practice it is not so easy to do that. Take for
example
http://trac.sagemath.org/sage_trac/ticket/6705
about missing tuning parameters for sun4v processors. I submitted
that 10 months ago. Let's say I decide to fix that now. Nobody else
is likely to know I'm working on it - they would have to be
clairvoyant to know that.
Yep. I could guess from the ticket that you're updating the ATLAS
spkg, but spkg doesn't appear anywhere on the page so I couldn't
search for it (and at 10 months old, who knows how buried the results
would be). Perhaps it'd be worth a new field (spkg) and then we could
make a nice, easy report of tickets by spkg.
- Robert
--
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
