Hi Senthil, another alternative to drive your own agenda is to draft a blueprint it by yourself and have Andy do the final tweakage and approval of direction. Creating and filling out blueprints should be straight forward.
Just go to the appropriate lava subproject and create a blueprint, fill it out and propose it in one of your LAVA team meetings or in a one-on-one with andy/michael. At best every blueprint should have a roadmap card it is delivering against. Be sure you include the following pattern in the blueprint whiteboard. Meta: Roadmap id: CARD-XXX Acceptance: ... acceptance criteria... Headline: your headline describing what is expected to be delivered and announced in the release announcement covering this work... On Mon, Nov 26, 2012 at 11:32 AM, Senthil Kumaran S <[email protected]> wrote: > Hi Andy, > > I would like to take the following items in a separate blue-print. I would > request you to create one for me and let me know. > > <snip> > TODOS: > For new testdef format we need to think about including new things such as: > * meta-data: targetted for lava-android-test, lava-test, lava-test-shell > * meta-data: OS like ubuntu, android, oe > * meta-data: device-types like panda, origen, etc > * overall test description > * descriptions of test cases, maybe think about some type of nesting logic > for optional test cases > </snip> > > Thank You. > -- > Senthil Kumaran S > http://www.stylesen.org/ > http://www.sasenthilkumaran.com/ > > _______________________________________________ > linaro-validation mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/linaro-validation -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
