From: Thomas Monjalon <thomas@monjalon.net> To: Ajit Khaparde <ajit.khaparde@broadcom.com> Cc: Ferruh Yigit <ferruh.yigit@intel.com>, dpdk-dev <dev@dpdk.org>, David Marchand <david.marchand@redhat.com>, Asaf Penso <asafp@nvidia.com>, John McNamara <john.mcnamara@intel.com>, Bruce Richardson <bruce.richardson@intel.com> Subject: Re: [dpdk-dev] [PATCH v8] doc: add release milestones definition Date: Tue, 14 Sep 2021 18:46:28 +0200 Message-ID: <2616975.G1blO3fqPY@thomas> (raw) In-Reply-To: <CACZ4nhu=CxasajzHCXRFqDvk9EReny+WA9OisLB+uDWAO5N_NA@mail.gmail.com> 14/09/2021 18:11, Ajit Khaparde: > On Tue, Sep 14, 2021 at 12:53 AM Thomas Monjalon <thomas@monjalon.net> wrote: > > 03/09/2021 17:35, Ferruh Yigit: > > > On 9/3/2021 12:50 PM, Thomas Monjalon wrote: > > > > 02/09/2021 18:33, Ferruh Yigit: > > > >> On 8/26/2021 11:11 AM, Thomas Monjalon wrote: > > > >>> +* Any issue found in -rc1 should be fixed. > > > >>> + > > > >>> +rc3 > > > >>> +~~~ > > > >>> + > > > >>> +* Priority: applications. No application feature should be accepted after -rc3. > > > >>> +* New functionality that does not depend on libraries update > > > >>> + can be integrated as part of -rc3. > > > >>> +* The application change must include documentation in the relevant .rst files > > > >>> + (application-specific and release notes if significant). > > > >>> +* Libraries and drivers cleanup are allowed. > > > >>> +* Small driver reworks. > > > >>> +* Critical and minor bug fixes. > > > >> > > > >> As mentioned before, my concern is this may create false impression that bugs > > > >> are fixed only in this phase. What about remove this line completely and update > > > >> below -rc4 one as 'Critical bug fixes only.'? I think that makes intention more > > > >> clear. > > > > > > > > I had added in -rc2: "Any issue found in -rc1 should be fixed." > > > > Do you want to remove it as well? > > > > > > I think we can keep it, good to highlight one of the major tasks for -rc2 is to > > > fix defects found in -rc1, and it doesn't limit fixes to ones found in -rc1. > > > > Actually I think it is better to remove. > > It looks weird to have it only in -rc2. > I see you have sent the new version and it is looking really good. > > We can mention that bug fixes are welcome at any point in the cycle, I hope it is obvious. > but priority will be given to critical fixes close to the release date. Yes it says critical bug fixes only.
next prev parent reply other threads:[~2021-09-14 16:46 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-10 18:44 [dpdk-dev] [PATCH] " Asaf Penso 2021-01-12 13:30 ` [dpdk-dev] [PATCH v2] " Michael Baum 2021-01-13 9:12 ` [dpdk-dev] [PATCH v3 1/1] " Thomas Monjalon 2021-01-27 18:33 ` Mcnamara, John 2021-02-01 22:13 ` [dpdk-dev] [PATCH v4 " Thomas Monjalon 2021-02-01 22:31 ` Ajit Khaparde 2021-02-01 22:38 ` Thomas Monjalon 2021-02-03 7:58 ` [dpdk-dev] [PATCH v5 " Thomas Monjalon 2021-02-03 10:14 ` David Marchand 2021-02-03 10:27 ` Thomas Monjalon 2021-03-28 19:00 ` [dpdk-dev] [PATCH v6] " Thomas Monjalon 2021-03-29 2:02 ` Ajit Khaparde 2021-05-18 11:57 ` Ferruh Yigit 2021-05-18 12:25 ` Thomas Monjalon 2021-05-18 13:13 ` Ferruh Yigit 2021-05-18 17:20 ` Ajit Khaparde 2021-05-18 16:43 ` [dpdk-dev] [PATCH v7] " Thomas Monjalon 2021-05-19 8:56 ` Bruce Richardson 2021-05-19 11:58 ` Ferruh Yigit 2021-05-19 12:16 ` Thomas Monjalon 2021-08-26 10:11 ` [dpdk-dev] [PATCH v8] " Thomas Monjalon 2021-09-02 16:33 ` Ferruh Yigit 2021-09-03 11:50 ` Thomas Monjalon 2021-09-03 15:35 ` Ferruh Yigit 2021-09-14 7:53 ` Thomas Monjalon 2021-09-14 16:11 ` Ajit Khaparde 2021-09-14 16:46 ` Thomas Monjalon [this message] 2021-09-03 12:26 ` Andrew Rybchenko 2021-09-03 12:55 ` Thomas Monjalon 2021-09-14 7:56 ` [dpdk-dev] [PATCH v9] " Thomas Monjalon 2021-09-14 16:34 ` Ferruh Yigit 2021-09-14 16:50 ` Thomas Monjalon 2021-09-14 16:51 ` Ajit Khaparde 2021-09-14 17:20 ` Thomas Monjalon
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=2616975.G1blO3fqPY@thomas \ --to=thomas@monjalon.net \ --cc=ajit.khaparde@broadcom.com \ --cc=asafp@nvidia.com \ --cc=bruce.richardson@intel.com \ --cc=david.marchand@redhat.com \ --cc=dev@dpdk.org \ --cc=ferruh.yigit@intel.com \ --cc=john.mcnamara@intel.com \ /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
DPDK patches and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \ dev@dpdk.org public-inbox-index dev Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git