> On 03/15/16 18:20, Kinney, Michael D wrote:
> I don't object to pulling, if the submitter explicitly requests it, and
> if we're making this option official now.
Let's say "at the discretion of the person doing the merge" rather than
writing down that it should need an explicit request.
Over
se
>> Sent: Tuesday, March 15, 2016 3:50 AM
>> To: Kinney, Michael D <michael.d.kin...@intel.com>; Mangefeste, Tony
>> <tony.mangefe...@intel.com>; edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
>> Subject: Re: [edk2] EDK2 Staging Repository 2nd Draft
>&g
<michael.d.kin...@intel.com>; Mangefeste, Tony
> <tony.mangefe...@intel.com>; edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
> Subject: Re: [edk2] EDK2 Staging Repository 2nd Draft
>
> On Tue, 2016-03-15 at 00:16 +, Kinney, Michael D wrote:
> >
> >
&g
On Tue, 2016-03-15 at 00:16 +, Kinney, Michael D wrote:
>
>
> Can you provide some revised text you would like to see in step 6.
>
> I agree that we need to use the tools in ways that help make this easy,
> prevent
> errors, and preserve history. Given that step 6 describes promoting a
>
> de...@ml01.01.org>
> Subject: Re: [edk2] EDK2 Staging Repository 2nd Draft
>
> On Mon, 2016-03-14 at 22:38 +, Mangefeste, Tony wrote:
> > Yes there is work that is substantial enough.
>
> I'm not sure what that's an answer to; you didn't leave a specific part
>
On Mon, 2016-03-14 at 22:38 +, Mangefeste, Tony wrote:
> Yes there is work that is substantial enough.
I'm not sure what that's an answer to; you didn't leave a specific part
of my email above it as context.
I was saying that *when* work is substantial enough to warrant such
staging, that is
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 at
On Sat, 2016-03-12 at 00:25 +, 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
>
On Sat, 2016-03-12 at 00:25 +, Mangefeste, Tony wrote:
>
> Problem statement
> =
> 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
[edk2] EDK2 Staging Repository 2nd Draft
Importance: High
After collecting numerous feedback, here's a clean 2nd proposal for review.
* Message format clean
* Approval process updates for stanging -> EDK2 trunk
* The intention of the staging branch is _not_ to work on features that grow to
unr
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 a
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.
>
After collecting numerous feedback, here's a clean 2nd proposal for review.
* Message format clean
* Approval process updates for stanging -> EDK2 trunk
* The intention of the staging branch is _not_ to work on features that grow to
unreasonable sizes. It is to manage features in an isolated
On 03/10/16 19:29, Kinney, Michael D wrote:
>> -Original Message-
>> From: Laszlo Ersek [mailto:ler...@redhat.com]
>> Keeping work-in-progress modules in a separate repo has a critical
>> drawback: those modules will not share the commit history of the main
>> edk2 repo.
>
> The issue
t;;
> edk2-
> de...@lists.01.org <edk2-de...@ml01.01.org>
> Subject: Re: [edk2] EDK2 Staging Repository
>
> On 03/10/16 00:02, Kinney, Michael D wrote:
> > Jordan,
> >
> > Responses included below.
> >
> > Mike
> >
> >
> >
&g
efe...@intel.com>; Gerd Hoffmann
<kra...@redhat.com>; Bruce Cran <br...@cran.org.uk>
Cc: Justen, Jordan L <jordan.l.jus...@intel.com>; edk2-devel@lists.01.org
<edk2-de...@ml01.01.org>
Subject: Re: [edk2] EDK2 Staging Repository
On 03/10/16 17:55, Mangefeste, Tony wrote:
> Thi
On 03/10/16 17:55, Mangefeste, Tony wrote:
> This is fantastic, because the other two things I would like for us all to
> consider is Gerrit+Jenkins support.
Sorry for repeating myself :(, but:
Please make sure that all reviews done on the web are forwarded to the
mailing list, and that I can
On 3/10/16 9:55 AM, Mangefeste, Tony wrote:
This is fantastic, because the other two things I would like for us all to
consider is Gerrit+Jenkins support.
Why Gerrit? Everyone I've seen talk about it hate its UI.
FWIW I seem to be leading a bit of a rebellion at $work, since I setup a
demo
;br...@cran.org.uk>
Cc: Justen, Jordan L <jordan.l.jus...@intel.com>; Mangefeste, Tony
<tony.mangefe...@intel.com>; edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
Subject: Re: [edk2] EDK2 Staging Repository
On Mi, 2016-03-09 at 16:57 -0700, Bruce Cran wrote:
> On 3/9/16 2
y, March 9, 2016 1:47 PM
>> To: Mangefeste, Tony <tony.mangefe...@intel.com>; edk2-devel@lists.01.org
>> Subject: Re: [edk2] EDK2 Staging Repository
>>
>> On 2016-03-09 10:53:38, Mangefeste, Tony wrote:
>>> Below are the details of the proposal for
On Mi, 2016-03-09 at 16:57 -0700, Bruce Cran wrote:
> On 3/9/16 2:59 PM, Jordan Justen wrote:
>
> > So far I have a setup that can test building BaseTools and OVMF on
> > Linux. The Windows setup is a little more complicated, but I don't
> > think it should be too difficult.
>
> I guess that's
On 2016-03-09 16:36:04, Kinney, Michael D wrote:
> > -Original Message-
> > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> > Jordan Justen
> >
> > On 2016-03-09 15:02:41, Kinney, Michael D wrote:
> > >
> > > Package maintainers are involved in the code review of
dk2-devel@lists.01.org; Kinney, Michael D
> <michael.d.kin...@intel.com>
> Subject: Re: [edk2] EDK2 Staging Repository
>
> On 2016-03-09 15:02:41, Kinney, Michael D wrote:
> >
> > > -Original Message-
> > > From: edk2-devel [mailto:edk2-devel-boun...@
On 2016-03-09 15:02:41, Kinney, Michael D wrote:
>
> > -Original Message-
> > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> > Jordan Justen
> >
> > On 2016-03-09 10:53:38, Mangefeste, Tony wrote:
> > >
> > > Proposal
> > >
> > > 1) Create a new repo
On 3/9/16 2:59 PM, Jordan Justen wrote:
So far I have a setup that can test building BaseTools and OVMF on
Linux. The Windows setup is a little more complicated, but I don't
think it should be too difficult.
I guess that's Linux x86_64? Any solution we come up with should also be
extendable
half Of
>> Jordan Justen
>> Sent: Wednesday, March 9, 2016 1:47 PM
>> To: Mangefeste, Tony <tony.mangefe...@intel.com>; edk2-devel@lists.01.org
>> Subject: Re: [edk2] EDK2 Staging Repository
>>
>> On 2016-03-09 10:53:38, Mangefeste, Tony wrote:
>
On 2016-03-09 11:15:21, Bruce Cran wrote:
> On 3/9/16 11:53 AM, Mangefeste, Tony wrote:
> > Below are the details of the proposal for a staging branch, please review
> > and comment.
> >
> >
> >
> > Problem statement
> > =
> > Need place on tianocore.org where new features that
On 2016-03-09 10:53:38, Mangefeste, Tony wrote:
> Below are the details of the proposal for a staging branch, please review and
> comment.
>
>
>
> Problem statement
> =
> Need place on tianocore.org where new features that are not ready for product
> integration can be checked
Below are the details of the proposal for a staging branch, please review and
comment.
Problem statement
=
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
29 matches
Mail list logo
