[p4] A few questions about perforce and a specific branchingstrategy

[Robert Cowham]

I hope that the (currently undoc'ed) dynamic labels will address this issue.

Robert 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of G Barthelemy
> Sent: 16 October 2006 10:57
> To: karish at well.com
> Cc: Perforce Users
> Subject: Re: [p4] A few questions about perforce and a 
> specific branchingstrategy
> 
> 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
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
>