Samer, Access to edk2-staging should be identical to edk2.
Every feature branch on edk2-staging requires one or more maintainer(s) with write access to support updates to a feature branch in edk2-staging. If a developer does not have write access to edk2-staging, then they need to share changes with one of the maintainer(s) that is supporting the edk2-staging feature branch. Pull requests are being evaluated for edk2 trunk. Right now, there are no changes to the way changes are made to edk2 trunk. Once a feature branch in edk-2staging is ready for edk2 trunk, email patch reviews should be sent to edk2-devel. Feature branches in edk2-staging can be managed using any method(s) the maintainer(s) for that feature branch decide. Probably a good idea to document the method(s) being used in the Readme.md in the root of the feature branch. Best regards, Mike > -----Original Message----- > From: edk2-devel [mailto:[email protected]] On Behalf Of > El-Haj-Mahmoud, > Samer > Sent: Tuesday, April 26, 2016 9:35 AM > To: [email protected]; Kinney, Michael D <[email protected]>; > Mangefeste, Tony <[email protected]>; Andrew Fish <[email protected]>; > Laszlo > Ersek <[email protected]> > Subject: [edk2] Questions on write access to edk2-staging > > What is the process of requesting write access to edk2-staging? > > > * Should only module and tree maintainers have write access (similar > to edk2)? > > * Should developers working on contributing to the feature branches > have write > access? > > Also related: > > > * Should developers use pull requests on a branch to commit a change > (after it > gets reviewed through the official process on edk2-devel)? > > Thanks, > --Samer > _______________________________________________ > 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
