DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-web] [PATCH] highlight roadmap is not commitment for release
Date: Mon, 10 Sep 2018 11:14:05 +0100	[thread overview]
Message-ID: <20180910101405.43799-1-ferruh.yigit@intel.com> (raw)

Add a note to roadmap to say roadmap items are not commitment but list
of planned work.

This is to address concern to share roadmaps publicly, that published
roadmap can be taken as commitment for that release.

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
cc'in doc maintainers:
Cc: John McNamara <john.mcnamara@intel.com>
Cc: Marko Kovacevic <marko.kovacevic@intel.com>
---
 content/roadmap/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 8968da5..fc09b81 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -4,7 +4,7 @@ weight = "3"
 +++
 
 {{% notice info %}}
-Major known features and milestones may be noted here.
+Major known features and milestones may be noted here. This is not a commitment but plan of work.
 This list is obviously neither complete nor guaranteed.
 {{% /notice %}}
 
-- 
2.17.1

             reply	other threads:[~2018-09-10  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 10:14 Ferruh Yigit [this message]
2018-09-10  9:23 ` Thomas Monjalon
2018-10-16  8:45   ` 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=20180910101405.43799-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=thomas@monjalon.net \
    --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).