From: "Demeter, Miki" <miki.demeter@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"announce@edk2.groups.io" <announce@edk2.groups.io>
Subject: TianoCore Community Meeting 20220602 EMEA/NAMO
Date: Thu, 2 Jun 2022 16:27:33 +0000 [thread overview]
Message-ID: <DS0PR11MB64452B692BB6D61DBF68C8FD8DDE9@DS0PR11MB6445.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
# TianoCore Community Meeting
**Highlights:**
- Stable tag 202205 released
- Call for discussion on versioning components, manifest
- Need to determine what to do about BZ reporters not responding to requests for info
# Meeting Minutes:
1) **Event Updates (_5 minutes]**
- **UEFI Summit Virtual only**
2) [**Stable Tag Updates (_5 minutes_)**
- 2022- Release
-** Stable Tag 202205released **
3) **Stewards Download (_20 minutes_)**
- Not fully attended no real report down
-**Coverity Status**
- No update
-** Bugzilla Status **
- 177 Unconfirmed bugs
- 477 Confirmed
- 158 Unassigned
- 37 In Progress
- Last 7 days 6 issues reported only 2 confirmed
- Last 7 days 8 BZ resolved
Need to determine what to do about BZ reporters not responding to requests for info
4) **Opens (_30 minutes_)**
- Miki - Better Versioning of components., Manifest…
**AR: Michael K reach out to Felix on Coverity status**
Next meeting will be Thursday July 7th
--
Miki Demeter (she/her/Miki)
Security Researcher / FW Developer
FST
Intel Corporation
Portland Women in Tech Best Speaker
miki.demeter@intel.com<mailto:miki.demeter@intel.com>
[-- Attachment #2: Type: text/html, Size: 13583 bytes --]
reply other threads:[~2022-06-02 16:27 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=DS0PR11MB64452B692BB6D61DBF68C8FD8DDE9@DS0PR11MB6445.namprd11.prod.outlook.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