add testing requirement for new PMDs

As discussed in the technical board meeting
https://mails.dpdk.org/archives/dev/2021-February/200012.html

This is to record that new upstreamed devices tested adequately.

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
CC: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
---
 content/testing/_index.md | 4 ++++
 1 file changed, 4 insertions(+)
  

2021-06-24 15:45 (UTC+0100), Ferruh Yigit:
> As discussed in the technical board meeting
> https://mails.dpdk.org/archives/dev/2021-February/200012.html
> 
> This is to record that new upstreamed devices tested adequately.
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> CC: John McNamara <john.mcnamara@intel.com>
> Cc: dev@dpdk.org
> ---
>  content/testing/_index.md | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/content/testing/_index.md b/content/testing/_index.md
> index fcdc47feca9a..3e430f8640af 100644
> --- a/content/testing/_index.md
> +++ b/content/testing/_index.md
> @@ -116,6 +116,10 @@ some validation reports are requested to the community members.
>  
>  Such release validations are sent as replies to the release announcement.
>  
> +It is not easy (or not possible at all) to test PMDs other than device vendors,

I'm not a native speaker, but is "for" missing (to do X is easy for Y)?
Suggestion: for anyone other than device vendors.

> +that is why it is expected vendors send a release validation report at least in
> +the first release that the PMD is upstreamed.
> +
>  
>  ## Tools
>  ---
  

On 6/24/2021 4:30 PM, Dmitry Kozlyuk wrote:
> 2021-06-24 15:45 (UTC+0100), Ferruh Yigit:
>> As discussed in the technical board meeting
>> https://mails.dpdk.org/archives/dev/2021-February/200012.html
>>
>> This is to record that new upstreamed devices tested adequately.
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> ---
>> CC: John McNamara <john.mcnamara@intel.com>
>> Cc: dev@dpdk.org
>> ---
>>  content/testing/_index.md | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/content/testing/_index.md b/content/testing/_index.md
>> index fcdc47feca9a..3e430f8640af 100644
>> --- a/content/testing/_index.md
>> +++ b/content/testing/_index.md
>> @@ -116,6 +116,10 @@ some validation reports are requested to the community members.
>>  
>>  Such release validations are sent as replies to the release announcement.
>>  
>> +It is not easy (or not possible at all) to test PMDs other than device vendors,
> 
> I'm not a native speaker, but is "for" missing (to do X is easy for Y)?
> Suggestion: for anyone other than device vendors.
> 

Thanks Dmitry, I consulted to John for it, I am sending a new version soon.

>> +that is why it is expected vendors send a release validation report at least in
>> +the first release that the PMD is upstreamed.
>> +
>>  
>>  ## Tools
>>  ---
>