From: Patrick Robb <probb@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Ferruh Yigit <ferruh.yigit@amd.com>,
Bruce Richardson <bruce.richardson@intel.com>,
David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Akhil Goyal <gakhil@marvell.com>,
ci@dpdk.org
Subject: Re: [PATCH] version: 24.03-rc0
Date: Fri, 1 Dec 2023 16:24:28 -0500 [thread overview]
Message-ID: <CAJvnSUBvJoOfCLLraxraGeAFuerjCEprdjnwXEhHP9GCwyq61Q@mail.gmail.com> (raw)
In-Reply-To: <2163541.irdbgypaU6@thomas>
[-- 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 --]
next prev parent reply other threads:[~2023-12-01 21:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 16:18 David Marchand
2023-11-30 9:23 ` David Marchand
2023-11-30 9:30 ` Ferruh Yigit
2023-11-30 9:32 ` David Marchand
2023-11-30 9:53 ` David Marchand
2023-11-30 10:05 ` Ferruh Yigit
2023-11-30 18:33 ` Patrick Robb
2023-12-01 8:04 ` Thomas Monjalon
2023-12-01 8:55 ` David Marchand
2023-12-01 10:32 ` Thomas Monjalon
2023-12-01 10:39 ` David Marchand
2023-12-01 11:13 ` Bruce Richardson
2023-12-01 11:33 ` Ferruh Yigit
2023-12-01 14:30 ` Bruce Richardson
2023-12-01 16:36 ` Ferruh Yigit
2023-12-01 17:24 ` Patrick Robb
2023-12-01 17:32 ` Bruce Richardson
2023-12-01 21:08 ` Thomas Monjalon
2023-12-01 21:24 ` Patrick Robb [this message]
2023-12-07 9:55 ` David Marchand
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-all 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=CAJvnSUBvJoOfCLLraxraGeAFuerjCEprdjnwXEhHP9GCwyq61Q@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=maicolgabriel@hotmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).