From: "Michael Kubacki via groups.io" <mikuback=linux.microsoft.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>, announce@edk2.groups.io
Subject: [edk2-devel] EDK II Code First Process Change
Date: Fri, 7 Mar 2025 14:47:19 -0500 [thread overview]
Message-ID: <9ce773f5-52a5-4252-980e-5b304bf62586@linux.microsoft.com> (raw)
The EDK II Code First Process defined on this TianoCore wiki page has
been updated for GitHub issues in addition to some other changes to
provide more flexibility in the process.
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Code-First-Process
Key changes:
1. Code first issues are tracked with a GitHub issue instead of a
Bugzilla item.
2. Code first changes are always submitted in a GitHub draft PR.
3. The code first changes in the draft PR may reside in a branch on a
fork or a branch in edk2-staging.
4. The process to request write permissions for collaborators to push to
edk2-staging, if that option is preferred, is defined.
5. "GI" is used instead of "BZ" in places like branch names and code
tags while the change is in the draft state (prior to specification
changes being published).
Note: The requirement to tag source code names is under consideration
for removal but is still required at this time.
Thanks to Leif Lindholm, Mike Kinney, and Sean Brogan for reviewing and
providing feedback for the new process.
Please let me know if there are any questions or feedback.
Thanks,
Michael
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121163): https://edk2.groups.io/g/devel/message/121163
Mute This Topic: https://groups.io/mt/111574454/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2025-03-07 19:47 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=9ce773f5-52a5-4252-980e-5b304bf62586@linux.microsoft.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