public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Liming Gao <liming.gao@intel.com>, devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [Patch] Maintainers.txt: Move ShellBin maintainers to EDK II Releases section
Date: Tue, 24 Sep 2019 19:26:45 +0200	[thread overview]
Message-ID: <e48bf337-0482-ea21-cf6e-289c9ad16f2f@redhat.com> (raw)
In-Reply-To: <1569287994-7660-1-git-send-email-liming.gao@intel.com>

Hi Liming,

On 09/24/19 03:19, Liming Gao wrote:
> ShellBinPkg is generated for each edk2 stable tag release.
> 
> Cc: Andrew Fish <afish@apple.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Signed-off-by: Liming Gao <liming.gao@intel.com>
> ---
>  Maintainers.txt | 13 ++++++-------
>  1 file changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/Maintainers.txt b/Maintainers.txt
> index f348d70df3..f75b35d5a8 100644
> --- a/Maintainers.txt
> +++ b/Maintainers.txt
> @@ -82,6 +82,12 @@ EDK II Releases:
>  W: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
>  M: Liming Gao <liming.gao@intel.com>
>  
> +W: https://github.com/tianocore/edk2/releases/download/edk2-stable20XXXX/ShellBinPkg.zip

I'm not a fan of this link. It contains "XXXX", therefore it cannot work
with a simple click (or copy & paste). And it's not easy to notice the
"XXXX" part, and to substitute a valid stable tag identifier for it.

All the links we provide should work without manual tweaking, in my
opinion. They might not provide an immediately downloadable file (which
is fine with me), but they should not result in a 404.

How about the following:

UEFI Shell Binaries (ShellBinPkg.zip) from EDK II Releases:
-----------------------------------------------------------
W: https://github.com/tianocore/edk2/releases/
M: ...
M: ...
M: ...
M: ...

This allows users to go to the releases page, and search that page for
"ShellBinPkg.zip".

For me, the "Assets" block of the latest release is open immediately,
upon loading the page, and so searching the page for "ShellBinPkg.zip"
provides a hit at once. If a user wants an older build, they can locate
the Assets blocks under older releases, and look for "ShellBinPkg.zip"
there.

Thanks
Laszlo

> +M: Ray Ni <ray.ni@intel.com>                  (Ia32/X64)
> +M: Zhichao Gao <zhichao.gao@intel.com>        (Ia32/X64)
> +M: Leif Lindholm <leif.lindholm@linaro.org>   (ARM/AArch64)
> +M: Ard Biesheuvel <ard.biesheuvel@linaro.org> (ARM/AArch64)
> +
>  EDK II Architectures:
>  ---------------------
>  ARM, AARCH64
> @@ -421,13 +427,6 @@ W: https://github.com/tianocore/tianocore.github.io/wiki/ShellPkg
>  M: Ray Ni <ray.ni@intel.com>
>  M: Zhichao Gao <zhichao.gao@intel.com>
>  
> -Maintainers for stable Shell binaries generation
> -when need to publish Shell binaries with edk2 release:
> -M: Ray Ni <ray.ni@intel.com>                  (Ia32/X64)
> -M: Zhichao Gao <zhichao.gao@intel.com>        (Ia32/X64)
> -M: Leif Lindholm <leif.lindholm@linaro.org>   (ARM/AArch64)
> -M: Ard Biesheuvel <ard.biesheuvel@linaro.org> (ARM/AArch64)
> -
>  SignedCapsulePkg
>  F: SignedCapsulePkg/
>  W: https://github.com/tianocore/tianocore.github.io/wiki/SignedCapsulePkg
> 


  parent reply	other threads:[~2019-09-24 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  1:19 [Patch] Maintainers.txt: Move ShellBin maintainers to EDK II Releases section Liming Gao
2019-09-24 10:41 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-09-24 15:08   ` Liming Gao
2019-09-24 15:12     ` Philippe Mathieu-Daudé
2019-09-24 15:17       ` Liming Gao
2019-09-24 15:25         ` Philippe Mathieu-Daudé
2019-09-24 17:17   ` Laszlo Ersek
2019-09-24 17:26 ` Laszlo Ersek [this message]
2019-09-25  0:43   ` Liming Gao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e48bf337-0482-ea21-cf6e-289c9ad16f2f@redhat.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox