StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIs trunk needed in multiversion projects
text
Body
copied!<p>I work in a project with one released version in maintenance and two or more versions in development simultaneously.</p> <p>Here is where the doubts about the need of trunk arises.</p> <p>I've read the SVN Book in The Read Bean and others (Pragmatic Version Control with Subversion) and all of then suggest using a trunk-centric mode of development. I don't know if in my case this is applicable and if exist other projects with multiversion release cycle that use other schemas successfully.</p> <p>Why is the trunk-centric mode the recommended? Is there any problem with the version branches going more and more far of the trunk? I this schema the integrations with trunk have any sense?</p> <pre> /-----gamma-----/(3)----------> / / /----beta---/(1)---/(2)--/---beta--------/--\ / / / \ /------------alpha--/------/---\ \ / \ \ ------------trunk--------------------(a)----------------------(b)------------------> </pre> <p>Edit:</p> <p>When I say two or more development versions I mean versions of the software with incremental level of functionality. In the <em>graphic</em> above:</p> <ul> <li>alpha: functionality A.</li> <li>beta: functionality A + B.</li> <li>gamma: functionality A + B + C.</li> </ul> <p>Meaning that <em>all</em> the functionality of a branch is included in later branches (through sync merges). The branches differ in stability level (<em>older</em> branches are more stable) and in functionality (<em>young</em> branches have new functionality).</p> <p>Edit 2, after TridenT answer:</p> <p>The development of the stable version is done in a trunk's branch and then merged back to trunk when is stable, so the trunk contains all the stable changes and in the end the more stable version of the software.</p> <p>I'm asking this question now because I'm rethinking the branching strategy of the whole project.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload