[p4] User initiated Codeline Freezes

Roy Smith smith_roy at emc.com
Mon Aug 27 10:40:53 PDT 2007


One way or another, somebody needs to have recorded the fact that  
"Release 1.0 was built from change 432246."  How you remember that is  
just part of your release process.  Whether you do that with a label  
in your revision control system, by writing it down in a logbook, by  
recording it in file, or by having it tattooed on your release  
engineer's forehead, is up to you.

On Aug 27, 2007, at 11:28 AM, todd.benham at kodak.com wrote:

> Playing devil advocate here:
>
> If 5 change lists were needed to complete a release branch like,  
> Rel1.0,
> then how would you know a year later which change lists were in the
> 'final' release. Someone could have added the 5th accidentally and the
> release was really only 4 change lists.
>
> Todd
>
>
> -----Original Message-----
> From: Chuck Karish [mailto:chuck.karish at gmail.com]
> Sent: Monday, August 27, 2007 11:12 AM
> To: Todd D. Benham
> Cc: jab at pobox.com; smith_roy at emc.com; perforce-user at perforce.com
> Subject: Re: [p4] User initiated Codeline Freezes
>
>
> On 8/27/07, todd.benham at kodak.com <todd.benham at kodak.com> wrote:
>> Being relatively new to the 'Perforce way', if you don't freeze a
>> branch (in whatever means), how do know what files where part of a
>> particular version. Is there an assumption that it is labeled?  A
>> general CM practice is to occasional rebuild (audit) older  
>> versions to
>> prove the process really captured it correctly. If it is not frozen,
>> how do you ensure it wasn't accidentally changed later (added to).
>
> A changelist number defines a moment in the history of the code  
> line that
> can be used the same way you would use a label.  It completely  
> specifies
> the contents of the code line.
>
> Syncing to the same changelist number always brings the same bits  
> into the
> client workspace.  Whether your build system does the same thing  
> with them
> is still worth auditing, but it's a separate problem.
>
> -- 
> Chuck Karish   karish at well.com   (415) 317-0182
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>

-------------------
Roy Smith <smith_roy at emc.com>
Software Guy, EMC Common Management Group
44 South Broadway, 7th floor
White Plains, NY 10601
(914) 580-3427
AIM: roysmith649



More information about the perforce-user mailing list