From: "Demeter, Miki" <miki.demeter@intel.com>
To: "announce@edk2.groups.io" <announce@edk2.groups.io>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: TianoCore Community Meeting Minutes - January 2022
Date: Thu, 13 Jan 2022 17:43:28 +0000 [thread overview]
Message-ID: <BFCF7C71-D62D-4DFE-B658-F8D7AD36D410@intel.com> (raw)
# TianoCore Community Meeting
**Highlights:**
- Updates upcoming on the new PR review Process
- Doxygen parsing EDK 2 files still work in progress for live documentation
- No problems reported using Uncrustify
- 729 open Bugs, they are not getting fixed, getting triaged and assigned but not getting work. (Miki to look into getting more focus on real open bugs)
- Open discussion with community on supported tools
# Meeting Minutes:
1) **Event Updates (_5 minutes]**
- **UEFI Summit shifting to Virtual Event**
- Call for presenters out now
-Python 2 support removed
2) **Stable Tag Updates (_5 minutes_)**
- Stable Tag [edk2-stable202111](https://github.com/tianocore/edk2/releases/tag/edk2-stable202111)
- [Hard freeze was extended for Uncrustify changes](https://edk2.groups.io/g/announce/message/274) - ETA Dec 3rd
- Stable Tag [edk2-stable202202](https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning) Proposed Schedule
- 2021-11-26 Beginning of development
- 2022-02-07 Soft Feature Freeze
- 2022-02-11 Hard Feature Freeze
- 2022-02-25 Release
3) **Stewards Download (_20 minutes_)**
- Ongoing work implementing the Admin view
- Updates upcoming on the new PR review Process - This
4) **Opens (_30 minutes_)**
- Doxygen parsing EDK 2 files still work in progress {Rebecca and Michael K)
- Update for uncrustfy - File diff what are the actual lines that need attention. (Rececca and Michael Kubacki)
- Base tools - need input from community about removal and moving to pip install version
- Future moving off of Bugzilla
- 729 open Bugs, they are not getting fixed, getting triaged and assigned but not getting work. (Miki to look into getting more focus on real open bugs)
- Open Discussion about sunsetting for CI VS-2017 and moving CI to VS-2022
- Open Discussion toolsdef about the removal of some of the tools listed moved unused tools to separate file
--
Miki Demeter (she/her)
Intel Corporation
reply other threads:[~2022-01-13 17:43 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=BFCF7C71-D62D-4DFE-B658-F8D7AD36D410@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