[Dev] Tracking with Bugzilla (2) - vote on component list

[Katie Capps Parlante]

Philippe Bossut wrote:
> Hi,
> 
> Following up on yesterday's e-mail and meetings with Heikki, Aparna and 
> the whole App team, I updated the doc:
>    http://wiki.osafoundation.org/bin/view/Chandler/BugzillaTracking
> 
> Notes:
> - The components list in the doc is a new proposal (read the paragraph 
> above) and need the App team and stake holders approval before being 
> implemented: please, vote on this proposal before within 24 hours. This 
> concerns only the App dev team (I'm not planning to change the other 
> components like Repository and of course, nothing outside Chandler 
> proper) and QA (Heikki, Aparna). Feel free to chime in if you have some 
> opinion though. Since I'm calling for the vote, I know I'll have to do 
> the implementation and I indeed checked that I do have the privileges to 
> do those changes.
> - Since I got no push back on them, I went ahead and added the proposed 
> keywords to Bugzilla
> - In particular, the "task" keyword is there so, even if the 
> "components" are not there yet, you (App devs) can technically move 
> forward and log task records (use the best component available, we'll do 
> a reassign later)
> - Still need to be done in the doc:
>    - add a paragraph on the use of dependent and blocking bugs
>    - add a paragraph on the use of target milestones
> 

One comment about the swags -- other groups/projects have been using 
wiki tables to track tasks, and have a swag column as well. The 
convention for the swag value has been:

    small => a few days
    med => 1-2 weeks
    large => ~1 month

These values were meant to swag task times at the beginning of a 
project, before enough detailed work was done to build a detailed 
schedule. I know that the apps team is trying to break things down into 
smaller tasks to do better estimates. Also, we presumably want these to 
apply to bugs as well as tasks.

You are proposing:

     * [SWAG : Trivial] : bug that takes a few hours to fix
     * [SWAG : Small] : 1 day to fix or implement
     * [SWAG : Medium] : 2 to 3 days to fix or implement
     * [SWAG : Big] : 1 week to fix or implement
     * [SWAG : Huge] : 2 weeks or more to fix or implement (those are 
good candidates for spec and further decomposition)

Is it important to be consistent? Are people happy with the swag units 
as proposed here?

I like the proposal overall. +1

Cheers,
Katie