Define QA owner for a component

[pkou at ua.fm]

Implementation of customized workflow (see NewWorkflow) requires that a component has two owners: developer-owner and QA-owner.

This feature requires database changes. If the database upgrade is performed in a patch, it is very hard to track changes and upgrade projects with new version of Trac.

On the other hand, this feature does not make any impact on existing system.

Thus, it is necessary to implement the change in mainstream for simplifying further development on customized workflow.

Necessary changes:

• trac/db_default.py: add column qaowner to table component. Modify default database data;
• trac/upgrades/dbX.py: An upgrade script that sets qaowner equals to currnet owner during the upgrade;
• trac/admin/scripts.py: Extend commands for component modification:
  • component add <name> <owner> [<qaowner>]: Set qaowner if specified. Set qaowner equals to owner if omitted.
  • component chown <name> <owner> [<qaowner>]: Change qaowner if specified. Set qaowner equals to owner if omitted.

(In preparation for #869)

[pkou at ua.fm]

Would you agree with this change for 0.9?

[pkou at ua.fm]

Patch for the changes

[pkou at ua.fm]

Patch attached.

While working on the patch: Milestone owner has been removed in [1169] because of #786. Why? This creates another minor problem for customized workflows. Need to think how it will look without milestone owner.

[Christopher Lenz]

What do you mean with "milestone owner has been removed"? We never had owners for milestones AFAIK.

[pkou at ua.fm]

Oops! Just entangled with all my patches. Sorry :) (Do we have a possibility to edit/remove comments? :)
Milestone owner has been introduced with my first patch for NewWorkflow.

[Christopher Lenz]

Okay, I'd rather not check in this change separately as it'd just add unused code/db column. Let's just keep it together with the NewWorkflow patch (#869), okay?

[Christian Boos]

(clearing report:35)