Since nobody answered so far I would like to give you my opinion:
It is not a good Idea to split up if there are only minor tweaks between
projects. A way forward is to have a common core library - you need to do
bug-fixes only once and not for each branch. Then have sub-repositories
which are
Cheers, I'm not the author so I don't feel comfortable splitting it up.
What you say in last paragraph is exactly what I needed to hear, so I'll
stick to the current approach, each website instance its own separate
branch.
--
You received this message because you are subscribed to the Google
I think you need to say a little more of the 5 websites. Is it 5
different applications, based on common libraries? How much commonality is
it? Do they depend on each other in release cycles? Maybe it is the same
product, tweaked to support 5 major customers with various requirements?
--
You
