Databases
StackOverflow2013
Postsdbo
POA better way to handle branching and merging?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POA better way to handle branching and merging?
    primarykey
    data
    text
    <p>We run a web development shop with ~20 developers working on ~30 different sites at any given time and we are sinking an incredible amount of time into managing our subversion repositories - there has to be a better way.</p> <p>Our client sites generally have 3 separate deployment environments: development (trunk), staging (branch), and production (branch).</p> <p>New features get reviewed internally on development, then merged with staging for client review and approval, and finally merged to production.</p> <p>Our current workflow: Every developer who is working on a major new feature for a client will create a branch from trunk, work on their feature, while regularly updating from trunk, and then merge the changes back to trunk (development) for internal review. Developers working on minor changes or fixes, will make them directly in the trunk.</p> <p>After internal sign off, the changes are then merged to staging. If changes need to be made, they will most often be made in trunk, and then merged to staging. Once approved, the changes will be merged with production and then deployed.</p> <p>New features are not reviewed sequentially internally or by clients, and the whole thing gets rather messy. It seems we are using the wrong processes - there has to be a better way to do this. We are very interested in learning how to utilize version control better, but we are lacking the experience to jump start the process.</p> <p>What are best practices for these scenarios? In addition to this forum, we are interested in engaging an experienced consultant, who can help us improve our processes.</p> <p>Thank you!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USToby Hemmerling
    1. USToby Hemmerling
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POA better way to handle branching and merging?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POA better way to handle branching and merging?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POA better way to handle branching and merging?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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