[p4] User initiated Codeline Freezes
william_ivey at bmc.com
Mon Aug 27 11:44:12 PDT 2007
In our case it's easy. The build number (reported by commands
and embedded as a comment in .jar and .zip files) tells us
what branch and what change on that branch created the build.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of
todd.benham at kodak.com
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.
More information about the perforce-user