[Gluster-infra] Tracking issues on Bugzilla

Nigel Babu nigelb at redhat.com
Sat Jun 11 05:56:45 UTC 2016

On Fri, Jun 10, 2016 at 08:09:28PM +0200, Michael Scherer wrote:
> Le vendredi 10 juin 2016 à 14:12 +0530, Nigel Babu a écrit :
> > Hello folks,
> >
> > There's a bugzilla component for glusterfs on Bugzilla called
> > project-infrastructure. As far as I can see, we've used it on and off. I'd like
> > to propose that we file bugs in that component for anything infra-related
> > rather than report on the mailing list. This will let us track issues into
> > completion rather than have them potentially lost on the mailing list.
> >
> > Does anyone have any strong feelings against this?
> Could issues be sent on that ML ?
> (ideally, if we could also have answer by mail, but I think this is
> disabled in RH bugzilla).
> And I am also pondering on the multiplication of account, ie, we need to
> have github account, rh bugzilla account, jenkins account, etc. Not
> strongly to be against bz, but to keep in mind. (this and the dependency
> of gluster on the main sponsor, which i think we should try to reduce to
> put the community in charge a bit more)
> --
> Michael Scherer
> Sysadmin, Community Infrastructure and Platform, OSAS

I expect the people who will file infra bugs to be developers or those of us
who deal with infrastructure. Most people have a bugzilla account anyway
because that's where we file upstream bugs. The dependency on the primary
sponsor already exists. It makes more sense to keep all the bugs, code and
infra, in one place.

The only other platform I can think of using is Github, which does not let us
have private bugs (at least not easily). Infrastructure bugs should have an
option for private bugs in case we want to discuss a security issue.


More information about the Gluster-infra mailing list