Thank you for all youre responses
The point uis that im not interested in feature branching, my developers
are interested in working with developer branches because its hard for them
to setup up eclipse each time they branch of from trunk, (i now the switch
command is the solution) , but atm. they are just not branching, so to get
them started we will work like they get developer branches and the hope the
discover how easy it is and start using branching for features. which i
agree is the right thing onles youre in ClearCase UCM.
*Jes Struck*
Consultant
Praqma A/S
Tel:+45 22 71 82 46
Mail: j...@praqma.net
web: www.praqma.net
On 28 November 2011 17:46, Les Mikesell <lesmikes...@gmail.com> wrote:
> On Mon, Nov 28, 2011 at 4:43 AM, jes Struck <j...@praqma.net> wrote:
>
>>
>> no what i wanted to do was
>>
>>
>> https://sites.google.com/a/praqma.net/howto/subversion/branching-strategies
>>
>> im pretty sure this would solve my issues.
>>
>>
> The relevant thing there is the merge from trunk to branch, which you'll
> likely want to do often so your developers can take advantage of each
> others' work and avoid large conflicts. You might also consider more of a
> feature-branch approach, just copying a new branch from the trunk to start
> the next round of work after you reintegrate the current work. This will
> work even if only one developer uses the branch. If you don't like the
> clutter from a lot of branch names, you could delete the finished work and
> copy back to the same name.
>
> --
> Les Mikesell
> lesmikes...@gmail.com
>
>
