• Stars
    star
    143
  • Rank 257,007 (Top 6 %)
  • Language
  • Created over 8 years ago
  • Updated 8 months ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

EDK II new feature staging
This repository is used by EDK II as a staging location for new
features that are not yet ready for inclusion in EDK II.

Introduction
=================
Need place on tianocore.org where new features that are not ready for product 
integration can be checked in for evaluation by the EDK II community prior to 
adding to the edk2 trunk.  This serves several purposes:

* Encourage source code to be shared earlier in the development process
* Allow source code to be shared that does not yet meet all edk2 required quality criteria
* Allow source code to be shared so the EDK II community can help finish and validate new features
* Provide a location to hold new features until they are deemed ready for product integration
* Provide a location to hold new features until there is a natural point in edk2 release cycle to fully validate the new feature.
* Not intended to be used for bug fixes.
* Not intended to be used for small, simple, or low risk features.

Process for creating, using, and maintaining staging efforts
========
[Step 1 is already completed, it is here for documentation purposes; proceed to 2)]
1) Create a new repo called edk2-staging
	a) edk2-staging is a fork of edk2
	b) edk2-staging/master tracks edk2/master

2) edk2-staging discussions can use the existing edk2-devel mailing list for design/patch/test.
	Use the following style for discussion of a specific feature branch in edk2-staging repo.

	[staging/branch]: Subject

3) All commits to edk2-staging must follow same edk2 rules

4) Process to add a new feature to edk2-staging
	a) Maintainer sends patch email to edk2-devel mailing list announcing the creation of a new 
        feature branch in edk2-staging with Readme.MD.  Readme.MD is in root of feature branch 
        with summary, owners, timeline, links to related materials.
	b) Maintainer creates feature branch in edk2-staging
	c) Maintainer is responsible for making sure feature is frequently synced to edk2/master

     NOTE: Feature branch may initially use a stable edk2 tag.  As feature stabilizes, 
           syncs to edk2/master can begin.

5) Process to update sources in feature branch
	a) Commit message subject format:

		[staging/branch PATCH]: Package/Module: Subject

	b) Directly commit changes to feature branch or if community review is desired,
        then use edk2-devel review process.

	NOTE: win32 binaries are not automatically generated if a feature branch includes BaseTools source changes.

6) Process to promote an edk2-staging branch to edk2 trunk
	a) Use edk2 patch review/commit process on edk2-devel mailing list.
        The specific git actions used to add the feature to edk2 is at the discretion 
        of the maintainer(s) doing the merge.  A merge commit must always contain the final
        'Reviewed-by:' tags.
	b) Remove feature branch from edk2-staging and archive at https://github.com/tianocore/edk2-archive.

7) Process to remove an edk2-staging branch
	a) Stewards may periodically review of feature branches in edk2-staging (once a quarter?)
	b) If no activity for extended period of time and feature is no longer deemed a candidate 
        for edk2 then stewards send email to edk2-devel to request deletion of feature branch.  
	c) If no objections from EDK II community, then feature branch is deleted and archived at
        https://github.com/tianocore/edk2-archive.

8) How to evaluate a feature in edk2-staging
	a) Clone edk2
	b) Create local branch with optional platform packages
	c) Build platform in local branch and verify it is stable
	d) Clone edk2-staging/[branch name]
	e) Create local branch with optional platform packages
	f) Build platform in local branch and evaluate new feature

More Repositories

1

edk2

EDK II
C
4,196
star
2

tianocore.github.io

Tianocore website
HTML
1,216
star
3

edk2-platforms

EDK II sample platform branches and tags
C
501
star
4

edk2-libc

Port of libc to EDK II with applications that depend on libc
Python
86
star
5

edk2-test

Test infrastructure and test cases for EDK II based firmware
C
68
star
6

edk2-BaseTools-win32

git-svn mirror of https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32
Batchfile
64
star
7

udk

UEFI Development Kit
C
63
star
8

edk2-non-osi

EDK II non-OSI licensed content
Assembly
57
star
9

edk2-pytool-extensions

Extensions to the edk2 build system allowing for a more robust and plugin based build system and tool execution environment
Python
55
star
10

edk2-pytool-library

Python library package that supports UEFI development
Python
54
star
11

edk2-archive

Archive of old branches for EDK II
C
32
star
12

edk

Git mirror of EDK
C
29
star
13

edk2-basetools

EDK II BaseTools Python tools as a PIP module
Python
23
star
14

buildtools-BaseTools

DEPRECATED. Use BaseTools under EDK II instead.
Python
21
star
15

containers

Repository to maintain and manage edk2 containers
Dockerfile
19
star
16

edk2-share

Python
17
star
17

edk2-edkrepo

Repository for the edkrepo utility
Python
16
star
18

edk-Shell

Older, deprecated EFI Shell
C
13
star
19

edk2-FatPkg

EDK II FatPkg
C
11
star
20

edk2-NetNt32Io

C
9
star
21

edk2-codereview

Temporary repository used to evaluate the GitHub based code review process with a GitHub webhook that generates an email archive of the code review activities.
C
7
star
22

edk2-cmocka

Mirror of https://git.cryptomilk.org/projects/cmocka.git
6
star
23

edk2-edkrepo-manifest

Platforms manifests used by the edkrepo utility
5
star
24

edk2-redfish-client

Utilizes the EFI protocols provided by EDK2 Redfish Foundation to communicate with the Redfish service for creating, consuming, and updating the Redfish properties which are managed by firmware.
C
5
star
25

projects

Empty repository to track all issues associated with TianoCore Projects
1
star