That's a good idea. ------ Original message------ From: Justen, Jordan L Date: Fri, Mar 11, 2016 5:34 PM To: Mangefeste, Tony;edk2-devel@lists.01.org; Cc: Subject:Re: [edk2] EDK2 Staging Repository 2nd Draft
On 2016-03-11 16:25:39, Mangefeste, Tony wrote: > > 6) Process to promote an edk2-staging branch to edk2 trunk > a) Request sent to edk2-devel that describes the feature, design, > testing, etc. > b) Stewards evaluate request and determine if the feature meets edk2 > criteria. > c) If approved, use edk2 patch review/commit process on edk2-devel > mailing list > d) Remove feature branch from edk2-staging (maybe archived > elsewhere?). > > 7) Process to remove an edk2-staging branch > a) Stewards 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 (maybe archived elsewhere?). I recommend we move all committed and abandoned staging branches to: https://github.com/tianocore/edk2-archive Archiving the committed patchsets might not be useful though. -Jordan _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
