Shared branch vs single branch

2013-09-23 Thread C M
What are some of the pros/cons of using a single/shared branch versus the private developer branch? We are having an internal debate within the team where the idea of a single/shared branch was proposed in reaction to two specific issues: 1. In the merge to trunk from individual developer

Re: Shared branch vs single branch

2013-09-23 Thread Branko Čibej
On 23.09.2013 19:44, C M wrote: What are some of the pros/cons of using a single/shared branch versus the private developer branch? We are having an internal debate within the team where the idea of a single/shared branch was proposed in reaction to two specific issues: 1. In the merge to

Re: Shared branch vs single branch

2013-09-23 Thread Les Mikesell
On Mon, Sep 23, 2013 at 1:50 PM, Bob Archer bob.arc...@amsi.com wrote: It really depends. I think all work for a specific release should be done in a single branch/folder. Many people follow the stable trunk model. In this model you generally do all work on trunk and then branch for a

RE: Shared branch vs single branch

2013-09-23 Thread Bob Archer
On Mon, Sep 23, 2013 at 1:50 PM, Bob Archer bob.arc...@amsi.com wrote: It really depends. I think all work for a specific release should be done in a single branch/folder. Many people follow the stable trunk model. In this model you generally do all work on trunk and then branch for a

Re: Shared branch vs single branch

2013-09-23 Thread C M
Unfortunately, we are lacking on processes and there's a definite lack of product management. But coming back to my original question: Are there any potential gotchas with using a single/shared branch? For now, that's the only change the team (and leadership) is looking to as the solution. Our

Re: Shared branch vs single branch

2013-09-23 Thread Les Mikesell
On Mon, Sep 23, 2013 at 2:35 PM, Bob Archer bob.arc...@amsi.com wrote: On Mon, Sep 23, 2013 at 1:50 PM, Bob Archer bob.arc...@amsi.com wrote: It really depends. I think all work for a specific release should be done in a single branch/folder. Many people follow the stable trunk model. In

Re: Shared branch vs single branch

2013-09-23 Thread BRM
...@gmail.com Cc: Bob Archer bob.arc...@amsi.com; Subversion users@subversion.apache.org Sent: Monday, September 23, 2013 4:04 PM Subject: Re: Shared branch vs single branch Unfortunately, we are lacking on processes and there's a definite lack of product management. But coming back to  my original

RE: Shared branch vs single branch

2013-09-23 Thread Bob Archer
What are some of the pros/cons of using a single/shared branch versus the private developer branch? We are having an internal debate within the team where the idea of a single/shared branch was proposed in reaction to two specific issues: 1. In the merge to trunk from individual developer

Re: Shared branch vs single branch

2013-09-23 Thread Edwin Castro
On 9/23/13 1:15 PM, BRM wrote: Trunk is dirty won't save you from bad merges, it'll just make more conflicts in your working copy as you do updates - something that drove a colleague of mine nuts so I started working in my own branch for that project. You also have to more frequently be doing

RE: Shared branch vs single branch

2013-09-23 Thread Andrew Reedick
From: C M [mailto:cmanalys...@gmail.com] Sent: Monday, September 23, 2013 4:05 PM To: Les Mikesell Cc: Bob Archer; Subversion Subject: Re: Shared branch vs single branch Unfortunately, we are lacking on processes and there's a definite lack of product management. But coming back