definition-of-done: update based on planning meetings * Update the Author * Remove reference to integration to clarify upstream kernel * Update tested requirement to make sure developers know they need to add their code into the automation framework. * Add paragraph detailing the need for test reports * Add outline of upstream flow and creation of merge stories to track that items have upstream merges pending * Clarify some reasons why the upstream step may not occur and what to do in that case * Give ideas about how to handle feedback within the current sprint when the feedback requires changes that need to be scheduled in the next sprint. * Remove the reference to backporting for LTS * Specify that when we miss a commit we have to carry the patches Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> --- * Updated in version 2 * Fixed grammatical error pointed out by Felipe
DoD: get rid of 'integrated' We're targetting mainline only development. There won't be an official TI Integration tree from LCPD, so that requirement can vanish. While at that, also make it clear we want automated test scripts. Acked-by: Chase Maupin <chase.maupin@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
scope: add pointers to mailing list and github project Mention those two important pieces of information as links, so people can figure out how to find the latest source code for the manual itself. Acked-by: Chase Maupin <chase.maupin@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
grooming: rename chapter and add initial text Rename the "Breaking tasks into bite size pieces" chapter into "Work Breakdown", write an introduction and the descriptions of Epics and Stories. Signed-off-by: Luciano Coelho <coelho@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
tamm: roles: rename chapter later patches will come adding more roles to that chapter. Those roles are TI-specific, not related to scrum in any way. Instead of creating a new chapter, it felt better to just rename what we have. Signed-off-by: Felipe Balbi <balbi@ti.com>
tamm: terminology: add new terminology section This covers most of the basic keyworks for Scrum along with some more LCPD specific items such as mainline / upstream, etc. Signed-off-by: Darren Etheridge <detheridge@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>