StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10058582
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-07T21:34:52.983
FavoriteCount
0
LastActivityDate
2012-04-07T21:34:52.983
LastEditDate
LastEditorUserId
0
OwnerUserId
6309
ParentId
10058261
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The rule of thumb is simple: The less branch, the better. I mean, if you ever done deliver and rebase before with ClearCase, you know: <ul> <li>how painful it is</li> <li>how poorly it scales with the number of file (merging 1000 files is awfully long, merging 5000 files is murder)</li> </ul> So the real rule of thumb is: if you don't have to modify any file for a given development stage, don't create a branch. For instance, for promoting a code to QA, where you will only read it (and launch some tests, in order to accept that code if they pass, or to reject that code if they fail), don't create a QA Stream where you would deliver the code: it is too long for an non-existent added value. Use <a href="http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_proj.doc/t_chng_bl_prom_lvl.htm" rel="nofollow noreferrer">baseline promotion level</a> whenever you can, and <a href="http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_proj.doc/c_ucm_ovvw_recommend_bl.htm" rel="nofollow noreferrer">recommend your promoted baselines</a>. <img src="https://i.stack.imgur.com/XpUMk.gif" alt="promoted baselines"> <blockquote> The Deployment Engineer will always use a dedicated stream for each environment to get his/her files required to carry out the build/deployment activities. </blockquote> Err... no, if you don't have any change to do. The Deployment Engineer doesn't care at all where the baseline is coming from, only if the code deploys and runs successfully. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTypical best-practice ClearCase project structure
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USVonC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTypical best-practice ClearCase project structure
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.