DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 705] 2021 Epic: Deploy Coverity Alternatives
Date: Mon, 17 May 2021 20:59:48 +0000	[thread overview]
Message-ID: <bug-705-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=705

            Bug ID: 705
           Summary: 2021 Epic: Deploy Coverity Alternatives
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: UNH infra
          Assignee: ci@dpdk.org
          Reporter: lylavoie@iol.unh.edu
                CC: dpdklab@iol.unh.edu
  Target Milestone: ---

Summary: Expand the static analysis tools available to the CI testing, adding 3
additional static analyzers and a spell checker.

* Completed Q1 Story: Investigate list of static analyzers, reporting to the
Tech Board with a recommendation of 3 to move forward with for depoyment.
* Q2 Story: Deploy spell checker to review changes to documentation patches.
* Q4 Story: Complete deployment of 3 additional static analyzers by the end of
Q4.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-05-17 20:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-705-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).