[Trac-tickets] [The Trac Project] #1547: Define QA owner for a
component
The Trac Project
noreply at edgewall.com
Fri May 13 09:30:33 EDT 2005
#1547: Define QA owner for a component
------------------------+---------------------------------------------------
Id: 1547 | Status: new
Component: trac-admin | Modified: Fri May 13 09:30:32 2005
Severity: normal | Milestone: 0.9
Priority: normal | Version: 0.8
Owner: cmlenz | Reporter: 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/db}}}''{{{X}}}''{{{.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)''
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1547>
The Trac Project <>
More information about the Trac-Tickets
mailing list