On 12/17/06, Ed Leafe <[EMAIL PROTECTED]> wrote: > On Dec 17, 2006, at 12:54 AM, Nate Lowrie wrote: > > > I am creating a branch for the time being to develop the graph > > widgets. I don't want to include them in the dev trunk until at least > > some of the widgets are working..... > > Good idea. I sometimes create a local svn repository to back up > experimental stuff, but a branch will allow others to also take a > crack at the code.
I am used to the practice of always creating branches (or streams over in AccuRev land) for my work, and only merging to trunk after things are stable, tested, and sometimes reviewed (processes vary by job). (some logistics: you have to keep up with changes though or you'll end up in merge hell. so back merge from the trunk (or at least that's what I called it when working in clear case. in accurev you don't have backmerge problems so much)) when I had a job where we used svn repositories I would make branches and then in my personal workspace only switch the parts I was working on to the branch so that I'd still be working from the trunk otherwise. that kind of helped to keep up with things. anyway, I was wondering, as more people start to collaborate on dabo, would that be the practice to follow? -- sheila _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
