« Home | Excellent tutorial on linux usermanagement and sud... » | Using Grep to search in files » | Android implicit intents various intents creation ... » | Find the unused selectors in a webpage. » | Installing missing dependencies redhat / fedora / ... » | Query to delete rows with duplicate columns. » | Mysql do bulk operations on tables, columns, infor... » | Joomla templating tutorials. » | Google Trends / Result count, of programming langu... » | Excellent video on performance testing with open s... » 

Tuesday, December 21, 2010 

Svn branching strategies.

I was often baffled by the different process that people follow while adopting svn for their work. Came across this link

Here are the process that they follow
  • Unstable trunk
  • Stable trunk
  • Agile release strategy¬†
For the projects that we work at scube, we followed Unstable trunk. However seems like Stable trunk is better strategy and a default strategy incase you are using git ?. I think it would help in automating the build process better as you always check out from trunk instead of a different branch every-time (esp for point releases).