From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id E68A144C3 for ; Tue, 12 Mar 2019 20:12:59 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 0190F3086206; Tue, 12 Mar 2019 19:12:59 +0000 (UTC) Received: from [10.33.36.103] (unknown [10.33.36.103]) by smtp.corp.redhat.com (Postfix) with ESMTP id 02DD95F9B7; Tue, 12 Mar 2019 19:12:56 +0000 (UTC) From: Kevin Traynor To: "dev@dpdk.org" Cc: Luca Boccassi , Yongseok Koh , Thomas Monjalon , Ferruh Yigit , John McNamara , Aaron Conole , "Walker, Benjamin" , Jay Rolette Message-ID: <0989b56a-f480-416c-e0a7-3e562c9b990b@redhat.com> Date: Tue, 12 Mar 2019 19:12:56 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.42]); Tue, 12 Mar 2019 19:12:59 +0000 (UTC) Subject: [dpdk-dev] DPDK short term stable maintenance 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: , X-List-Received-Date: Tue, 12 Mar 2019 19:13:00 -0000 Hi All, This is about short term stable maintenance, ~3 months based on n.02/05/08 DPDK. It is **not** referring/impacting DPDK LTS, maintained for ~2 years based on n.11 DPDK. The effort and usefulness of short term stable maintenance was raised previously and in the last DPDK Release meeting [1], so sending mail to kick off discussion here... Currently DPDK 19.02 stable branch has no maintainer and it has been difficult to get the companies to validate DPDK 18.08.1 RC. There seems to be a lack of appetite in the community for short term stables, or at least for all of them, and hence giving resources for helping them. It could be that users are either moving from latest bleeding edge master release to the next, or settling on DPDK LTS for an extended period of time - I'm just speculating, but IMHO that would not be a bad thing. So what to do with short term stables? Some choices could be: - continue with short term stables for n.02/05/08 - ad-hoc support for short term stables where community have an interest in a particular one - have a maintainer to backport fixes on a public branch, but have no releases, or have unvalidated/best effort validated releases - no short term stable branches/releases Probably there's other ideas too. Obviously most of the above would need resources from the community to proceed. One advantage of not having short term stables is that there might be more resources available for maintenance/validation of master and LTS DPDK releases. Thoughts? thanks, Kevin. [1] https://mails.dpdk.org/archives/dev/2019-March/126006.html