Integration tree follows a monthly release cycle

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
m (Added category tag)
 
(3 intermediate revisions not shown)
Line 1: Line 1:
 +
<font size = "4"><u>'''Sync Tree Release model based on Moving Code base'''</u></font>
 +
[[File:Monthly-SyncTreev0.1.jpg]]
[[File:Monthly-SyncTreev0.1.jpg]]
 +
 +
 +
Phase I: &nbsp;Developers are submitting patches to various mailing lists/Gerrit etc
 +
 +
Phase II: 3 Days before the Code freeze, we take the Snapshot of Moving code base, Freeze it and merge patches from Phase I (which are not in code base yet)
 +
 +
Sources of these patches are the patches in submitted-but-not-accepted state
 +
 +
Sometimes patches/features in development required for a Monthly release
 +
 +
Phase III: Subject the sync tree to Unit testing and fix any issues found in a week.
 +
 +
Finally proceed to give the Sync tree for handoff.
 +
 +
[[category:Linux]]
 +
[[Category:Patches and Release]]

Latest revision as of 14:02, 25 May 2010

Sync Tree Release model based on Moving Code base

Monthly-SyncTreev0.1.jpg


Phase I:  Developers are submitting patches to various mailing lists/Gerrit etc

Phase II: 3 Days before the Code freeze, we take the Snapshot of Moving code base, Freeze it and merge patches from Phase I (which are not in code base yet)

Sources of these patches are the patches in submitted-but-not-accepted state

Sometimes patches/features in development required for a Monthly release

Phase III: Subject the sync tree to Unit testing and fix any issues found in a week.

Finally proceed to give the Sync tree for handoff.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox