On Sat, 2016-03-12 at 00:25 +0000, 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?).
Anything which is substantial enough to warrant this kind of 'staging' definitely wants to be *pulled* into the main tree, rather than rebasing it onto the current master, losing accurate history and invalidating the testing that's been done. The 'Reviewed-by' and similar tags could be collected by the submitter and added in their own tree (leaving them in control of whether they rebase, and responsible for subsequent retesting everything). Perhaps better still, the Reviewed-by: could be included in the *merge* commit. Either way, let's not further entrench incorrect rebase behaviour. -- David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
