Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update EDK II Code First Process for GitHub Issues #84

Open
makubacki opened this issue Mar 3, 2025 · 4 comments
Open

Update EDK II Code First Process for GitHub Issues #84

makubacki opened this issue Mar 3, 2025 · 4 comments
Assignees

Comments

@makubacki
Copy link
Member

makubacki commented Mar 3, 2025

The EDK II Code First Process is defined in EDK II Code First Process.

After the transition from Bugzilla to GitHub issues, the code first process needs to be revised to accommodate GitHub issues. This issue identifies the areas that must be updated with a proposal for those updates.

Please provide feedback if something is missing or you have other suggestions.


  1. Replace the BZ#### identifier with GI####.
    • BZ#### previously referred to the Bugzilla ID for the code first entry.
    • GI#### refers to a GitHub issue ID for the code first entry.
      • A single GitHub issue is used to track all activity related to the code first item. This issue might link to multiple pull requests, attached documents, conversations, and links to other places.
      • The GitHub issue is filed in the repository most relevant for the code first change. Usually this will be the edk2 repository.
  2. Add a dedicated "Code First" GitHub issue form to accept code first tracking issues.
    • This will be tailored for the code first process, such as having a required field with a template for the draft specification update.
  3. Add a type:code-first label to all GitHub issues submitted with the "Code First" template.
    • Only a single "Code First" template exists that covers "Code First Spec" and
      "Code First Implementation".
      • "Code First Implementation" is implied by the code links added to the issue.
    • Code first issues migrated from Bugzilla should manually have the type:code-first labels added for consistency.
  4. Update EDK-II-Code-First-Process.md on the TianoCore wiki with the new process.
@makubacki makubacki self-assigned this Mar 3, 2025
@makubacki
Copy link
Member Author

makubacki commented Mar 3, 2025

@samerhaj
Copy link

samerhaj commented Mar 3, 2025

Thanks @makubacki . The link you provided is broken, but I was able to see the changes here: master...makubacki:tianocore.github.io:update_code_first_process

Looks good!

@makubacki
Copy link
Member Author

Thanks @makubacki . The link you provided is broken, but I was able to see the changes here: master...makubacki:tianocore.github.io:update_code_first_process

Looks good!

Thanks. I had a period at the end the URL and just fixed it.

@leiflindholm
Copy link
Member

The text in 4 looks good. I added one comment. But it kind of depends on 2 being in place.

One more thing we might need to do is look at whether there are any in-flight branches in edk2-staging (most recently modified I spot is 7 months since last update, so maybe not, but...).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants