From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 4E30F201B0458 for ; Fri, 22 Feb 2019 12:19:43 -0800 (PST) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D1B1D58E40; Fri, 22 Feb 2019 20:19:42 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-125-131.rdu2.redhat.com [10.10.125.131]) by smtp.corp.redhat.com (Postfix) with ESMTP id D965B19C58; Fri, 22 Feb 2019 20:19:41 +0000 (UTC) To: "Gao, Liming" , "edk2-devel@lists.01.org" References: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E61EB@SHSMSX104.ccr.corp.intel.com> From: Laszlo Ersek Message-ID: Date: Fri, 22 Feb 2019 21:19:40 +0100 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: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E61EB@SHSMSX104.ccr.corp.intel.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Fri, 22 Feb 2019 20:19:42 +0000 (UTC) Subject: Re: [edk2-announce] Soft Feature Freeze starts today for edk2-stable201903 X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2019 20:19:43 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Hi Liming, On 02/22/19 15:25, Gao, Liming wrote: > Hi, all > https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning lists edk2-stable201903 tag planning. Now, we enter into Soft Feature Freeze phase. In this phase, the feature without Reviewed-by or Acked-by tags will be delayed after the upcoming stable tag. The patch review can continue without break. Below is edk2-stable201903 tag planning. > > 2019-03-08 Beginning of development > 2019-02-22 Soft Feature Freeze > 2019-03-01 Hard Feature Freeze > 2019-03-08 Release I got the last missing R-b from Ray for my patch set [edk2] [PATCH v3 0/5] MdeModulePkg, OvmfPkg, ArmVirtPkg: more visible boot progress reporting today (2019-02-22) at 12:50 in my time zone (CET = UTC+01:00). Before pushing the series, I asked Ray to confirm one last thing about his review. I consider the series properly reviewed, but due to this last question, I expect I should push it early next week. IMO that satisfies the soft feature freeze definition: https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze "By the date of the soft feature freeze, developers must have sent their patches to the mailing list and received positive maintainer reviews (Reviewed-by or Acked-by tags). [...] Between the soft feature freeze and the hard feature freeze, previously reviewed and unit-tested features may be applied (or merged) to the master branch, for integration testing." Do you (and others) agree? If not, I won't insist -- while I'd certainly prefer these patches to be in the upcoming stable tag, if the community perceives it would mean bending the rules, I wouldn't want to do that. (Right now I don't think it would bend the rules). Thanks, Laszlo