Component filter for the Timeline

[fog@…]

The two attaches patches (to files Timeline.py and timeline.cs) implement Component filtering for the Timeline. Two new configuration options are defined in the [timeline] group:

• display_components shows the component name for tickets and commits just before the "by XXX" text; and

• changeset_guess_component assign to a checkin a component based on the first path element in the SVN repository (this only works for repositories used to host multiple projects. This configuration option is used only if changeset_show_files is set, because needs at least one file name to work on.

An example of the resulting Timeline can be seen on the ​initd.org website (both options activated.)

[fog@…]

version 2 of the patch (replaces 2 previous files)

[fog@…]

I attached a new version of the patch that implements:

• svn repository filtering (re-based, in both Browse and Timeline you only get the branches you asked for;
• component filtering in the Timeline;
• generation of component names for the svn changesets (automatically guessed or re-based)

This patch introduces two new options in the [trac] group (for a total of 4 new options). The 2 new options are:

repository_filter -- assign a regular expression to it to filter your SVN repository
repository_component -- assign to it a regular expression that matches at least one group to assign the first group as component name to the changeset (this option does nothing if changeset_guess_component is 0)

This is an example of the configuration we're using to make only the psycopg-related stuff from our SVN repo appear in the psycopg Trac:

repository_filter = ^/?(psycopg1|psycopg2|dbapi-programming)
repository_component = ^/?(psycopg1|psycopg2|dbapi-programming)
changeset_guess_component = 1
display_components = 1

Note that this new patch will guess the changeset component (if display_components is 1) even if changeset_show_files is 0 (I removed that limitation of the first version.

Also note that the new re-based component guessing allows for asigning components to projects orgainized as trunk/component1, trunk/component2, ..., branches/component1, etc.

It is working well for us, see the ​psycopg Trac.

[fog@…]

This last version of the patch uses the last group of the regular expression to assign to component name to the changeset. It allows for regular expressions like "^{/?(trunk|tags|branches)/(.*?)/" do what expected.}

[fog@…]

Version 3 of the patch

[cboos]

Also see #1678.

[cboos]

(changing the status, as I've not actually started to work on that yet)

[cboos]

#2374 has been marked as a duplicated of this proposal.

[cboos]

woops, I meant 1.0

[cboos]

Milestone 1.0 deleted