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

[Kevin Traynor]

Replied to the wrong LTS updates thread. Please ignore.

On 13/01/2022 10:11, Kevin Traynor wrote:
> Signed-off-by: Kevin Traynor <ktraynor at redhat.com>
> ---
>   content/roadmap/_index.md | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> index 9d3f8e6..cf212a4 100644
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -129,4 +129,6 @@ 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).
> +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            |
>