From: "Somnath Kotur (Google Slides)" <comments-noreply@docs.google.com>
To: stable@dpdk.org
Subject: [dpdk-stable] DPDK Development Process
Date: Thu, 18 Mar 2021 21:57:38 -0700 [thread overview]
Message-ID: <ikrjlJ0XZUANcpmDxUxo6A@notifications.google.com> (raw)
In-Reply-To: <p+QUFIUnBuWHM1UncwZ3dZTm91YW9YSXZMcXBmb3h3WFBvWGVaV3ZHTC1BY2tCdVdJZVFJcTBoN01na1VFcmhsSzU2akNpd3hGOTBwdXgyM0lXRUZFekNFNllOdWxEZkpVSHowaEZ5cEJrRXROYV9fVXdHTjViaTd3OkFBQUFMemNfZEJB@docs.google.com>
Somnath Kotur mentioned you in a comment in the following document
DPDK Development Process
(https://docs.google.com/presentation/d/1OZKDRfPocVw-918PF2_5IeTH8FOZ8xya_JaJg5a5z4g/edit?disco=AAAALzc_dBA&ts=60542f42&usp=comment_email_document&usp_dm=false)
You do not have commenting rights to DPDK Development Process.
[1 comment hidden]
Somnath Kotur
Here are my thoughts @andrew.gospodarek@broadcom.com ,
@ajit.khaparde@broadcom.com , @lance.richardson@broadcom.com ,@kalesh
When we upstream one of our individual patches , we are already making a
judgement call if a patch needs to go in one of the n-1,n-2 LTS releases by
marking it for stable( or not) using the ' Cc: @stable@dpdk.org' tag
correct? So maybe when we do that we can automatically cherrypick the
patch to the 2 LTS branches for 17.11 and 19.11? (90 % of the time patches
should apply cleanly using the 'cherry-pick' button on Gerrit itself, since
the code in those 2 branches was based on int_nxt anyway).
Now, it should be Randy's team's call if the patch from these LTS branches
needs to be also included in the corresponding release branch that has been
cut from these LTS branches , IOW, the gatekeeper for these 'release
branches' is from their team, make sense? So if/when there is a bug on any
of these release branches , Randy's team will look at the patches that went
into these LTS branches and see cherrypicking any of them to the release
branch would help in the fix? Does this make sense?
Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
You have received this email because you are mentioned in this thread.
Change () what Google sends you.
You cannot reply to this email.
parent reply other threads:[~2021-03-22 12:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <p+QUFIUnBuWHM1UncwZ3dZTm91YW9YSXZMcXBmb3h3WFBvWGVaV3ZHTC1BY2tCdVdJZVFJcTBoN01na1VFcmhsSzU2akNpd3hGOTBwdXgyM0lXRUZFekNFNllOdWxEZkpVSHowaEZ5cEJrRXROYV9fVXdHTjViaTd3OkFBQUFMemNfZEJB@docs.google.com>]
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=ikrjlJ0XZUANcpmDxUxo6A@notifications.google.com \
--to=comments-noreply@docs.google.com \
--cc=p+noreply@docs.google.com \
--cc=stable@dpdk.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).