17 messages in com.perforce.perforce-user[p4] Branching whole projects vs. sub...| From | Sent On | Attachments |
|---|---|---|
| Noel Llopis | 24 Dec 2003 04:29 | |
| Noel Yap | 24 Dec 2003 04:50 | |
| Oren Shemesh | 24 Dec 2003 05:15 | |
| jab | 24 Dec 2003 07:03 | |
| Noel Llopis | 24 Dec 2003 10:51 | |
| Noel Yap | 24 Dec 2003 12:37 | |
| Chuck Karish | 24 Dec 2003 13:16 | |
| Noel Llopis | 24 Dec 2003 13:27 | |
| Noel Yap | 24 Dec 2003 13:36 | |
| Noel Yap | 24 Dec 2003 13:51 | |
| Chuck Karish | 26 Dec 2003 08:24 | |
| Arnt Gulbrandsen | 30 Dec 2003 02:48 | |
| Alen Ladavac | 30 Dec 2003 03:22 | |
| Grills, Jeff | 30 Dec 2003 16:48 | |
| Stephen Ng | 31 Dec 2003 05:18 | .py |
| jab | 31 Dec 2003 06:46 | |
| Stephen Ng | 31 Dec 2003 09:55 |
| Subject: | [p4] Branching whole projects vs. sub-sections![]() |
|---|---|
| From: | Noel Yap (Noel...@morganstanley.com) |
| Date: | 12/24/2003 04:50:39 AM |
| List: | com.perforce.perforce-user |
AFAIK, internally to Perforce, there's not much difference between branching an
entire project and branching a sub-section of one.
OTOH, there's a management difference in that client specs might be a bit more
complicated.
IMHO, the "best" branching policy really depends on what you have. For example,
is each library properly organized such that tasks tend to touch only one to a
few libraries? If so, a task branch per library may be best.
OTOH, if a task tends to span a few or more libraries, branching the entire
project may be better.
HTH, Noel
Noel Llopis wrote:
Hello,
A question for those of you using sandbox or experimental branching (where a developer decides to set up a branch for some work that isn't ready to be checked in the main line): Do you usually branch the whole project of the product you're working on, or just the minimum amount of directories?
The reason I'm asking is that our product is composed of about 20-25 different libraries, and then several executables on top of them. Up until now, since our work is fairly localized, I would just branch off one of the libraries, do some work, and then merge stuff back in the main line. That was very convenient because I only had to worry about integrating changes back and forth on that library alone.
However, we might be switching a more traditional way of arranging our libraries and includes (it's a C++ project), and libraries might include header files from other libraries directly from their directory by using relative paths. If we do that, then I won't be able to branch just one library and have it work with the rest of the system. I would have to branch all the libraries at once so they all stay relative to each other.
Is there something I'm missing? Do other people have this problem? Is branching a sub-section of a project something to be avoided? Thanks.
-- --Noel llopis at verizon.net
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user





.py