From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from NAM12-DM6-obe.outbound.protection.outlook.com (NAM12-DM6-obe.outbound.protection.outlook.com [40.107.243.97]) by mx.groups.io with SMTP id smtpd.web08.16622.1611084880168900763 for ; Tue, 19 Jan 2021 11:34:40 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@microsoft.com header.s=selector2 header.b=ZRJtMCJL; spf=pass (domain: microsoft.com, ip: 40.107.243.97, mailfrom: bret.barkelew@microsoft.com) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Jwg3SLxfEPHApd2Bw471jhVFGlCUq+qGQjARDpqDBtu0vo4lX/RalD8edNVEACCRj0EiKMdsRUqq0RGPExwcrAF38xLfIY169etE6vofXl0hKr9N8gI5DQXoRCwQRi4cBhnXx3qcWLmnK3NKwpMVcU2m05AWOoEgFXlBahJzSblHUf6EHlyf7Vi/zjuTuLO0uaLy3TCWoJdwYz34mxA2h+ow0O7up7R41r/9NNr3CpII4mSRyzqaQwXj6GL52zc3hVBw67x9WHlhnsvHzmEZ+TAtrfCZTwR9tNBgrKiBIBjlzXPpSdrfhdxqiq9e60RJqiOvYV+RM+UJMja5gz/W+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uz+ZJmqHQLbN+CklJuBVPFVIhXwxY1Re5bmHMrfPTu4=; b=n8W/yr5Ep+DS7EuwR2tGGm7hfS+Wb9X5Fzfh8lGxwFnFWyhyNDvH3mctL1jKYpwTXwY21eRsQpl25J7LfNDMNIWn00pLLjvXnIFRxOLFDZzRzZ5/uIfoa8wYLytEIEbcsfMSj1m09IeMnNU8GdG1toj1SccuxaAyTWOBIofsXZRCsr900+zDCHQs+asY2hJ738XEyNkR3VisPuHLMbws4iuEUAqdI/OQU2twXZsK2vV4gmZ+L7YIo4p1Q4c2mnHB3n8IZpaLRm/vKNMVjjivPZ7iLd+vd/EeHDSt0LPYxyhK4M96LUEolcLVms0fs+ekHsSB+MFBcV3Q7L//JuE85g== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uz+ZJmqHQLbN+CklJuBVPFVIhXwxY1Re5bmHMrfPTu4=; b=ZRJtMCJLtG5MWITWtCTC+VPj3NTT/ajG+zKJVqhiXv0JWaYotRzDk4oEI5vI0HVnzKc6o9JdubKWN3QTODoDFAqN5Z2cvZnN5CHJTjYIRmJyj9EmJWl6XES/7IypoC4j1NHoH6hzpuGYDZfklZzS2DFBJvJ0IFBBa39dUlmc8CE= Received: from (2603:10b6:903:ba::8) by CY4PR21MB0504.namprd21.prod.outlook.com (2603:10b6:903:dc::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.2; Tue, 19 Jan 2021 19:34:37 +0000 Received: from CY4PR21MB0182.namprd21.prod.outlook.com ([fe80::dc6e:7d8f:2332:b6c1]) by CY4PR21MB0182.namprd21.prod.outlook.com ([fe80::dc6e:7d8f:2332:b6c1%14]) with mapi id 15.20.3805.004; Tue, 19 Jan 2021 19:34:37 +0000 From: "Bret Barkelew" To: "devel@edk2.groups.io" , "lersek@redhat.com" , "Liming Gao (Byosoft address)" , "Leif Lindholm (Nuvia address)" , "Ard Biesheuvel (TianoCore)" , "Ni, Ray" , Zhichao Gao , Abner Chang CC: edk2-devel-groups-io Subject: Re: [EXTERNAL] [edk2-devel] building the shell for edk2-stable202102 Thread-Topic: [EXTERNAL] [edk2-devel] building the shell for edk2-stable202102 Thread-Index: AQHW7pmbqdOsQciE90yf3g3ZDyIJ1aovVkV8 Date: Tue, 19 Jan 2021 19:34:36 +0000 Message-ID: References: <660228dd-649f-2fd9-e4c6-d8d206194020@redhat.com> In-Reply-To: <660228dd-649f-2fd9-e4c6-d8d206194020@redhat.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2021-01-19T19:31:50.6203329Z;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Privileged authentication-results: edk2.groups.io; dkim=none (message not signed) header.d=none;edk2.groups.io; dmarc=none action=none header.from=microsoft.com; x-originating-ip: [174.21.79.155] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 3ca2db8b-c355-44d1-d622-08d8bcb141bc x-ms-traffictypediagnostic: CY4PR21MB0504: x-ld-processed: 72f988bf-86f1-41af-91ab-2d7cd011db47,ExtAddr x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 4cjOFAmRb4VwJQLR3kJyTXb30/5Tc4gZbg5d0PaGeQTUluHTm5hDTWWG/grSc32oxbO3MdHqCeS79Du0IdfODhclShEE3uIsiUQaLasBSfDaSNv9mII9nLawdLVPU+aVR28u+wbjC+uirr5h0fVkBy3veZBhoTOjz4AD+JQm4nYuCr9by/zD9VECjf41xeNQ81cTLayWaY9diCoiGj75ZLEeOVoTMENcG8iScasN7RYvExe7OWBgs+ZdSiei2X/vo+cu0oi+tQvbQYPLxbEsLy85L6oOXLj03Y/+7nwbepw2YTEpbvPgF+E659zfKQGe7UF+xqPwApV+PzsTwGJMOm51A4bODackajZDkeYKXMVc43ycyplnQFyqYlaNWS8wenue7Pc9DOM8LhiuneV1MyGPNIwfS5HZfMAjjMfLTueTiq2orgs7qTaVQhLt2vLFv/OYWV8WYtHVqbFg2bFAEEdhvIuxA5qQ0VctgReQhlHS6xMCKWptupXkYgCdX/PQSPIURjYlq9+73TdmKixM3n8A4mFm2mrAVu/njEDDyLlWLrpBUvCxGTMLtrfGpsA4g0NW2xxQsWaiwwQksDFDh8/K2K93+Zj1V5dj5MLWERg= x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:CY4PR21MB0182.namprd21.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(396003)(346002)(366004)(39860400002)(376002)(136003)(66476007)(66556008)(64756008)(66446008)(82950400001)(55016002)(66946007)(82960400001)(91956017)(71200400001)(6506007)(8990500004)(76116006)(166002)(9686003)(10290500003)(83380400001)(86362001)(316002)(8676002)(478600001)(52536014)(53546011)(2906002)(4326008)(8936002)(966005)(5660300002)(7696005)(110136005)(26005)(33656002)(186003);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata: =?Windows-1252?Q?IF0jycGCnT9U4HQtWMUAbpZXjJh3tq4xlwnm/SGV6g4QZBe/dZ2pFAtq?= =?Windows-1252?Q?rEpp3YZkosY3+U9M9gvqFY+d/ukqfFpMG9b354GsP+1ImkqfqOC+iDwU?= =?Windows-1252?Q?wuosz+UWcTh5bO3GPztng1Rs3epbCf4eEytN20SeD2b08P+IrYJJFFY1?= =?Windows-1252?Q?fK+wIrQ3bhs5acw5IVPJvScTU+J734HIc7qDc939GemTf7ewwYTckkeE?= =?Windows-1252?Q?uRE8OHILgVSTjDd3MGfEv559rSEn1JH0L+gfwyteiejlY+P3iHgdmwmO?= =?Windows-1252?Q?6nUUhfn2HAIUcSniP1CU10YFDHca8IjEe28aF0O2kYcsToAeeyLYgjAJ?= =?Windows-1252?Q?+Ew+dpZ+h7XYX1ec9wdtXBet1/kwwcAS+amTgn5qNn71aQa2gfhUMSXo?= =?Windows-1252?Q?bvtslpQHaEja+yi/UlfsoTisqNrZKAaREf7fPvA6k+tPlPV9lKH23X/V?= =?Windows-1252?Q?UxhpNzrVovcAmPzFGwxPUgolEO4018/d6rUtlLokoA1CBqNeSXF1Fj/q?= =?Windows-1252?Q?jhdRpoa9P2tfW+Z93JoGL23UUigUEyXU2/NP4wL0cECLQYiMPJkqu2X/?= =?Windows-1252?Q?ZV5bQ4PTl1vOO4LHC47IbkoW8MJy0VCvzYQFjIX8K5VwyjJ9l1J3V/IR?= =?Windows-1252?Q?aV/ve9Y4iVR7ToZcdP9AUuY4lviME16p+jdw7gnITEbTXCG0ihpg0dL5?= =?Windows-1252?Q?A+umWbLTy7vqs4XDSk0eC6WJjzt7JAL18w2kFfpuGFDcr1Hlfa5QdL8p?= =?Windows-1252?Q?siyky8YQR1FZu1ZsE0kHQTD2920diCPJjyGEK3AeUXotSDyoy8mQNAor?= =?Windows-1252?Q?YwHishccZaDLXjLqLGSm1AiCs0LrTtW7L8hZ06liUJzSWkgsRaORxV2+?= =?Windows-1252?Q?oG4XYP4qMXOaxjcUnANWRpJmg4zz2tfGSqVDQ3iCrDNwvN+CwFhChUEz?= =?Windows-1252?Q?GSfxGZJcvPDR46UnP9DOjbxjUjLGWbF8thxnm4eImN+APkD1fuHu6pNo?= =?Windows-1252?Q?uLtMcM5g2sEtYXfqbnYpjkFIjpWod5zdQ8sCh4LmJyvcJApuUph0/GDp?= =?Windows-1252?Q?H1YomWZ3LUDEezZFBFFWhFHBwEF1UW1HV/CfoF0SkJ+yRwm6opqZB2cw?= =?Windows-1252?Q?7GhnzJGWzdXHwIRVUB1GMeKqOQ50Kg7KiavZF6k3qCYuZw=3D=3D?= x-ms-exchange-transport-forked: True MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: CY4PR21MB0182.namprd21.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 3ca2db8b-c355-44d1-d622-08d8bcb141bc X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jan 2021 19:34:36.9553 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 16wQDuv/uTaXevU6CevCC4TK4X3A7I1wcw/TvmNgrze1nw3rBWV/18iumdYgkowpskbUNjBu00nh+Lj6GvH8dQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0504 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_CY4PR21MB0182250B05D3228308C5A9DDEFA39CY4PR21MB0182namp_" --_000_CY4PR21MB0182250B05D3228308C5A9DDEFA39CY4PR21MB0182namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable We=92ve definitely build release pipelines for binaries internally and woul= d be happy to help with this. I like the idea of kicking a new release after a release is tagged. Do you= have any thoughts about how we=92re possibly re-release if there were chan= ges to one of the new stable/* branches, or would it be easier to just cros= s that bridge when we get there? Do you have opinions about Nuget vs other = binary release mechanisms (our experience is with Nuget, but I know there a= re other feed types that we could publish to)? Ideally it would be somethin= g that could be authenticated or compared somehow. - Bret From: Laszlo Ersek via groups.io Sent: Tuesday, January 19, 2021 11:30 AM To: Liming Gao (Byosoft address); Leif Li= ndholm (Nuvia address); Ard Biesheuvel (TianoCore= ); Ni, Ray; Zhic= hao Gao; Abner Chang Cc: edk2-devel-groups-io Subject: [EXTERNAL] [edk2-devel] building the shell for edk2-stable202102 Ouch, I totally forgot to add the mailing list to the address list! Doing that now. Apologies. --o-- Hi All, we've last built the UEFI shell binary for edk2-stable202002 (i.e., almost 1 year ago): https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgith= ub.com%2Ftianocore%2Fedk2%2Freleases%2Ftag%2Fedk2-stable202002&data=3D0= 4%7C01%7Cbret.barkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0bcb0%7= C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637466814561378976%7CUnknown%7C= TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0= %3D%7C1000&sdata=3DObFHM4vr8SuNSLwSwBD95qIvZjt7wRCA54xinkWZeLY%3D&r= eserved=3D0 Note "ShellBinPkg.zip" under Assets -- there is no stable tag that is (a) more recent and (b) whose Assets contain "ShellBinPkg.zip". Contents: > Archive: ShellBinPkg.zip > Length Date Time Name > --------- ---------- ----- ---- > 0 03-06-2020 22:43 ShellBinPkg/MinUefiShell/ > 0 03-06-2020 22:41 ShellBinPkg/MinUefiShell/AArch64/ > 380928 03-06-2020 17:39 ShellBinPkg/MinUefiShell/AArch64/Shell.efi > 0 03-06-2020 22:41 ShellBinPkg/MinUefiShell/Arm/ > 321568 03-06-2020 17:38 ShellBinPkg/MinUefiShell/Arm/Shell.efi > 0 03-05-2020 09:01 ShellBinPkg/MinUefiShell/Ia32/ > 339424 03-05-2020 09:01 ShellBinPkg/MinUefiShell/Ia32/Shell.efi > 643 03-06-2020 22:43 ShellBinPkg/MinUefiShell/MinUefiShell.inf > 0 03-05-2020 09:01 ShellBinPkg/MinUefiShell/X64/ > 392352 03-05-2020 09:01 ShellBinPkg/MinUefiShell/X64/Shell.efi > 0 03-06-2020 22:43 ShellBinPkg/UefiShell/ > 0 03-06-2020 22:41 ShellBinPkg/UefiShell/AArch64/ > 892928 03-06-2020 17:40 ShellBinPkg/UefiShell/AArch64/Shell.efi > 0 03-06-2020 22:41 ShellBinPkg/UefiShell/Arm/ > 791360 03-06-2020 17:39 ShellBinPkg/UefiShell/Arm/Shell.efi > 0 03-05-2020 09:01 ShellBinPkg/UefiShell/Ia32/ > 825184 03-05-2020 09:00 ShellBinPkg/UefiShell/Ia32/Shell.efi > 643 03-06-2020 22:43 ShellBinPkg/UefiShell/UefiShell.inf > 0 03-05-2020 09:01 ShellBinPkg/UefiShell/X64/ > 939648 03-05-2020 09:01 ShellBinPkg/UefiShell/X64/Shell.efi > 0 03-06-2020 22:40 ShellBinPkg/ > --------- ------- > 4884678 21 files I propose that we rebuild the shell for edk2-stable202102. Reasons: (1) There are two small shell features minimally in the latest development cycle: https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgi= thub.com%2Ftianocore%2Ftianocore.github.io%2Fwiki%2FEDK-II-Release-Planning= &data=3D04%7C01%7Cbret.barkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c0= 8d8bcb0bcb0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637466814561378976= %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW= wiLCJXVCI6Mn0%3D%7C1000&sdata=3DsH5nHKgFwcykHgNKm6Nu2esq05F1dKt3t%2BEnc= NyRap8%3D&reserved=3D0 * add file buffering to the UEFI shell's COMP command https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fbu= gzilla.tianocore.org%2Fshow_bug.cgi%3Fid%3D3123&data=3D04%7C01%7Cbret.b= arkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0bcb0%7C72f988bf86f141= af91ab2d7cd011db47%7C1%7C0%7C637466814561378976%7CUnknown%7CTWFpbGZsb3d8eyJ= WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&= sdata=3DPo1VBWyzo7YPioV1FUJZ2t1rB%2FhwgoofX8EH9YKJPBc%3D&reserved=3D0 * Shell: pathname / filename sorting https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fbu= gzilla.tianocore.org%2Fshow_bug.cgi%3Fid%3D3151&data=3D04%7C01%7Cbret.b= arkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0bcb0%7C72f988bf86f141= af91ab2d7cd011db47%7C1%7C0%7C637466814561378976%7CUnknown%7CTWFpbGZsb3d8eyJ= WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&= sdata=3DQz58BSZ7iwNpyD%2BvOayA0VaA0IlDWNz14zwCjxsS6aU%3D&reserved=3D0 (2) The zip file listed above does not contain a RISC-V binary, and RISC-V has been an official UEFI and edk2 platform minimally since edk2-stable202005 / . In particular, the following two platforms in edk2-platforms include the shell (SUPPORTED_ARCHITECTURES =3D RISCV64): Platform/SiFive/U5SeriesPkg/FreedomU500VC707Board/U500.dsc Platform/SiFive/U5SeriesPkg/FreedomU540HiFiveUnleashedBoard/U540.dsc However, as of this writing (@ 6e5586863148), we only have the following list in "Maintainers.txt": > UEFI Shell Binaries (ShellBinPkg.zip) from EDK II Releases: > ----------------------------------------------------------- > W: https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fg= ithub.com%2Ftianocore%2Fedk2%2Freleases%2F&data=3D04%7C01%7Cbret.barkel= ew%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0bcb0%7C72f988bf86f141af91a= b2d7cd011db47%7C1%7C0%7C637466814561388970%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi= MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata= = =3DikDhWcETk90pMfREpPuvAWzobu41W2vUQT9wrRRBhzM%3D&reserved=3D0 > M: Ray Ni (Ia32/X64) > M: Zhichao Gao (Ia32/X64) > M: Leif Lindholm (ARM/AArch64) > M: Ard Biesheuvel (ARM/AArch64) I think that (a) Abner should be added to this list, and (b) we should include a RISC-V shell binary in the upcoming assets. Abner, can you send a patch for "Maintainers.txt" please? Questions: - I'm not clear on how we intend to build the shell binaries -- will we retrieve them from CI / Azure somehow, or is it a manual process? - Given that this is a release activity, I'm unsure where I could file a reminder about it -- clearly, the binaries should be built right after the tag has been made. Should I perhaps file a new reminder BZ for the "N/A" Package, and maybe assign it to Liming (our release manager)? Thanks, Laszlo --_000_CY4PR21MB0182250B05D3228308C5A9DDEFA39CY4PR21MB0182namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

We=92ve definitely build release pipelines for bina= ries internally and would be happy to help with this.

 

I like the idea of kicking a new release after a re= lease is tagged. Do you have any thoughts about how we=92re possibly re-rel= ease if there were changes to one of the new stable/* branches, or would it= be easier to just cross that bridge when we get there? Do you have opinions about Nuget vs other binary relea= se mechanisms (our experience is with Nuget, but I know there are other fee= d types that we could publish to)? Ideally it would be something that could= be authenticated or compared somehow.

 

- Bret

 

 

Ouch, I totally forg= ot to add the mailing list to the address list!
Doing that now. Apologies.

--o--

Hi All,

we've last built the UEFI shell binary for edk2-stable202002 (i.e.,
almost 1 year ago):

  https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub= .com%2Ftianocore%2Fedk2%2Freleases%2Ftag%2Fedk2-stable202002&amp;data= =3D04%7C01%7Cbret.barkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0b= cb0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637466814561378976%7CUnkno= wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC= I6Mn0%3D%7C1000&amp;sdata=3DObFHM4vr8SuNSLwSwBD95qIvZjt7wRCA54xinkWZeLY= %3D&amp;reserved=3D0

Note "ShellBinPkg.zip" under Assets -- there is no stable tag th= at is
(a) more recent and (b) whose Assets contain "ShellBinPkg.zip".<= br>
Contents:

> Archive:  ShellBinPkg.zip
>   Length      Date  &nbs= p; Time    Name
> ---------  ---------- -----   ----
>         0  03-06-2020 22= :43   ShellBinPkg/MinUefiShell/
>         0  03-06-2020 22= :41   ShellBinPkg/MinUefiShell/AArch64/
>    380928  03-06-2020 17:39   ShellBinP= kg/MinUefiShell/AArch64/Shell.efi
>         0  03-06-2020 22= :41   ShellBinPkg/MinUefiShell/Arm/
>    321568  03-06-2020 17:38   ShellBinP= kg/MinUefiShell/Arm/Shell.efi
>         0  03-05-2020 09= :01   ShellBinPkg/MinUefiShell/Ia32/
>    339424  03-05-2020 09:01   ShellBinP= kg/MinUefiShell/Ia32/Shell.efi
>       643  03-06-2020 22:43 &= nbsp; ShellBinPkg/MinUefiShell/MinUefiShell.inf
>         0  03-05-2020 09= :01   ShellBinPkg/MinUefiShell/X64/
>    392352  03-05-2020 09:01   ShellBinP= kg/MinUefiShell/X64/Shell.efi
>         0  03-06-2020 22= :43   ShellBinPkg/UefiShell/
>         0  03-06-2020 22= :41   ShellBinPkg/UefiShell/AArch64/
>    892928  03-06-2020 17:40   ShellBinP= kg/UefiShell/AArch64/Shell.efi
>         0  03-06-2020 22= :41   ShellBinPkg/UefiShell/Arm/
>    791360  03-06-2020 17:39   ShellBinP= kg/UefiShell/Arm/Shell.efi
>         0  03-05-2020 09= :01   ShellBinPkg/UefiShell/Ia32/
>    825184  03-05-2020 09:00   ShellBinP= kg/UefiShell/Ia32/Shell.efi
>       643  03-06-2020 22:43 &= nbsp; ShellBinPkg/UefiShell/UefiShell.inf
>         0  03-05-2020 09= :01   ShellBinPkg/UefiShell/X64/
>    939648  03-05-2020 09:01   ShellBinP= kg/UefiShell/X64/Shell.efi
>         0  03-06-2020 22= :40   ShellBinPkg/
> ---------          =            -------
>   4884678        &n= bsp;            21 f= iles

I propose that we rebuild the shell for edk2-stable202102. Reasons:

(1) There are two small shell features minimally in the latest
    development cycle:

    https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub= .com%2Ftianocore%2Ftianocore.github.io%2Fwiki%2FEDK-II-Release-Planning&= ;amp;data=3D04%7C01%7Cbret.barkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c0= 8d8bcb0bcb0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637466814561378976= %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW= wiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DsH5nHKgFwcykHgNKm6Nu2esq05F1dKt3t%2= BEncNyRap8%3D&amp;reserved=3D0

    * add file buffering to the UEFI shell's COMP command     https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fbugzil= la.tianocore.org%2Fshow_bug.cgi%3Fid%3D3123&amp;data=3D04%7C01%7Cbret.b= arkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0bcb0%7C72f988bf86f141= af91ab2d7cd011db47%7C1%7C0%7C637466814561378976%7CUnknown%7CTWFpbGZsb3d8eyJ= WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&= amp;sdata=3DPo1VBWyzo7YPioV1FUJZ2t1rB%2FhwgoofX8EH9YKJPBc%3D&amp;reserv= ed=3D0

    * Shell: pathname / filename sorting
    https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fbugzil= la.tianocore.org%2Fshow_bug.cgi%3Fid%3D3151&amp;data=3D04%7C01%7Cbret.b= arkelew%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0bcb0%7C72f988bf86f141= af91ab2d7cd011db47%7C1%7C0%7C637466814561378976%7CUnknown%7CTWFpbGZsb3d8eyJ= WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&= amp;sdata=3DQz58BSZ7iwNpyD%2BvOayA0VaA0IlDWNz14zwCjxsS6aU%3D&amp;reserv= ed=3D0

(2) The zip file listed above does not contain a RISC-V binary, and
    RISC-V has been an official UEFI and edk2 platform mini= mally since
    edk2-stable202005 /
    <https://nam06.safelinks.protect= ion.outlook.com/?url=3Dhttps%3A%2F%2Fbugzilla.tianocore.org%2Fshow_bug.cgi%= 3Fid%3D2672&amp;data=3D04%7C01%7Cbret.barkelew%40microsoft.com%7C8e0e9a= 9a97be429c1b6c08d8bcb0bcb0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637= 466814561378976%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI= iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DB6E6J8HHERxZyqgV87n0= vbJgp4NWUSMVN%2FoyaW%2FcF0U%3D&amp;reserved=3D0>.

    In particular, the following two platforms in edk2-plat= forms include
    the shell (SUPPORTED_ARCHITECTURES =3D RISCV64):

      Platform/SiFive/U5SeriesPkg/FreedomU500VC70= 7Board/U500.dsc
      Platform/SiFive/U5SeriesPkg/FreedomU540HiFi= veUnleashedBoard/U540.dsc

    However, as of this writing (@ 6e5586863148), we only h= ave the
    following list in "Maintainers.txt":

> UEFI Shell Binaries (ShellBinPkg.zip) from EDK II Releases:
> -----------------------------------------------------------
> W: https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub= .com%2Ftianocore%2Fedk2%2Freleases%2F&amp;data=3D04%7C01%7Cbret.barkele= w%40microsoft.com%7C8e0e9a9a97be429c1b6c08d8bcb0bcb0%7C72f988bf86f141af91ab= 2d7cd011db47%7C1%7C0%7C637466814561388970%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM= C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sd= ata=3DikDhWcETk90pMfREpPuvAWzobu41W2vUQT9wrRRBhzM%3D&amp;reserved=3D0
> M: Ray Ni <ray.ni@intel.com>      = ;            (Ia32/X= 64)
> M: Zhichao Gao <zhichao.gao@intel.com>    &= nbsp;   (Ia32/X64)
> M: Leif Lindholm <leif@nuviainc.com>    &nb= sp;     (ARM/AArch64)
> M: Ard Biesheuvel <ardb+tianocore@kernel.org> (ARM/AArch64)

    I think that (a) Abner should be added to this list, an= d (b) we
    should include a RISC-V shell binary in the upcoming as= sets.

    Abner, can you send a patch for "Maintainers.txt&q= uot; please?

Questions:

- I'm not clear on how we intend to build the shell binaries -- will we   retrieve them from CI / Azure somehow, or is it a manual process?
- Given that this is a release activity, I'm unsure where I could file a   reminder about it -- clearly, the binaries should be built right af= ter
  the tag has been made.

  Should I perhaps file a new reminder BZ for the "N/A" Pac= kage, and
  maybe assign it to Liming (our release manager)?

Thanks,
Laszlo





 

--_000_CY4PR21MB0182250B05D3228308C5A9DDEFA39CY4PR21MB0182namp_--