Re: [coreboot] [RFC] Time until patches should be submitted (was: Document for review: coreboot Gerrit Etiquette and Guidelines)

As others have stated, my concern is the tradeoff between long and short times. Too short a time, and people don't getting the chance to review patches. Too long a time and it delays development, frustrates developers, and requires rebasing the patch, maybe requiring MORE review. Alternate

Re: [coreboot] [RFC] Time until patches should be submitted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/04/2015 10:07 AM, Martin Roth wrote: > As others have stated, my concern is the tradeoff between long and > short times. Too short a time, and people don't getting the chance to > review patches. Too long a time and it delays development,

Re: [coreboot] [RFC] Time until patches should be submitted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/2015 03:36 PM, Paul Menzel wrote: > Dear coreboot folks, > > > Am Donnerstag, den 29.10.2015, 12:55 -0600 schrieb Martin Roth: >> As the community has grown, so has the need to formalize some of the >> guidelines that the community lives

[coreboot] [RFC] Time until patches should be submitted (was: Document for review: coreboot Gerrit Etiquette and Guidelines)

Dear coreboot folks, Am Donnerstag, den 29.10.2015, 12:55 -0600 schrieb Martin Roth: > As the community has grown, so has the need to formalize some of the > guidelines that the community lives by. When the community was small, > it was easy to communicate these things just from one person to >

Re: [coreboot] [RFC] Time until patches should be submitted (was: Document for review: coreboot Gerrit Etiquette and Guidelines)

On Tue, Nov 3, 2015 at 1:36 PM, Paul Menzel < paulepan...@users.sourceforge.net> wrote: > Dear coreboot folks, > > > Am Donnerstag, den 29.10.2015, 12:55 -0600 schrieb Martin Roth: > > As the community has grown, so has the need to formalize some of the > > guidelines that the community lives by.