8 messages in com.perforce.perforce-user[p4] What to do with development code...| From | Sent On | Attachments |
|---|---|---|
| Jan Kristiansen | 22 Oct 2003 00:58 | |
| Lars Thegler | 22 Oct 2003 01:14 | |
| Robert Cowham | 22 Oct 2003 01:33 | |
| Jeff Bowles | 22 Oct 2003 06:54 | |
| Rick Macdonald | 22 Oct 2003 07:03 | |
| Stephen Vance | 22 Oct 2003 09:48 | |
| Lars Thegler | 23 Oct 2003 00:33 | |
| Robert Cowham | 24 Oct 2003 08:54 |
| Subject: | [p4] What to do with development codelines when development is finished |
|---|---|
| From: | Robert Cowham (rob...@vaccaperna.co.uk) |
| Date: | 10/22/2003 01:33:52 AM |
| List: | com.perforce.perforce-user |
Jan
One idea is to have a date component in the name of the branch, e.g.
2003-10-01-devel-proj1 Or 2003-10-01/devel-proj1
This makes sort order more useful and less changeable (any standard sequence number would do the same). It also becomes very easy to ignore ancient branches when browsing repository.
To mark a dev branch as "dead" there are a couple of options:
- delete the branch spec (implying that you always have branch specs for "active" branches, and when they die you remove them - train your users to only integrate with branch specs - of course you should save branch specs as text files in Perforce as well, but that's another issue)
- remove access permissions from dead branches so people won't see them
- p4 delete files on the dead branch - people won't see them if they don't have "View deleted files" option ticked in p4win. Danger is someone might do an integrate from the deleted files and thus "delete" the same files on main. You can get around this using the (un)documented command (p4 help undoc) and remove permission for =branch right on the dead branch (so it can't be used as source for an integrate). This =branch trick will also work even if you don't delete the files.
Does that help?
Robert Perforce Consulting Partner and Trainer P.s. Haven't mentioned obliterate on purpose - bad idea!!
-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Jan Kristiansen Sent: 22 October 2003 08:59 To: perforce-user at perforce.com Subject: [p4] What to do with development codelines when development is finished
Hi,
We have started to implement a product structure where we have a main- codeline, release codelines and development codelines, like shown below
product#1 -+- devel -+- devel_project_1 + +- devel_project_2 + +- main + +- releases -+- release_1 +- release_2
This structure suits our need quit well, but due to the posibility of a large number of development codelines I would like hear what other perforce users do with development codelines when development has finished (keep, delete or something else).