From: Patrick Robb <probb@iol.unh.edu>
To: ci@dpdk.org
Cc: dev@dpdk.org, dts@dpdk.org
Subject: Re: Rescheduling DPDK CI Meetings
Date: Thu, 15 Feb 2024 13:47:13 -0500 [thread overview]
Message-ID: <CAJvnSUDCc5_ECH3O7BY9ezUNXsHcCQ2Zf_O4HE=ot-nSHy-m2Q@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUDyNg5Gtq3=Z5ZcUg-9dq7fB0u63=QyHNzJwsrWPmkp1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Hi,
This is finalized. The next CI meeting will be next Thursday. Then we go
back to every other week.
On Wed, Feb 14, 2024 at 4:20 PM Patrick Robb <probb@iol.unh.edu> wrote:
> Hello all,
>
> As discussed in the previous CI testing meeting, it will be advantageous
> for us to shift the (every other week) DPDK CI meetings forward or
> backwards 1 week to get it onto a different cadence.
>
> That will allow us to have the DTS meetings 1 week, and the CI meetings on
> the off week, instead of both on the same week, which should yield more
> valuable conversations.
>
> So the idea is to have tomorrow's CI meeting, then have another meeting
> next Thursday (2/22), then go back to every other week. So the 2/29 meeting
> would be cancelled, we would have a 3/7 meeting, a 3/21 meeting, etc.
>
> I am hoping this will work well for those of you out there who attend
> these meetings, but please let me know! If there are no objections, I will
> request that Nathan modify the calendar event. Thanks.
>
>
[-- Attachment #2: Type: text/html, Size: 1476 bytes --]
prev parent reply other threads:[~2024-02-15 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 21:20 Patrick Robb
2024-02-15 18:47 ` 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='CAJvnSUDCc5_ECH3O7BY9ezUNXsHcCQ2Zf_O4HE=ot-nSHy-m2Q@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).