[PATCH 1/2] add link in stable release section and update typical timeframe

[Kevin Traynor]

Signed-off-by: Kevin Traynor <ktraynor at redhat.com>
---
 content/roadmap/_index.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 9d3f8e6..a07ed2b 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -127,6 +127,8 @@ After each -rc tag and after the final version, relevant bug fixes get
 backported by the stable maintainers into the respective branches in "bursts".
 
-Developers can provide stable-specific patches by sending them
-to stable at dpdk.org only (avoiding dev at dpdk.org).
+Developers can provide stable specific patches by sending them
+to stable at dpdk.org only (avoiding dev at dpdk.org). Further information on
+subject prefixes for this case is documented
+[here](//doc.dpdk.org/guides/contributing/patches.html#backporting-patches-for-stable-releases).
 
 After all the relevant bugfixes have been backported,
@@ -134,5 +136,5 @@ regression tests are run, and if clear, the stable release is announced.
 
 Typically a new stable release version follows a mainline release
-by 1-2 weeks, depending on the test results.
+by 3-6 weeks, depending on the test results.
 
 | Current version | Next version | Next version Date | End of life | Maintainers            |
-- 
2.31.1