Modify

Opened 15 months ago

Closed 8 months ago

Last modified 8 months ago

#7467 closed defect (fixed)

Update plugins list in Trac

Reported by: Don-vip Owned by: stoecker
Priority: minor Component: Trac
Version: Keywords:
Cc:

Description

We should update the plugins list in Trac:

  • for all tickets referencing plugins that have been moved to core, affect them to core and delete these plugins from the list (remotecontrol, wms, validator...)
  • add missing plugins manually, or with another cron job ?

Attachments (0)

Change History (10)

comment:1 in reply to: ↑ description ; follow-up: Changed 15 months ago by skyper

Replying to Don-vip:

We should update the plugins list in Trac:

  • for all tickets referencing plugins that have been moved to core, affect them to core and delete these plugins from the list (remotecontrol, wms, validator...)

Using plugin for core components is silly but I like a grouping in core. E.g. remotecontrol and validator are still valid information and it is very handy for quick search.

  • add missing plugins manually, or with another cron job ?

We do this manually. It does not make much sense to have it in the list, as long as there are not tickets and you still have the "open" group plugin. We also need to know the trac user name of the maintainer or at least a valid email address.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 15 months ago by Don-vip

Replying to skyper:

Using plugin for core components is silly but I like a grouping in core. E.g. remotecontrol and validator are still valid information and it is very handy for quick search.

I understand, but I use very often "open core defects" report, and I miss this kind of tickets. We can use keywords for that, no ?

comment:3 in reply to: ↑ 2 Changed 15 months ago by skyper

Replying to Don-vip:

Replying to skyper:

Using plugin for core components is silly but I like a grouping in core. E.g. remotecontrol and validator are still valid information and it is very handy for quick search.

I understand, but I use very often "open core defects" report, and I miss this kind of tickets. We can use keywords for that, no ?

I guess we can. They are almost not used anyway.

stoecker's magic is behind the report page !

comment:4 Changed 15 months ago by stoecker

This request is not so easy to fulfill. Trac has no real support to get rid of old components. I already filled a ticket for this in the past.

comment:5 follow-up: Changed 15 months ago by skyper

A workaround would be to substitute "Plugin" with "Core" in the components name and list all tickets with "Core*" under "open core defects"

comment:6 in reply to: ↑ 5 Changed 15 months ago by skyper

Replying to skyper:

A workaround would be to substitute "Plugin" with "Core" in the components name and list all tickets with "Core*" under "open core defects"

@stoecker
Is there anything that speaks against renaming the components and listing all tickets with "Core" and "Core *" under report/12 for the moment ?

comment:7 follow-up: Changed 14 months ago by stoecker

As said, Trac does not support this. I would need to dig into the database directly and filter and change all entries. This is possible, but I do not yet know, if I really want to do so.

comment:8 in reply to: ↑ 7 Changed 14 months ago by Don-vip

Replying to stoecker:

Trac does not support this.

The wiki page http://trac.edgewall.org/wiki/TracAdmin mentions this command for trac-admin:

component rename <name> <newname>

    Rename a component

Is it not what we are looking for ?

comment:9 Changed 8 months ago by stoecker

  • Resolution set to fixed
  • Status changed from new to closed

comment:10 Changed 8 months ago by Don-vip

Thank you !

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.