[p4] A few questions about perforce and a specific branching strategy

[G Barthelemy]

On 10/14/06, Chuck Karish <chuck.karish at gmail.com> wrote:
> If they record the changelist at which each release is made
> neither a new branch nor a label is needed.  To be more
> careful one could save a list of all the file revisions that go
> into the release.

The one snag I can see with recording just the changelist number of
releases is that, the day you have to "merge" your Perforce depot with
another one (say following an acquisition, a change of strategy in the
company going from multiple depots at multiple sites to one
centralised depot, or simply to take onboard that forgotten depot from
that box in the lab) then most of your existing changelists will get
renumbered.
OK, you'd get an "old changes to new changes" mapping, but would you
want to rework all your old release documentation ?
So for releases I would really use explicit metadata, such as a label.
-- 
Guillaume