From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by dpdk.org (Postfix) with ESMTP id 2090B3DC for ; Tue, 21 Aug 2018 19:23:06 +0200 (CEST) Received: by mail-oi0-f49.google.com with SMTP id n21-v6so33414150oig.3 for ; Tue, 21 Aug 2018 10:23:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=b86JSYrR/uG0SDPhEFJL0wWgpY14l0C5MPMWnWB5Isc=; b=BEUObKc6iBnyztqqx+MYhWJWwc9+tyLRVm7dX+pjX6z4eygYra0P6qiGJF/07VezfG iHyb//zZKGUyOEVkUSYQiELI5YSqWhvL61dSPQg6b2zUoeyHEtbqjRlVa9MgwJA5NiMk 3n5WEv/ThZIAvheK2misi0zW58l0OV31xxwwc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b86JSYrR/uG0SDPhEFJL0wWgpY14l0C5MPMWnWB5Isc=; b=Sc2Qq71z5QxIWeAlbOc5uXx1OwCkZ5ItzkWyfz7gNiHSa9/1mkTg3xRBT9j8marg6z AeovZuUw1PIJRvFDLEyXPoZDeLfZIehRONihDIM8Ye1EDit8Jd/BsCZxCG96/mqw8vjY yyYSP0RE5hLmy3YjZ+RP3fmWD8q07bxHBDuot+4ko6qMEokzcGNjYYrKF6UQB9PyZCUr bVi+n4z7uTT5DK2GYG9cyv0vnWI1KLw4mziEg2BSN6IevttSeQ4vrHh/s/rjNj//9UKW DqNq1QlwP1nJm4ZSAsIWVVM3hpstM508LvRrxLTPff1+2vtFIm5M5Fzjl973WZWCOypp VX3g== X-Gm-Message-State: APzg51DBLBO5C20sVnLLvYxRp6qVJnNMIDiFerlhl/grWG8EbvB59UYw DwRSJ1U25RnVB9BiJrsfpg1gicWgMxAI1YWLmAFcVw== X-Google-Smtp-Source: ANB0VdbqKwy/drbqQilpAnb4fUF7VOpsSfPnUz+Stq/OBT42YIBiOidPnQYUz+nvNLbn2iut5gYvMTZ4AYRI99XfFUo= X-Received: by 2002:aca:bd8b:: with SMTP id n133-v6mr288725oif.108.1534872185309; Tue, 21 Aug 2018 10:23:05 -0700 (PDT) MIME-Version: 1.0 References: <26FA93C7ED1EAA44AB77D62FBE1D27BAB772ACA1@IRSMSX107.ger.corp.intel.com> <2274547.mcss5qQXk0@xps> <7e4b37f2-dda8-7e2f-e377-b445f6961655@intel.com> In-Reply-To: <7e4b37f2-dda8-7e2f-e377-b445f6961655@intel.com> From: Jeremy Plsek Date: Tue, 21 Aug 2018 13:22:28 -0400 Message-ID: To: "Yigit, Ferruh" Cc: thomas@monjalon.net, ci@dpdk.org, "O'Driscoll, Tim" , Trishan de Lanerolle Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-ci] bugzilla section for the lab X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2018 17:23:06 -0000 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 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