Trac: release management

Noah Kantrowitz noah at coderanger.net
Fri Jun 13 14:45:49 EDT 2008


> -----Original Message-----
> From: devel-bounces at lists.laptop.org [mailto:devel-
> bounces at lists.laptop.org] On Behalf Of Wade Brainerd
> Sent: Friday, June 13, 2008 11:38 AM
> To: Garrett Goebel
> Cc: devel at lists.laptop.org
> Subject: Re: Trac: release management
> 
> Hello,
> 
> I agree wholeheartedly that ticket triage and statistical analysis is
> a worthwhile effort, so I think I support what Garrett is talking
> about.
> 
> At my employer we have teams of producers constantly watching
> individual and per-component bug counts, transfering bugs from
> overworked team members, ensuring progress is being made according to
> priority levels, and tracking the rate of change of the blocking
> ticket count compared with previous projects to estimate our
> completion date, among other things.
> 
> Without that kind of attention, there is no way we would ship anything
> on time.  I don't care how the open source world "usually" does it,
> releases don't happen unless you're on top of your tickets.
> 
> I know there is a Git plugin for Trac, anyone know why it isn't
> installed?  I would love to see commits on the Trac Timeline RSS feed,
> and the Trac source browser is pretty nice too.

People requested we stay with gitweb as everyone was familiar with it.

--Noah




More information about the Devel mailing list