[p4] Promotion Model

[Zarnes, Todd]

I am looking for away to manage 'firmer' code streams under the Tofu model -
the firmer the code stream the more stable, less intrusive the changes.  I
want to promote\trip only QA validated changes (Jobs) from a development
code stream into a release code stream that can be built nightly.  Not all
changes made in the Dev branch would make the nightly release candidate -
only those that were passed by QA.  I am trying to keep the integration
tasks low and don't want to have the originating developer go back and
integrate from Dev to Release once approved by QA.  I don't want to give QA
write access to integrate files from Dev to Release once they validate a
Job.  I supported PVCS Dimensions for a few years and they had a 'status' on
a file where you could promote a version of the file from say Open - Worked
- Built - Released.  The file stayed the same and different support groups
could move it along the process with transitions.  Besides integrating to
separate branches and has anybody mimicked this type of model in Perforce.
May a Jobs 'save in' trigger that had a filed for QA sign off that would do
a safe automatic merge into a Release branch?      

 

Todd  Zarnes

Intuit SCM