Yes there is work that is substantial enough.
------ Original message------
From: David Woodhouse
Date: Mon, Mar 14, 2016 3:19 PM
To: Mangefeste, Tony;edk2-devel@lists.01.org<mailto:;edk2-devel@lists.01.org>;
Cc:
Subject:Re: [edk2] EDK2 Staging Repository 2nd Draft
On Sat, 2016-03-12<tel: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
thanrebasing it onto the current master, losing accurate history
andinvalidating the testing that's been done.Th<http://done.Th>e 'Reviewed-by'
and similar tags could be collected by the submitterand added in their own tree
(leaving them in control of whether theyrebase, 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
centredavid.woodho...@intel.com<mailto:%20centredavid.woodho...@intel.com>
Intel Corporation
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
