On Mon, Aug 22, 2016 at 2:47 AM, Niels de Vos <[email protected]> wrote:
> On Mon, Aug 22, 2016 at 11:16:15AM +0200, Michael Scherer wrote: > > Le lundi 22 août 2016 à 12:41 +0530, Nigel Babu a écrit : > > > Hello, > > > > > > I've just switched the bugzilla authentication on Gerrit today. From > today > > > onwards, Gerrit will comment on Bugzilla using a new account: > > > > > > [email protected] > > > > > > If you notice any issues, please file a bug against > project-infrastructure. > > > This bot will only comment on public bugs, so if you open a review > request when > > > the bug is private, it will fail. This is intended behavior. > > > > You got me curious, in which case are private bugs required ? > > > > Do we need to make sure that the review is private also or something ? > > I do not expect any private bugs. On occasion it happens that a bug gets > cloned from Red Hat Gluster Storage and it can contain customer details. > Sometimes those bugs are not cleaned during the cloning (BAD!) and keep > the references to details from customers. > > All bugs that we have in the GlusterFS product in bugzilla must be > public, and must have a public description of the reported problem. > > Niels > > _______________________________________________ > Gluster-infra mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-infra > Is it worth denying all posts from RHGS and causing people to manually submit bugs? I realize that's using a hammer on an edge-case, but if someone is moving a bug to the gluster.org project, I feel like it's on them to scrub it. -- amye -- Amye Scavarda | [email protected] | Gluster Community Lead
_______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
