[Cosmo-dev] Re: Bugzilla Trunk version
Jared Rhine
jared at wordzoo.com
Wed Dec 6 01:33:01 PST 2006
Jared Rhine wrote:
> I poked around the Mozilla Sunbird's bugzilla yesterday, and saw a
> configuration that immediately made total sense to me. I'd like to propose
> it for use in Cosmo's bugzilla.
>
> * Add "Trunk" to the list of "versions"
It looks like there's no version identifier in Cosmo's bugzilla to
record bugs against trunk.
I'd like to continue advocating for the addition of "Trunk" to the
bugzilla "Version" field. If there is objection to this, at least a 0.6
entry should be added. (If the thread stays silent, I'll just go ahead
and add it.)
I'm including the rest of my original email proposal (Oct 20th) below
for context; there's not much to add on the topic.
> So instead of reporting most new bugs currently as version "0.5" bugs,
> they'd be reported as version "Trunk".
>
> Benefits:
> * A bit more specificity on where a bug was found
>
> * Less need to pay attention to exactly what release is out vs upcoming
>
> * Bit easier to quantify sources of bugs. Count up "Trunk" version bugs
> versus a numbered release, and the former will be mostly devs reports vs
> user reports for the latter.
>
> Downsides:
> * Trunk still doesn't say where you actually found a bug; you still need to
> include a specific svn revision number in a bug report to report a bug properly
>
> * You can't really look back over a long history of bug reports and use
> "version" as a guide as to when a bug was entered.
>
> * Maybe this approach has already been discussed early at OSAF and rejected.
> Many bugzilla configurations don't use it; it's not necessarily better.
>
> I'm not very vested in moving to this. Maybe it just looks cool to me
> because of the novelty. But it seemed worth a pointer and proposal. Thanks.
>
> -- Jared
More information about the cosmo-dev
mailing list