From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A238043B0F; Wed, 14 Feb 2024 22:20:49 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9BE8F42E10; Wed, 14 Feb 2024 22:20:49 +0100 (CET) Received: from mail-oo1-f42.google.com (mail-oo1-f42.google.com [209.85.161.42]) by mails.dpdk.org (Postfix) with ESMTP id 8A22E42E10 for ; Wed, 14 Feb 2024 22:20:47 +0100 (CET) Received: by mail-oo1-f42.google.com with SMTP id 006d021491bc7-59a8ecbadf7so77560eaf.0 for ; Wed, 14 Feb 2024 13:20:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1707945647; x=1708550447; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=l7TKoKsIvDCPgjV5KmpjmeKYRcin3BHAMQcFp/ViPIM=; b=ce52e/TfD0x9ZuYaCHBhPA+qoPx/UzIFMIfbgbWpCQsynQV7vJtsYN2EmnJQybu65J 8H7YtTrNFuoLUFjRjU/+IZ0ZL5JZbIirA56G1CwOsbm+r2+H8QFYhX0LzRGGi+4AvqFa 4GaIRkpn/ztjCyksO77SxgacJezAUIed01QYQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707945647; x=1708550447; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=l7TKoKsIvDCPgjV5KmpjmeKYRcin3BHAMQcFp/ViPIM=; b=A7GP9jjZEc67KYAjJhPTSdqe59ytNQJXGyLRucrihqoX5K8ibvHFMxITT9xWYkMevp vYeE+5/ObzS1MfgSUmMb9oqGmJzOmyR7jkXDfFF9dCdUoBdCtOHpH/AtP0boUdrUE+un EUFz5nygCScqPzroF+dSroCUeOaIOPSs4/1U1tM3LZiihiFUMI3RQjReyjmIfDE+YA3t mBrX021Zosfo1a8QpdBv1DS3aJfnn/jIz+rQ/KXdBLgxi6+Z64uwryCc5+ryRKJXKf1p hxRJZz+MW15T8PZZaR75NW789F7iy8LCu9YjFUsUxDjSmOizoGf1zhZmz6GWju41ndsn mOMQ== X-Forwarded-Encrypted: i=1; AJvYcCUDNjsPS1iKXR9A5EzCZHVk9xX+2UKVx2bWVniaaKrah778cBFtYLxbtEt9vCvQ+f3y5AXQQcaIjtiZtiQ= X-Gm-Message-State: AOJu0Yw6IrSVRMoD5NUMYr9fkENypid43WDosg0eYZs7orvPInwCzd5U VTXrWuidToO1Bp+Upx+X7ejmcm8dTZ+QIGYA2yKonlug6AlD9m5R449V7NNSNhsI9rQsF+Rr+j7 CuFDfNeQyaMRy0iRBNeDT3tOYZY+XJylLue0eaw== X-Google-Smtp-Source: AGHT+IE+y4Z/7vzbSTA8Zwn81uUdpA3ixl8hTJdCeU6ybelKXjHZdVXW5K1hq3+n5FROGJVx/dnj1OdGExWj8tl+0o8= X-Received: by 2002:a4a:2d02:0:b0:59c:d9f1:b931 with SMTP id y2-20020a4a2d02000000b0059cd9f1b931mr3884872ooy.9.1707945646858; Wed, 14 Feb 2024 13:20:46 -0800 (PST) MIME-Version: 1.0 From: Patrick Robb Date: Wed, 14 Feb 2024 16:20:36 -0500 Message-ID: Subject: Rescheduling DPDK CI Meetings To: ci@dpdk.org Cc: dev@dpdk.org, dts@dpdk.org, Nathan Southern Content-Type: multipart/alternative; boundary="00000000000093bb1106115e15b6" X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org --00000000000093bb1106115e15b6 Content-Type: text/plain; charset="UTF-8" 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. --00000000000093bb1106115e15b6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello all,

As discussed in the previous= CI testing meeting, it will be advantageous for us to shift the (every oth= er week) DPDK CI meetings forward or backwards 1 week to get it onto a diff= erent cadence.=C2=A0

That will allow us to have th= e DTS meetings 1 week, and the CI meetings on the off week, instead of both= on the same week, which should yield=C2=A0more valuable conversations.=C2= =A0

So the idea is to have=C2=A0tomorrow's CI = meeting, then have another meeting next Thursday (2/22), then go back to ev= ery other week. So the 2/29 meeting would be cancelled, we would have a 3/7= meeting, a 3/21 meeting, etc.=C2=A0

I am hoping t= his will work well for those of you out there who attend these meetings, bu= t please let me know! If there are no objections, I will request that Natha= n modify the calendar event. Thanks.

=
--00000000000093bb1106115e15b6--