Skip to content

Update EDK II Code First Process for GitHub Issues #84

@makubacki

Description

@makubacki

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions