Re: [dpdk-ci] bugzilla section for the lab

[Jeremy Plsek <jplsek@iol.unh.edu>]

I would say almost anything could be put into the bugzilla, such as
feature requests (such as those made during our meetings) and bug
reports. Major changes and additions to the policies document could be
done on the bugzilla for more discussion and tracking.

What would not go on the bugzilla would probably be security concerns
(these can be made public later after confirmation and a fix was made)
or member specific requests.

I could start adding feature requests talked about from previous
meetings onto the bugzilla, just to get it going.
On Tue, Aug 21, 2018 at 8:31 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> On 8/20/2018 6:16 PM, Thomas Monjalon wrote:
> > Hi,
> > Following up on below request:
> >
> > 01/08/2018 15:55, O'Driscoll, Tim:
> >> * Thomas will update Bugzilla so we can use it for tracking lab tickets.
> >
> > I have created a new "product" in bugzilla, called "lab".
> > Now we can fill a bug for the lab:
> >       https://bugs.dpdk.org/enter_bug.cgi
> >
> > Then you can choose between "dashboard" and "UNH infra".
> > If we need other or more bugzilla components, please ask.
>
> Is only for defects, when implementation doesn't match the requirement, or do we
> plan to use bugzilla for new requirements and/or changing existing requirements?
>
> >
> > The default assignee, for above components, is ci@dpdk.org
> > mailing list, meaning that new bugs will be posted here.
> > Jeremy is already on the default Cc list.
> > If you think the Cc list must be modified, please ask.
> >
> > I think we can use this bugzilla section for other labs
> > participating in the distributed CI (Intel for now).
> > It would require to create just a new "component" in bugzilla.
> >
> > Hope it will be useful
> >
> >
>


--
Jeremy Plsek
UNH InterOperability Laboratory