DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev <dev@dpdk.org>, dts@dpdk.org
Subject: Re: DPDK CI Testing Meeting schedule updates
Date: Wed, 11 Dec 2024 09:57:27 -0500	[thread overview]
Message-ID: <CAJvnSUCL3a4BVXp-6b7cdNm0Tt4GCqpzzOcsGLL-iZJgnwnawQ@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUBH_y8t-YhuEkfjeM1zuJ9YrmCYTJirf2yJNRBYe4w+8w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On Mon, Nov 25, 2024 at 10:47 AM Patrick Robb <probb@iol.unh.edu> wrote:

> Hello,
>
> I have a couple reminders/updates for the schedule of the upcoming DPDK CI
> Testing meetings.
>
> 1. The meeting which was scheduled to happen this Thursday, November 28,
> is cancelled due to the American Thanksgiving Holiday. To "make up" for
> this, I will add a brief CI Labs discussion topic to the DTS meeting
> happening next Thursday, November 5.
>
> 2. There is a conflict between the November 12 DPDK Ci Meeting, and a
> joint Governing Board and Tech Board meeting about 2025 objectives. I am
> moving the DPDK CI meeting back 1 hour to 15:00 UTC to avoid this conflict.
> Ensuing meetings will return to the normal 14:00 UTC timeslot.
>
> Correction, I meant December 12 (tomorrow), not November 12.



> 3. The December 26 DPDK CI meeting is cancelled due to Winter Holidays.
>
> Since a number of CI meetings are being affected due to randomness, and
> the DTS meetings are relatively unaffected, I will be sure to leave some
> space for CI lab discussion during those DTS meetings.
>
> Thanks.
>
>

[-- Attachment #2: Type: text/html, Size: 1794 bytes --]

      reply	other threads:[~2024-12-11 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 15:47 Patrick Robb
2024-12-11 14:57 ` Patrick Robb [this message]

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=CAJvnSUCL3a4BVXp-6b7cdNm0Tt4GCqpzzOcsGLL-iZJgnwnawQ@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dts@dpdk.org \
    /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).