DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: "web@dpdk.org" <web@dpdk.org>
Cc: "ci@dpdk.org" <ci@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	"tim.odriscoll@intel.com" <tim.odriscoll@intel.com>,
	"lijuan.tu@intel.com" <lijuan.tu@intel.com>,
	"lylavoie@iol.unh.edu" <lylavoie@iol.unh.edu>
Subject: [dpdk-ci] [PATCH 1/2] rename the performance lab page
Date: Thu, 8 Nov 2018 16:48:02 +0000	[thread overview]
Message-ID: <20181108164732.11265-1-alialnu@mellanox.com> (raw)

DPDK Community Lab is a more generic and suitable name
if additional testing other than performance is added in the future.

Suggested-by: Thomas Monjalon <thomas@monjalon.net>
Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
---
 content/{perf-lab => lab}/_index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename content/{perf-lab => lab}/_index.md (75%)

diff --git a/content/perf-lab/_index.md b/content/lab/_index.md
similarity index 75%
rename from content/perf-lab/_index.md
rename to content/lab/_index.md
index 4061491..5a2e508 100644
--- a/content/perf-lab/_index.md
+++ b/content/lab/_index.md
@@ -1,5 +1,5 @@
 +++
-title = "Performance Lab"
+title = "DPDK Community Lab"
 weight = "8"
 +++
 
@@ -8,7 +8,7 @@ weight = "8"
 
 - Automated performance regression testing of new patches.
   - When a new patch is received, automatically test
-    and determine if it degrades performance on one or more architectures.
+    and determine if it degrades performance or causes other issues on one or more architectures.
   - Provides input to maintainers on whether to accept patches or request rework.
 - Scope may expand in future: test DPDK-enabled applications, use lab for demos, etc.
 
-- 
2.11.0

             reply	other threads:[~2018-11-08 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 16:48 Ali Alnubani [this message]
2018-11-08 16:48 ` [dpdk-ci] [PATCH 2/2] add a link to the CI dashboard Ali Alnubani
2018-11-20  9:20   ` Thomas Monjalon

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=20181108164732.11265-1-alialnu@mellanox.com \
    --to=alialnu@mellanox.com \
    --cc=ci@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@intel.com \
    --cc=web@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).