This project has moved. For the latest updates, please go here.

branch and plugins

May 10, 2010 at 9:15 AM

hi everybody

We have just on team that is developing one product with many plugins  at the moment we have one team project with this branch strategy

-tfs TeamProject

   -main

     ---DEV

     ---versions

        --v1

        --v2  and so on...

it's correct to have plugins inside the product project or is better to have one Team project foreach plugin ? i need to change my branching strategy ?

 

thanks 

 

 

Developer
Jun 8, 2010 at 5:42 PM

I don't suppose there is ever one *correct* answer for all scenarios.

Your question probably raises more questions than answers:

Do you release different versions of a plugin at different times. For example, if your product has ten plugins, and you release a new version of the product, would you be releasing new versions of the plugins at the same time, on the same release cycle. Or is it possible to release a plugin on a different release cycle than the product?

My first inclination would to have all the code related to a product (and it's plugins) all contained within one TeamProject. I would not have a separate Team Project for each plugin unless these plugins are shared across products.

Regards,
Bill Heys
VS ALM Ranger