Do you continue development in a branch or in the trunk? [closed]

by

I have tried both methods with a large commercial application.

The answer to which method is better is highly dependent on your exact situation, but I will write what my overall experience has shown so far.

The better method overall (in my experience): The trunk should be always stable.

Here are some guidelines and benefits of this method:

  • Code each task (or related set of tasks) in its own branch, then you will have the flexibility of when you would like to merge these tasks and perform a release.
  • QA should be done on each branch before it is merged to the trunk.
  • By doing QA on each individual branch, you will know exactly what caused the bug easier.
  • This solution scales to any number of developers.
  • This method works since branching is an almost instant operation in SVN.
  • Tag each release that you perform.
  • You can develop features that you don’t plan to release for a while and decide exactly when to merge them.
  • For all work you do, you can have the benefit of committing your code. If you work out of the trunk only, you will probably keep your code uncommitted a lot, and hence unprotected and without automatic history.

If you try to do the opposite and do all your development in the trunk you’ll have the following issues:

  • Constant build problems for daily builds
  • Productivity loss when a a developer commits a problem for all other people on the project
  • Longer release cycles, because you need to finally get a stable version
  • Less stable releases

You simply will not have the flexibility that you need if you try to keep a branch stable and the trunk as the development sandbox. The reason is that you can’t pick and chose from the trunk what you want to put in that stable release. It would already be all mixed in together in the trunk.

The one case in particular that I would say to do all development in the trunk, is when you are starting a new project. There may be other cases too depending on your situation.

By the way distributed version control systems provide much more flexibility and I highly recommend switching to either hg or git.

More Related Contents:

  1. When should you branch?
  2. How can I use ClearCase to “add to source control …” recursively?
  3. Why is a 3-way merge advantageous over a 2-way merge?
  4. Using IPython / Jupyter Notebooks Under Version Control
  5. ClearCase advantages/disadvantages [closed]
  6. Should I store generated code in source control
  7. What is the cleverest use of source repository that you have ever seen?
  8. IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?
  9. Source control vs. Revision Control?
  10. What’s the best three-way merge tool? [closed]
  11. Storing third-party libraries in source control
  12. Mercurial for Beginners: The Definitive Practical Guide
  13. Named Branches vs Multiple Repositories
  14. Mercurial — revert back to old version and continue from there
  15. Is version control (ie. Subversion) applicable in document tracking? [closed]
  16. Mercurial Subrepos – How do you create them and how do they work?
  17. How to edit incorrect commit message in Mercurial? [duplicate]
  18. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  19. Mercurial: How to ignore changes to a tracked file
  20. How do I perform a recursive checkout using ClearCase?
  21. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  22. Is there a way to keep Hudson / Jenkins configuration files in source control?
  23. Branching Strategies [closed]
  24. Comparison between Centralized and Distributed Version Control Systems [closed]
  25. Mercurial: Merging one file between branches in one repo
  26. How often to commit changes to source control? [closed]
  27. TFS 2017 – how build/deliver only changed files?
  28. How to find untracked files in a Perforce tree? (analogue of svn status)
  29. Code version change “rules” [closed]
  30. What is the difference between all the different types of version control?

Leave a Comment