From: stephano <stephano.cetola@linux.intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: [edk2-announce] Community Bug Triage
Date: Mon, 4 Feb 2019 13:11:36 +0100 [thread overview]
Message-ID: <8532059e-7c91-55f9-5029-aad2d4adf3c5@linux.intel.com> (raw)
We will begin community bug triage this month. The first meeting will be
this Friday the 8th (Thursday US time). Details are available here:
https://www.tianocore.org/bug-triage
The meetings are held every other week. The first triage is held on
Friday (Shanghai time), and the second will be on the following Monday
(Europe/US time).
I made the Europe meeting Monday rather than Friday as I assume those in
Europe would *not* like a 4pm Friday bug triage. If I am incorrect and
you would all like to meet at 4pm on Fridays, please respond to this
email and let me know.
I will create a Bugzilla list so that we can all follow long with the
triage without requiring anyone to share screens. Since the meeting is
held on Zoom, screenshare will be available for those who can.
Ping me if you have any questions.
Cheers,
Stephano
reply other threads:[~2019-02-04 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list 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=8532059e-7c91-55f9-5029-aad2d4adf3c5@linux.intel.com \
--to=devel@edk2.groups.io \
/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