diff mbox series

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

Message ID 20220111121949.92998-1-ktraynor@redhat.com (mailing list archive)
State Superseded
Headers
Series [1/2] add link in stable release section and update typical timeframe |

Commit Message

Kevin Traynor Jan. 11, 2022, 12:19 p.m. UTC 
  Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
 content/roadmap/_index.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

Comments

Thomas Monjalon Jan. 11, 2022, 12:43 p.m. UTC | #1 
11/01/2022 13:19, Kevin Traynor:
> Signed-off-by: Kevin Traynor <ktraynor@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@dpdk.org only (avoiding dev@dpdk.org).
> +Developers can provide stable specific patches by sending them
> +to stable@dpdk.org only (avoiding dev@dpdk.org). Further information on

Please start sentence on a new line.

> +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.
Kevin Traynor Jan. 11, 2022, 1:22 p.m. UTC | #2 
On 11/01/2022 12:43, Thomas Monjalon wrote:
> 11/01/2022 13:19, Kevin Traynor:
>> Signed-off-by: Kevin Traynor <ktraynor@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@dpdk.org only (avoiding dev@dpdk.org).
>> +Developers can provide stable specific patches by sending them
>> +to stable@dpdk.org only (avoiding dev@dpdk.org). Further information on
> 
> Please start sentence on a new line.
> 

Ack, thanks. Will wait to see if there's any other comments, then send a v2.

>> +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.
> 
> 
>
diff mbox series

Patch

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@dpdk.org only (avoiding dev@dpdk.org).
+Developers can provide stable specific patches by sending them
+to stable@dpdk.org only (avoiding dev@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            |