On Jun 12, 2010, at 1:47 AM, David Kirkby wrote:
On 12 June 2010 00:58, Robert Bradshaw
<rober...@math.washington.edu> wrote:
On Jun 9, 2010, at 1:44 PM, Dr. David Kirkby wrote:
On 06/ 9/10 08:39 PM, leif wrote:
A drop-down box like "component", without the version number?
I can see the point of that. Being able to search by component
would be
useful.
+1 to that from me.
But it's not obvious to me how this will help find what people are
working
on, so avoiding clashes of patches and two people creating tickets
of the
same version number.
Ideally there needs to be a way of searching for tickets based on a
particular .spkg, which people are actively working on, rather
than issues
reported long ago, that nobody is looking at
http://trac.sagemath.org/sage_trac/ticket/1169
is an NTL related ticket that has not been touched for 19 months.
I doubt I would have any need to worry about that if I were
updating NTL
now. So how would I find tickets where people are actively working
on them?
Well, personally I would use my judgement based on the activity of
any
relevant tickets, pinging the person who opened (or last edited)
the ticket
if needed. Not perfect, but there are few enough people working on
any given
spkg at any given time that this should be sufficient.
- Robert
That may be practical when there is a pull-down and one can select
from the individual standard packages.
We're just waiting for someone with the time and trac knowhow to add
the field, as everyone seems to like the idea.
At the moment, it is very hard
to do. Very often, a bug is reported and nobody knows how to solve it,
so the package does not even get put in the title, so its hard to find
them.
I'm not imagining the spkg field would always be filled out at the
time of filing the bug (though it could be). Often, when someone went
to try to fix the bug, then it would be apparent what spkg was
involved, and this would be even more useful as the purpose is to be
able to see whether there is potential conflict with someone else
actively working on an spkg.
I've currently got a what (excluding comments) is a 3-line fix to
python awaiting review. (It looks huge, the fact I've had to copy a
new file python file and make a diff from that too.). There is a
fairly good chance that will need re basing soon, given pyton is
already at patch level 8 and it was not that long that a new upstream
release was added.
http://trac.sagemath.org/sage_trac/ticket/9041
for anyone that would want to look at what is a short patch in fact.
Looks like it's got a positive review to me, so hopefully this can get
in soon :)
- 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
