[Engine-devel] [SUGGESTION] Defining a process for the new feature discussion/implementation.

[Itamar Heim]

On 12/19/2012 03:08 PM, Michael Pasternak wrote:
>
> Hi All,
>
> In many cases OSS maintainers not always can be in the loop of different threads what may
> cause them missing important decisions being taken,
>
> As result later on during reviews of the patches they're not accepting (already implemented)
> features, what is causing not once for feature to be re-designed and/or delayed, what is wrong
> from the development cycle PoV.
>
> Therefore I'd like to suggest establishing dev-rules for the new feature implementation,
> what will make entire process much more easer for all of us:
>
> 1. discuss new feature on the mailing list (requirements/constraints/etc.)
> 2. summarise feature details in feature-doc
> 3. send feature-doc to review to:
>     3.1 ML (engine-devel)
>     3.2 MG (mailing group of maintainers of the relevant layers)
> 4. after feature-doc is accepted,
>     4.1 implement the feature
>     4.2 send it to gerrit for review to:
>         4.2.1 lead maintainer/s (they will review/delegate it)
>
>
> NOTE 3.2, 4.2.1 will require defining MGs such as:
>        - engine-devel-core
>        - engine-devel-ui
>        - engine-devel-api
>        - engine-devel-sdk
>        - engine-devel-cli
>        - engine-devel-vdsm ...
>
>
> Thoughts?
>

i thought this is what we have the arch mailing list for, since any 
feature is going to cut through multiple layers/components, unless they 
are very specific, they should be sent to arch, and all maintainers 
should follow arch.