From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2A271A00E6 for ; Fri, 9 Aug 2019 04:52:47 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 374ED2B95; Fri, 9 Aug 2019 04:52:46 +0200 (CEST) Received: from dish-sg.nttdocomo.co.jp (dish-sg.nttdocomo.co.jp [202.19.227.74]) by dpdk.org (Postfix) with ESMTP id E2BCA2C5 for ; Fri, 9 Aug 2019 04:52:44 +0200 (CEST) X-dD-Source: Outbound Received: from zssg-mailmd101.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou101.ddreams.local (Postfix) with ESMTP id 09534120168; Fri, 9 Aug 2019 11:52:44 +0900 (JST) Received: from t131sg-mailcc11.ddreams.local (t131sg-mailcc11.ddreams.local [100.66.31.86]) by zssg-mailmd101.ddreams.local (dDREAMS) with ESMTP id <0PVY011287ZV31C0@dDREAMS>; Fri, 09 Aug 2019 11:52:43 +0900 (JST) Received: from t131sg-mailcc12 (localhost [127.0.0.1]) by t131sg-mailcc11.ddreams.local (unknown) with SMTP id x792qhVM061963; Fri, 9 Aug 2019 11:52:43 +0900 Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf106.ddreams.local (Postfix) with ESMTP id 271F67E603C; Fri, 9 Aug 2019 11:52:19 +0900 (JST) Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 209EC8E6063; Fri, 9 Aug 2019 11:52:19 +0900 (JST) Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 1E5B18E605A; Fri, 9 Aug 2019 11:52:19 +0900 (JST) X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026 Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 673B78E6042; Fri, 9 Aug 2019 11:52:18 +0900 (JST) Received: from zssg-mailua105.ddreams.local (unknown [10.160.172.62]) by zssg-mailmf106.ddreams.local (Postfix) with ESMTP; Fri, 9 Aug 2019 11:52:18 +0900 (JST) Received: from [10.87.198.18] (unknown [10.160.183.129]) by zssg-mailua105.ddreams.local (dDREAMS) with ESMTPA id <0PVY00D1G7Z4T6G0@dDREAMS>; Fri, 09 Aug 2019 11:52:16 +0900 (JST) Date: Fri, 09 Aug 2019 11:52:16 +0900 From: Hideyuki Yamashita In-reply-to: <20190809024002.GA85810@intel.com> References: <20190809111910.D110.17218CA3@ntt-tx.co.jp_1> <20190809024002.GA85810@intel.com> Message-id: <20190809115216.D113.17218CA3@ntt-tx.co.jp_1> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Becky! ver. 2.74.02 [ja] X-TM-AS-GCONF: 00 To: Ye Xiaolong Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] which is the code base when submitting patch around end of September X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello Ye, Thanks for your quick response. I understand the basis. I don't have much intention to push proposal to 19.11 right now. Thanks again. BR, Hideyuki Yamashita NTT TechnoCross > Hi, > > On 08/09, Hideyuki Yamashita wrote: > >Hello Experts, > > > > > >Very basic question to create patch. > > > >I am planning to post patch set which introduce new functionality (not > >bug fix ). > >Note that I will post the patch set on end of September. > > If your patch is targeted for 19.11 release, you need to send out your V1 patch > before proposal deadline 9/6, you can check the roadmap in http://core.dpdk.org/roadmap/. > > > > >Q1. > >If I post patch set to dev-ml, which is the code base? > >Source code which is retrieved from "git clone" ? > >Or tar ball of previous version like "dpdk-19.05.tar.gz"? > > > > In most of cases, you should clone the main tree (git clone http://dpdk.org/git/dpdk) > as the code base, and regularly rebase your patchset if you have new versions. > > >Q2. > >If review of the patch starts around October, when > >will the patch will be merged, if patch is good one. > >19.11 LTS? or 20.02? > >(Are there any rule or deadlines?) > > yes, please refer to the deadlines in the roadmap page. > > Thanks, > Xiaolong > > > > >Thanks in advance, > >Hideyuki Yamashita > >NTT TechnoCross > >