building the shell for edk2-stable202102

["Laszlo Ersek" <lersek@redhat.com>]

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://github.com/tianocore/edk2/releases/tag/edk2-stable202002

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://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

    * add file buffering to the UEFI shell's COMP command
    https://bugzilla.tianocore.org/show_bug.cgi?id=3123

    * Shell: pathname / filename sorting
    https://bugzilla.tianocore.org/show_bug.cgi?id=3151

(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 /
    <https://bugzilla.tianocore.org/show_bug.cgi?id=2672>.

    In particular, the following two platforms in edk2-platforms include
    the shell (SUPPORTED_ARCHITECTURES = 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://github.com/tianocore/edk2/releases/
> M: Ray Ni <ray.ni@intel.com>                  (Ia32/X64)
> M: Zhichao Gao <zhichao.gao@intel.com>        (Ia32/X64)
> M: Leif Lindholm <leif@nuviainc.com>          (ARM/AArch64)
> M: Ard Biesheuvel <ardb+tianocore@kernel.org> (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