Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Thu, 12 Feb 2004 07:38:24 +0100
Subject: Re: bugzilla usage (was: [IMP] Code Freeze)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: dev@cocoon.apache.org
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <402A7A17.2020203@gmx.de>
Message-Id: <0F017483-5D26-11D8-AC5E-000393CFE402@apache.org>

Le Mercredi, 11 f=E9v 2004, =E0 19:53 Europe/Zurich, Joerg Heinicke a =
=E9crit=20
:
> ...The dependency tree as we use it at the moment is not meant=20
> blocking, but that's an obvious wrong usage of it and bugzilla as it=20=

> reads "bug 123 blocks 456". We really should use this only for=20
> blocking issues...

I disagree, these dependency lists are very useful to quickly get a=20
picture of where we stand.

But you're right that saying "bug 123 blocks 456" is not correct. Note=20=

that the reverse field is called "bug 456 depends on 123" which=20
correctly represents what we mean: dependencies, not blocking.

We might be flexing bugzilla a bit (hmm....someone will certainly=20
mention jira here) but it seems to work well, I think bugzilla is used=20=

much more now than a few months ago and find it a Good Thing.

Problem is, in a dependency page like
http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=3D25321
you don't see what's a blocker, what's nice to have and so on.

An easy way to fix this would be to add [BLOCKER] to the title as we=20
already do for patches.

The official way is to use the "severity" field, but unfortunately it=20
is not visible on the dependency tree.

...
> Bugzilla provides another function to add "might be good to have it in=20=

> the release": target milestones. We should just add milestones for=20
> every release and set value for the "might be good ..."-bugs.

You're right but I prefer the dependency tree because of the crossed /=20=

non-crossed bug display. And target milestones need to be changed=20
manually a lot when bugs don't make it to the expected release.

> WDYT? Where are the bugzilla admins?

Some of us have additional rights in bugzilla to be able to define=20
products and components, see
http://marc.theaimsgroup.com/?l=3Dxml-cocoon-dev&m=3D107029869507213&w=3D2=

But it doesn't mean we're the rulers of bugzilla, it's as much a=20
community tool as everything else.

-Bertrand