Integration tree follows a monthly release cycle
Sync Tree Release model 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.