New trac report
Jason Grout
It lists all open tickets in which the current logged-in user
participated (i.e., any ticket you changed), grouped by component.
http://trac.sagemath.org/sage_trac/report/21
Hopefully this finds tickets that you may have commented on, but lost
track of.
Jason
--
Jason Grout
William Stein
This is great. It now makes me want a report on "tickets that I
participated in that say [with patch; needs review]". That would be
the perfect report on what I should referee (except for the tickets
that are by me).
William
kcrisman
(And now Jason can use this to close the ticket which requests it,
http://trac.sagemath.org/sage_trac/ticket/3951, which he participated
in by creating it.)
- kcrisman
On Sep 29, 3:43 am, William Stein <wst...@gmail.com> wrote:
> On Tue, Sep 29, 2009 at 12:25 AM, Jason Grout
>
Minh Nguyen
On Wed, Sep 30, 2009 at 1:04 AM, kcrisman <kcri...@gmail.com> wrote:
>
> Finally! Thank you.
>
> (And now Jason can use this to close the ticket which requests it,
> http://trac.sagemath.org/sage_trac/ticket/3951, which he participated
> in by creating it.)
Ticket #3951 [1] is now closed as fixed. The relevant trac report
works only if you login to trac first.
[1] http://trac.sagemath.org/sage_trac/ticket/3951
--
Regards
Minh Van Nguyen
Jason Grout
This would be much easier to do if we codified the stages of a ticket
using a "status" trac field or something. mhansen had a prototype when
he first set up trac 0.11. I don't know where the prototype went.
A suggestion for a workflow based on the Drupal ticket system is here:
As a plus, people wouldn't have to worry about misspelling "needs
review" dropping a ticket off the report.
Jason
--
Jason Grout
Jason Grout
>
> A suggestion for a workflow based on the Drupal ticket system is here:
>
> http://groups.google.com/group/sage-devel/browse_thread/thread/d794dcc6f98c17fe/356342ea14f6d265?q=drupal+group:sage-devel#356342ea14f6d265
To elaborate, here are some stages that our patches seem to go through:
* active
* active (needs more info)
* patch (needs work)
* patch (needs documentation/testing work) -- this is for doctest
fixing, adding doctests, or documentation that needs to be fixed (e.g.,
improper rest structure)
* patch (needs review)
* patch (positive review)
* fixed
* duplicate
* invalid
* bydesign
In split out code work and documentation work, since it seems that
documentation work often can be done by someone who may or may not
understand the code deeply.
And here are instructions for modifying trac.ini to implement something
like this:
http://trac.edgewall.org/wiki/TracWorkflow
Jason
--
Jason Grout