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 54F74A00E6 for ; Fri, 9 Aug 2019 04:40:42 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5F36D2B8C; Fri, 9 Aug 2019 04:40:41 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id F089829CB for ; Fri, 9 Aug 2019 04:40:39 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Aug 2019 19:40:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,363,1559545200"; d="scan'208";a="193292202" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.117.5]) by fmsmga001.fm.intel.com with ESMTP; 08 Aug 2019 19:40:38 -0700 Date: Fri, 9 Aug 2019 10:40:02 +0800 From: Ye Xiaolong To: Hideyuki Yamashita Cc: "dev@dpdk.org" Message-ID: <20190809024002.GA85810@intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BAB790C9E0@IRSMSX108.ger.corp.intel.com> <20190809111910.D110.17218CA3@ntt-tx.co.jp_1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190809111910.D110.17218CA3@ntt-tx.co.jp_1> User-Agent: Mutt/1.9.4 (2018-02-28) 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" 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 >