Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Neal Caidin <ncaidin@linuxfoundation.org>,
	yocto@lists.yoctoproject.org,
	openembedded-core@lists.openembedded.org
Cc: Stephen Jolley <sjolley.yp.pm@gmail.com>
Subject: Re: [yocto] Yocto Project Status 31 October 2023 (WW44)
Date: Tue, 31 Oct 2023 14:33:17 +0100	[thread overview]
Message-ID: <b5624398-79ea-4838-ace2-774fac6f787a@bootlin.com> (raw)
In-Reply-To: <CAODMxsJ2Wsd6fURK_JLP-YTtOSqVknZnJ87BNN8jVOGQ4J_=Bw@mail.gmail.com>

Greetings,

On 31.10.23 at 13:29, Neal Caidin wrote:
>
> Current Dev Position: YP 4.3 M4 (Feature Freeze)
>
> Next Deadline: 2nd October 2023 YP 4.3 M4 build date
>
>
> Next Team Meetings:
>
>  *
>
>     Bug Triage meeting Thursday November 2, 7:30 am PDT
>     (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09
>     <https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>)
>
>  *
>
>     Weekly Project Engineering Sync Tuesday October 31st at 8 am PDT
>     (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
>     <https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>)
>     <https://zoom.us/j/990892712>
>

Reminder: this week 8:00 PDT translates to 16:00 CET if I understood 
correctly. That's one hour earlier because daylight saving time changes 
happen in Europe 1 week earlier than in the USA.

Michael.
-- 

Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2023-10-31 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 12:29 Yocto Project Status 31 October 2023 (WW44) Neal Caidin
2023-10-31 13:33 ` Michael Opdenacker [this message]
2023-10-31 13:50   ` [yocto] " Neal Caidin
2023-11-03  2:20 ` [OE-core] " Tim Orling

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=b5624398-79ea-4838-ace2-774fac6f787a@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=ncaidin@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=yocto@lists.yoctoproject.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