diverging workareas, same branch

nipper

Now, I have always avoided workareas that diverge and never get synced with staging. IMHO, only bad things can happen. The 2 times I have seen it I was brought in to clean up some really screwed up branches.

So I have another customer I am talking to. They are usign language specific workareas, so the fr workarea has a folder corp.com.fr and templatedata/corp.fr/. The uk workarea has corp.com.uk and templatedata/corp.uk/ etc. The staging area has everything.

This can only work if no one EVER does a get latest.

They also have a limited # of branches available, so doing a langauge specific branch is not possible.

My first gut feeling is to get everything into 1 workarea. However this *could* work.

So am I being paraniod ? Well, you do not need ot answer that, but does an architecture like this have a good likelyhood of success with the right restrictions ?

Thoughts ?

ISCBorisB

Now, I have always avoided workareas that diverge and never get synced with staging. IMHO, only bad things can happen. The 2 times I have seen it I was brought in to clean up some really screwed up branches. So I have another customer I am talking to. They are usign language specific workareas, so the fr workarea has a folder corp.com.fr and templatedata/corp.fr/. The uk workarea has corp.com.uk and templatedata/corp.uk/ etc. The staging area has everything. This can only work if no one EVER does a get latest. They also have a limited # of branches available, so doing a langauge specific branch is not possible. My first gut feeling is to get everything into 1 workarea. However this *could* work. So am I being paraniod ? Well, you do not need ot answer that, but does an architecture like this have a good likelyhood of success with the right restrictions ? Thoughts ?

In the case like that you do not really have a good solution. All you can do is consider your options and pick the
one that stinks less. So, here's the Option I considered the least offensive in one of my Projects.

Note that my use case was different:
We had WAs per Country, like US, Canada, etc... So, US WA contained English/Spanish Assets, Canada WA English/French, etc.
I cared only about DCRs, we generated multiple JSP Tiles per DCR to be assembled by WebSphere App Server run-time.

To make it work I used an idea of View Filter. I've modified (hacked) TS "All Files" View. WAs were really in synch with
STAGING, "Get Latest" worked, etc. The CCPro "All Files" however worked differently for different Workeareas, filtering-in only relevant DCRs.
For example, Canada WA listed (showed) only Canadian DCRs, etc. WAs that the filter did not recognise ( like WA "Boris" )
worked normally. Note also that I deliberately left "View all and Deleted" unmodified so that Contributors could work
with the whole collection if needed.

If you think it a sane idea (that's debatable!), let me know. I can mail you modified jsp and couple screen shots with
install explanation.