From: Luca Boccassi <bluca@debian.org>
To: web@dpdk.org
Cc: thomas@monjalon.net, yliu@fridaylinux.org,
Luca Boccassi <bluca@debian.org>
Subject: [dpdk-web] [RFC] Add LTS section on the roadmap page
Date: Thu, 8 Feb 2018 18:21:42 +0000 [thread overview]
Message-ID: <20180208182142.6189-1-bluca@debian.org> (raw)
Signed-off-by: Luca Boccassi <bluca@debian.org>
---
dev/roadmap.html | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index a2fea2f..c818bde 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -111,5 +111,15 @@
<li>Integration deadline: September 28, 2018
<li>Release: November 2, 2018
</ul>
+ <h3 id="lts">LTS releases</h3>
+ <p>LTS point releases follow mainline releases.
+ <p>After each -rc tag and after the final version, relevant bug fixes get
+ backported by the LTS maintainers into the respective branches.
+ <p>Developers can provide LTS-specific patches by sending them to stable@dpdk.org
+ only.
+ <p>After all the relevant bugfixes have been backported, regression tests are ran,
+ and if clear, the LTS is announced.
+ <p>Typically a new LTS version follows a mainline release by 1-2 weeks, depending
+ on the test results.
</section>
<footer></footer>
--
2.14.2
next reply other threads:[~2018-02-08 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 18:21 Luca Boccassi [this message]
2018-02-08 18:24 ` Luca Boccassi
2018-02-08 20:42 ` Thomas Monjalon
2018-02-09 13:05 ` Luca Boccassi
2018-02-09 13:04 ` [dpdk-web] [RFC v2] " Luca Boccassi
2018-03-06 11:25 ` Thomas Monjalon
2018-03-06 19:45 ` Luca Boccassi
2018-03-06 19:43 ` [dpdk-web] [RFC v3] " Luca Boccassi
2018-03-08 22:47 ` 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=20180208182142.6189-1-bluca@debian.org \
--to=bluca@debian.org \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--cc=yliu@fridaylinux.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).