Promotion/SCM models - Nick...@navio.com - com.perforce.perforce-user

12 messages in com.perforce.perforce-userPromotion/SCM models

From	Sent On	Attachments
Jeff...@uplanet.com	10 Jun 1997 14:24
Clay...@stac.com	11 Jun 1997 10:41
Jeff...@uplanet.com	11 Jun 1997 11:28
Paul...@radstone.co.uk	12 Jun 1997 00:52
Gerd...@BITart.com	12 Jun 1997 01:00
Paul...@radstone.co.uk	12 Jun 1997 03:34
Wayn...@ichips.intel.com	12 Jun 1997 08:13
Jeff...@uplanet.com	12 Jun 1997 08:20
Nick...@navio.com	12 Jun 1997 09:40
Clay...@stac.com	12 Jun 1997 10:06
Clay...@stac.com	12 Jun 1997 10:28
Jeff...@uplanet.com	12 Jun 1997 10:30

Subject:	Promotion/SCM models
From:	Nick...@navio.com (Nick...@navio.com)
Date:	06/12/1997 09:40:08 AM
List:	com.perforce.perforce-user

Hi all,

First, Jeff, I agree. Nice presentation.

One other problem, although somewhat minor, with labels:

Say you have a file called 'foo.c' and one called 'bar.c'. The tree gets labeled. Later, you delete 'bar.c', and then rename 'foo.c' to 'bar.c' for release 2.0. I don't believe Perforce can handle such a renaming problem correctly, although I haven't experimented with 97.2 yet. I know this is an odd situation, but with large code bases, problems like this are bound to arise.

Anyway, great product nonetheless.

- -Nick

At 08:52 AM 6/12/97 +0100, you wrote:

At 11:28 11/06/97 -0700, Jeff Bowles wrote:

ps. If you're interested in the "beginning Perforce talk" I gave to the people here, let me know. It's at ... let's see ... http://www.slip.net/~jbowles/p4presentation/index.htm Note that the suffix has three characters, not four.

Jeff,

Nice presentation.

I was interested to see that you're using labels to mark special "cuts" of code - for releases, etc.

I was keen to do that myself - recovering a version with get @label looks really good - but, as labels can be re-sync'd later, I'm not sure they're safe enough.

I sure that sooner of later, someone will accidentally re-sync a useful label like "CUSTOMER_RELEASE_1" to the current state of his client. Someone always does and, IMO, that puts archive at risk.

So, we're using change numbers and comments in the change spec. It's not pretty, but it's safe.

(If anyone knows how to make labels "safe" please let me know!)

Paul.

---------------------------------------------------------------------- Paul Goffin Principal Software Engineer Radstone Technology PLC Water Lane, Towcester, Northants, NN12 6JN United Kingdom

Tel +44 (0)1327 359444 Fax +44 (0)1327 358112 email goffin at radstone.co.uk