Answer by rmartinez for Subversion - is trunk really the best place for the...
Nope, trunk is not the best place for committing development level code. In our environment, we regard our trunk as the mirror to whatever has been deployed to production. The workflow maybe different...
View ArticleAnswer by conny for Subversion - is trunk really the best place for the main...
Another example of when the good old "stable trunk, dev in branch" process becomes an issue: You're developing a web application that depends on a lot of live, possibly user-contributed, data. You can...
View ArticleAnswer by JesperE for Subversion - is trunk really the best place for the...
I've created a couple of shell-scripts to simplify creating short-lived development branches: # Create new branch and switch to it function svn_bswitch() { branch=$1; shift msg="$1"; shift URL=$(svn...
View ArticleAnswer by Edward Z. Yang for Subversion - is trunk really the best place for...
Teams that use Subversion often have a pathological aversion to merging, because prior to 1.5 it was a long complex process prone to failure. If you have enough developers so that having an always...
View ArticleAnswer by SunfiShie for Subversion - is trunk really the best place for the...
The trunk is where the ongoing development is supposed to happen. You really shouldn't have a problem with "broken" code, if everyone is testing their changes before committing them. A good rule of...
View ArticleClik here to view.
Answer by Swanand for Subversion - is trunk really the best place for the...
Nope trunk isn't the best place. At our organization we always follow this approach: Trunk contains release code, so it always compiles. With new each release/milestone we open a new branch. Whenever a...
View ArticleAnswer by Fry for Subversion - is trunk really the best place for the main...
In our company, we have a nightly build of the trunk. It is expected that everybody test their code so that it at the very least compiles before they check it in. If the nightly build fails, the...
View ArticleAnswer by zigdon for Subversion - is trunk really the best place for the main...
It really depends on your environment. In some cases, having the trunk broken temporarily isn't a big deal. But if you're working with more than 2-3 people, that probably wouldn't be a good idea. In...
View ArticleAnswer by David Segonds for Subversion - is trunk really the best place for...
I would recommend reading this article on SCM best practices. Extracted from the article: Have a mainline. A "mainline," or "trunk," is the branch of a codeline that evolves forever. A mainline...
View ArticleAnswer by albertein for Subversion - is trunk really the best place for the...
Your trunk should ALWAYS compile, if you need to make breaking changes you should use a branch and merge the changes back later. Read this chapter of the SVN book:...
View ArticleSubversion - is trunk really the best place for the main development?
In SVN, trunk is the recommended place for the main development and I use this convention for all of my projects. However, this means that trunk is sometimes unstable, or even broken. This happens for...
View Article
