From: "Rebecca Cran" <rebecca@bsdio.com>
To: Gerd Hoffmann <kraxel@redhat.com>, devel@edk2.groups.io
Cc: michael.d.kinney@intel.com, "Marvin Häuser" <mhaeuser@posteo.de>
Subject: Re: [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label
Date: Fri, 17 Mar 2023 04:48:15 -0600 [thread overview]
Message-ID: <45969938-96c1-0fa6-b39f-61b7df2e0a03@bsdio.com> (raw)
In-Reply-To: <20230317093347.gi65s3qu5vzzilzn@sirius.home.kraxel.org>
Talking about mailing lists, I'm still disappointed that we lost so much
history of discussion and reviews around the project when the edk2-devel
archive at lists.01.org was deleted.
I've sometimes wanted to go back and take a look at the review history
of a certain commit only to find it's been lost.
--
Rebecca Cran
On 3/17/23 3:33 AM, Gerd Hoffmann wrote:
> On Thu, Mar 16, 2023 at 01:59:49PM -0600, Rebecca Cran wrote:
>> Is this still a requirement since Laszlo's departure from the project?
>>
>> I seem to recall it was him who made it a sticking point of moving to a
>> GitHub PR workflow originally with the requirement to have emails of
>> everything.
> I think it is very useful to have everything on the mailing list for
> a number of reasons:
>
> (1) In my experience reviewing patches, especially more complex ones,
> works better in email than in github PR workflows.
> (2) github doesn't preserve stuff like a mail archive does. When a
> patch series goes through multiple revision github only preserves
> the latest revision which was actually merged.
> (3) Search engines seem to be better in indexing mail list archives
> than github pull requests.
>
> Nevertheless I see some room for improvement in our current workflow.
> Developers often open a PR anyway for to run the CI. So maybe we could
> automate sending the emails and also avoid running CI twice by avoiding
> both developer and maintainer opening a PR, with a workflow like this:
>
> * developer opens a draft PR to run CI for the patch series.
> * when the series passes CI and is ready un-draft the PR.
> * github action sends the patch series to the edk2-devel list
> for review (maybe only after CI passed ...).
> * patch review happens on the list.
> * in case the developer pushes updates to the branch in response to
> review comments the github action posts v2/v3 of the series too.
> * once review is done merge the PR.
>
> take care,
> Gerd
>
next prev parent reply other threads:[~2023-03-17 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 20:02 [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label Michael D Kinney
2023-03-15 22:24 ` [edk2-devel] " Marvin Häuser
2023-03-15 22:34 ` Michael D Kinney
2023-03-16 19:54 ` Marvin Häuser
2023-03-16 19:59 ` Rebecca Cran
2023-03-17 9:33 ` Gerd Hoffmann
2023-03-17 10:36 ` Rebecca Cran
2023-03-17 10:48 ` Rebecca Cran [this message]
[not found] ` <174D2F2BAAB7643C.10271@groups.io>
2023-03-17 10:57 ` Rebecca Cran
2023-03-17 15:27 ` Michael D Kinney
-- strict thread matches above, loose matches on Subject: below --
2023-03-17 12:32 Marvin Häuser
2023-03-17 12:57 ` Rebecca Cran
2023-03-17 13:44 ` Gerd Hoffmann
2023-03-17 14:08 ` Marvin Häuser
2023-03-17 14:20 ` Rebecca Cran
2023-03-17 15:37 ` Michael D Kinney
2023-03-17 14:22 ` Rebecca Cran
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=45969938-96c1-0fa6-b39f-61b7df2e0a03@bsdio.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