Re: Advice on version conventions for parallel, multi-team development

2008-11-16 Thread stug23
Am I the only one with this question? stug23 wrote: My question is related to the situation where there are multiple teams working on the same project. Let's call the project 'foo-bar' For example, Team A is working on a Subversion branch called 'team-a' and Team B is working on another

Re: Advice on version conventions for parallel, multi-team development

2008-11-16 Thread Dan Tran
My team is about to venture into this situation, my plan is to have each team should have its own internal repo. Each team must periodically merge into the main trunk which should also has its own internal repo. We only cut a release at the main trunk. -D On Sun, Nov 16, 2008 at 12:25 PM,

Re: Advice on version conventions for parallel, multi-team development

2008-11-16 Thread Johan Lindquist
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 My thought as well - Hudson would have each branch (as well as trunk) using a separate repository (config option). Johan Dan Tran wrote: My team is about to venture into this situation, my plan is to have each team should have its own internal

Advice on version conventions for parallel, multi-team development

2008-11-13 Thread stug23
My question is related to the situation where there are multiple teams working on the same project. Let's call the project 'foo-bar' For example, Team A is working on a Subversion branch called 'team-a' and Team B is working on another Subversion branch called 'team-b'. The builds are