[p4] Looking for the best starting point
Mgressett at Verbind.com
Mon Jan 24 14:22:24 PST 2000
Sorry, tip of the slongue. We use the changelist number precisely to avoid
the need for labels.
Since the build runs at a time when no-one is checking in, we can recover
the build for a given date, i.e., 1:30 AM 1/13/2000. This isn't a perfectly
general solution, but it's all we need.
Also, our internal and external version numbers reference a changelist
number. So if we release something to QA for extensive testing, or
externally to a client, we can backtrack from a given .dll to a full build.
For these releases, we use branches rather than labels, so we can backtrack
through releases if necessary. I suppose we could use labels for internal
releases, since they would be static (we don't apply bug fixes to the
branch, we apply them to the tip).
From: Hoff, Todd [mailto:Todd.Hoff at ciena.com]
Sent: Monday, January 24, 2000 4:59 PM
To: perforce-user at perforce.com
Subject: RE: [p4] Looking for the best starting point
> -----Original Message-----
> From: Mark Gressett [mailto:Mgressett at Verbind.com]
> Sent: Monday, January 24, 2000 1:34 PM
> To: 'Piaw Na'; 'CRuble at ixl.com'; perforce-user at perforce.com
> Subject: RE: [p4] Looking for the best starting point
> We also use branching for releases, but simply use the
> current changelist
> number to label the nightly build. If two builds have the
> same changelist
> number, we don't really care, although I suppose that means
> we lose a bit of
> date information.
If you have the change number why do you need a label at all?
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user