* Re: [PATCH] version: 24.03-rc0
[not found] ` <CAJvnSUCcbcZjeGLB9KRkYsYmH-2Fvq2cHpN5CHRGuK84_yTc5g@mail.gmail.com>
@ 2023-12-01 21:08 ` Thomas Monjalon
2023-12-01 21:24 ` Patrick Robb
0 siblings, 1 reply; 2+ messages in thread
From: Thomas Monjalon @ 2023-12-01 21:08 UTC (permalink / raw)
To: Patrick Robb
Cc: Ferruh Yigit, Bruce Richardson, David Marchand, dev,
Aaron Conole, Michael Santana, Andrew Rybchenko, Ajit Khaparde,
Qi Zhang, Jerin Jacob Kollanukkaran, Raslan Darawsheh,
Maxime Coquelin, Akhil Goyal, ci
01/12/2023 18:24, Patrick Robb:
> For staging branches, Based on TB voting I did add a work item to the 2024
> lab SOW for "on-push" staging branch testing, which we will do via these
> GitHub branches (so like, next-virtio-staging).
Not sure about testing staging branches for next-*.
Each patch is already tested individually.
Then the ready branch for-* is tested again regularly.
I think the staging branch is more for manual testing.
There is also GitHub Actions doing an automatic test.
Instead of "on-push" testing, we could propose a manual trigger
if we want to avoid overloading the lab during critical release times.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] version: 24.03-rc0
2023-12-01 21:08 ` [PATCH] version: 24.03-rc0 Thomas Monjalon
@ 2023-12-01 21:24 ` Patrick Robb
0 siblings, 0 replies; 2+ messages in thread
From: Patrick Robb @ 2023-12-01 21:24 UTC (permalink / raw)
To: Thomas Monjalon
Cc: Ferruh Yigit, Bruce Richardson, David Marchand, dev,
Aaron Conole, Michael Santana, Andrew Rybchenko, Ajit Khaparde,
Qi Zhang, Jerin Jacob Kollanukkaran, Raslan Darawsheh,
Maxime Coquelin, Akhil Goyal, ci
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Fri, Dec 1, 2023 at 4:09 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> 01/12/2023 18:24, Patrick Robb:
> > For staging branches, Based on TB voting I did add a work item to the
> 2024
> > lab SOW for "on-push" staging branch testing, which we will do via these
> > GitHub branches (so like, next-virtio-staging).
>
> Not sure about testing staging branches for next-*.
> Each patch is already tested individually.
> Then the ready branch for-* is tested again regularly.
> I think the staging branch is more for manual testing.
> There is also GitHub Actions doing an automatic test.
> Instead of "on-push" testing, we could propose a manual trigger
> if we want to avoid overloading the lab during critical release times.
>
>
> Okay. I will leave it until Monday for any sub-tree maintainers to chime
in if they disagree. Otherwise, I will remove the staging branch testing
work item, and add in a work item for adding a manual trigger. Thanks.
[-- Attachment #2: Type: text/html, Size: 1344 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-12-01 21:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20231129161858.997576-1-david.marchand@redhat.com>
[not found] ` <dcd829c9-6ec4-4fd5-b05b-720fcfce0393@amd.com>
[not found] ` <CAJvnSUCcbcZjeGLB9KRkYsYmH-2Fvq2cHpN5CHRGuK84_yTc5g@mail.gmail.com>
2023-12-01 21:08 ` [PATCH] version: 24.03-rc0 Thomas Monjalon
2023-12-01 21:24 ` Patrick Robb
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).