> On Mar 16, 2016, at 3:05 PM, Kinney, Michael D <[email protected]> > wrote: > > David, > > I responded to an earlier email: > > ================================== > I think there are several methods we can support for development. > > 1) Simple bug fixes/features sent directly to edk2-devel for PRs. > 2) A larger or more complex bug fix/feature can optionally post a link > to a branch on personal github fork to help simplify the review process > for those reviewers that prefer to use that method. This type of bug > fix or feature is usually owned by a single subject matter expert. > 3) A larger or more complex feature that requires design/dev/test by more > than one subject matter expert. > > We already support (1) and (2) today. Feature branches on edk2-staging are > intended for (3). > > I can think of a couple ways we end up in (3). The first is a feature we know > requires multiple subject matter experts and the request is made to add > to edk2-staging from the beginning. The second is a PR that is sent to > edk2-devel, and the community believes it needs more design/dev/test work > that requires cooperation of multiple subject matter experts and the PR > is re-directed to a feature branch in edk2-staging.
I think David's point is any github repository can be used for this, if I understand David's point? So the only value to branches is an official place for them to live? Thus a way they can be discovered. Thanks, Andrew Fish > ================================== > > Mike > >> -----Original Message----- >> From: edk2-devel [mailto:[email protected]] On Behalf Of David >> Woodhouse >> Sent: Wednesday, March 16, 2016 2:05 PM >> To: Mangefeste, Tony <[email protected]>; [email protected] >> <edk2- >> [email protected]> >> Subject: Re: [edk2] EDK2 Staging Proposal 3rd draft, final? >> >> On Wed, 2016-03-16 at 20:17 +0000, Mangefeste, Tony wrote: >>> >>> Here's the 3rd iteration based on your input. Please take one last >>> opportunity to review, we'll settle on this if there are no major >>> requests by Friday of this week. >> >> I still haven't seen an answer to my question of what this buys us, >> over the normal process of having such submissions come via >> contributors' github repositories, with associated pull requests. >> >> Why invent new processes and not just use the existing tools that are >> basically *designed* for this workflow? >> >> -- >> David Woodhouse Open Source Technology Centre >> [email protected] Intel Corporation > > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
