Hi Lee,

I had this idea after looking at RoR trac, they have some useful custom
report, like pending patches:

http://dev.rubyonrails.org/report/3

it seems as they simlpy change the ticket summary adding a [PATCH]
prefix when the ticket gets a patch.

Using keywords as you suggested seems to be the right thing to do.

Some days ago I've looked at how to do trac custom reports:

http://trac.turbogears.org/turbogears/wiki/TracReports

I can't find a way to do it from the web, this probably need access to
the trac configuration and most probably only Kevin has this ATM.

Ciao
Michele

PS#2
I think we also need a small TurboGearsTracGuideLines with contents
like these:
- naming conventions for wiki pages (HowTo..., Tutorial...)
- useful formatting tips&tricks (python and html syntax coloring)
- keywords for tickets
- how to add a new faq
- adding your page to the DocumentationPlayground
I think this should be linked from the trac start page and could really
be helpful.

Lee McFadden wrote:
> An easy way to impliment this would be using the keywords field.
> afaik there is no way to tell if an attachment is a patch, image,
> binary, etc.
>
> I propose we use some standard keywords, e.g.
>
>  tg|has_patch
>  tg|patch_tested
>  tg|to_commit
>
> etc.
>
> That way custom reports can be set up with ease searching simply on
> the keywords.  These keywords are just examples, and could/should be
> changed to fit our needs.
>
> Does this sound like a good idea?
>
> Lee
>
>
>
> On 21/11/05, Michele Cella <[EMAIL PROTECTED]> wrote:
> >
> > Regarding Kid, I've also made a trivial patch for TG ticket 59.
> >
> > http://trac.turbogears.org/turbogears/ticket/59
> >
> > Ciao
> > Michele
> >
> > PS
> > I think we should setup a custom trac report to show pending patches.
> >
> > David Stanek wrote:
> > > I have posted a patch to the kid trac
> > > http://lesscode.org/projects/kid/ticket/66. This fixes the issue where
> > > having a comment in a template that extends another causes a failure.
> > >
> > > Related tickets:
> > > Kid: http://lesscode.org/projects/kid/ticket/66
> > > TurboGears: http://trac.turbogears.org/turbogears/ticket/71
> > >
> > > If you try the patch let me know how it works for you. Tomorrow morning 
> > > I'll
> > > see if I can post a blog entry describing the problem.
> > >
> > > -- David
> >
> >

Reply via email to