Integration tree follows a monthly release cycle

From OMAPpedia

Revision as of 03:55, 1 October 2009 (edit) Vikrampandita (Talk | contribs) ← Older edit		Revision as of 04:01, 1 October 2009 (edit) (undo) Vikrampandita (Talk | contribs) Newer edit →
Line 1:		Line 1:
		+	<font size = "4"><u>'''Generic Kernel CodeFreeze and Handoff Cycle 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:uncategorized]]

---

Revision as of 04:01, 1 October 2009

Generic Kernel CodeFreeze and Handoff Cycle based on Moving Code base

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.