Hello Sage-Devel,
I just checked and there are now 47 tickets on trac that "need review":
http://trac.sagemath.org/sage_trac/report/10
I recently went through all the tickets on trac and got the number
that need review down to about 15-20. It's back up to 47.
I did this by:
1. bravely looking at each ticket and trying to figure out what it is about.
2. if it is trivial, I refereed it myself
3. In many cases, I emailed a few people I thought might be able to
referee the ticket, e.g., because of their comments on the ticket, or
because they popped up in related discussions on sage-devel.
4. In cases where I didn't really get what was going on, I would
basically ignore the ticket.
I then wrote this blog post:
http://sagemath.blogspot.com/2008/11/sage-patch-review.html
I really wish somebody would do 1-4 for those 47 tickets above today.
I can't because I have so many other things I have to do first. But
maybe one of you out there who has worked on sage development enough
to understand how the workflow works, could do the above. In the
worst case you'll find yourself in step 4 everytime, and nothing will
happen :-).
You don't even have to respond to commit. Just do something.
Thanks,
-- William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
