From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: lersek@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by groups.io with SMTP; Tue, 23 Apr 2019 04:10:22 -0700 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6DE8981DFE; Tue, 23 Apr 2019 11:10:17 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-235.rdu2.redhat.com [10.10.120.235]) by smtp.corp.redhat.com (Postfix) with ESMTP id 74B275D71D; Tue, 23 Apr 2019 11:10:16 +0000 (UTC) Subject: Re: [edk2-devel] Requestion for LTS version on EDK2 To: liyi 00215672 , devel@edk2.groups.io References: <31863.1555672260703193805@groups.io> From: "Laszlo Ersek" Message-ID: Date: Tue, 23 Apr 2019 13:10:14 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <31863.1555672260703193805@groups.io> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Tue, 23 Apr 2019 11:10:18 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 04/19/19 13:11, liyi 00215672 wrote: > Hi Laszlo, >=20 > 1. If we could put some human resources into stable-branch(LTS), so cou= ld you give us an rough=C2=A0assessment, how many people should we put th= em into that? :) Honestly: no idea. Maybe this could be estimated if all of the commits / BZs since the first stable tag, edk2-stable201808, were now reviewed in retrospect, as to whether each would be a candidate for backporting to a stable branch based on "edk2-stable201808". Alas, right now that means ~1500 commits, so not too easy either... Perhaps you could dedicate one person ATM to monitor / investigate this question. Monitor all of the new BZs and all of the patches posted to edk2-devel, and try to determine, working with the subject package maintainers, whether each issue is a bug (=3D not a new feature) and whether it affects, say, "edk2-stable201903". If it does, then the patch is likely a backport candidate. If this person managed to actually backport these patches, let's say to a personal stable branch for starters, and test them too, then in a few months we might have evidence that the process works -- and then the central repo could grow such an official stable branch. It's difficult to say how much extra time is needed, without researching it first in practice. > 2. If we make a stable-branch(LTS) into reality, we can invent some rul= es, likes one year(or two years) to release a LTS version, the LTS versio= n was only merged the bug-fixed. After the one or two years ,we=C2=A0will= release=C2=A0another new =C2=A0LTS version and the older one LTS we woul= d maintain for 3-5 years. I'd suggest starting small, and aiming at 1 year (tops) at first, for keeping a stable branch alive. Thanks Laszlo