Databases
StackOverflow2013
Postsdbo
POHas this branching strategy sense in a web development ecosystem?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHas this branching strategy sense in a web development ecosystem?
    primarykey
    data
    text
    <p>i don't know if this question is stack-overflow related or it should be posted on another stack-exchange platform, but anyway..</p> <p>The problem is a <strong>new branching system</strong> that we have in mind to adopt in near future. At work we develop primarly web applications (ecommerce, cms, classified, special purpose) and some websites in php and our vcs is <strong>svn</strong>.</p> <p>This is the new model that we want to adopt:</p> <p><strong>Trunk</strong>: always development</p> <p><strong>Staging</strong> (branch): a branch created to test new features on remote ambient (the same system that live has, really the same server..)</p> <p><strong>Live</strong> (branch): branch for live.</p> <p><strong>Other branches</strong> to develop concurrent features.</p> <p>Now, the idea is to bugfix live and then push back changes to trunk. Develop features directly on trunk or into another branches then merge to trunk.</p> <p>Push trunk into staging to get ready for new features that will go live really soon; and then? how we can get that staging into the live branch? We have to pass from trunk?</p> <p>Now the strategy is:</p> <p><strong>Trunk</strong> : it's the live version</p> <p><strong>Branch</strong> for <strong>each feature</strong></p> <p>Live bugfix done to trunk then pushed to branches</p> <p>Staging is a working copy that switchs for a branch at the end of the development of the feature, before the merge back into trunk.</p> <p>But this method has some drawbacks:</p> <ul> <li><p>always switching..</p></li> <li><p>no possibility to test two concurrent branches</p></li> </ul> <p><em>What do you think about the new strategy?</em></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMark
    1. USapelliciari
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHave you reviewed git-flow? http://nvie.com/posts/a-successful-git-branching-model/
      singulars
      1. POHas this branching strategy sense in a web development ecosystem?
      1. USceejayoz
    2. COWon't you just merge from Trunk to Staging, do your QA, and then merge again to Live and deploy from there?
      singulars
      1. POHas this branching strategy sense in a web development ecosystem?
      1. USDon Zacharias
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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