Databases
StackOverflow2013
Postsdbo
POVersion control for web apps - how to handle revisions and go-live schedules?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POVersion control for web apps - how to handle revisions and go-live schedules?
    primarykey
    data
    text
    <p>I am using SVN for source code management on a Classic ASP app that I develop/support. I maintain several versions of the app as required by my company:</p> <ul> <li>Discovery/playground version - where I do all the work. My Working Copy</li> <li>Dev/Test versions (no access to these sites/servers)</li> <li>Live version (no access to these sites/servers)</li> </ul> <p>Here is when I run into trouble:</p> <ol> <li>Work is done on Project A and is committed</li> <li>Project A is promoted to Dev/Test using an export from the log</li> <li>There is a problem with Project A and it is stalled in Dev/Test</li> <li>Project B comes along, is prepared and committed</li> <li>Project B now builds on Project A, but there are parts of Project A not ready for prime time</li> </ol> <p>Short of just "be careful not to screw anything up," is there anything I can do to make sure that parts of projects can stall in the development process without holding up everything?</p> <p>The necessity of a web server in the process seems to be causing me problems. I know that I can branch Project A when it goes to Dev/Test, and then merge it back to the trunk when it is live. Also that way I can revert my playground from before the branch and do Project B without anything from Project A having a chance to go live accidentally. However, then I can't play with Project A on my playground site. Do I have to spawn a new playground site for each branch?</p> <p>I know that this is probably too specific to my situation with all its constraints, but I'm hoping somebody else has experienced something similar to my situation.</p> <p>Thanks!</p> <p><strong>EDIT:</strong></p> <p>Here is my current solution: Maintenance fixes - changes that could go immediately to production - can get made in WC and committed to the trunk. Anything that has dependencies on a project gets branched. Working copies along the test path can be switched to point to that branch to test a project. Branches have to be kept up to date, and we can use commit hooks to keep people notified. When a branch is ready to be deployed to production, it gets merged back to the trunk and deployed.</p> <p>This makes sense and would work, right? </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDon Zacharias
    1. USDon Zacharias
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POVersion control for web apps - how to handle revisions and go-live schedules?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POVersion control for web apps - how to handle revisions and go-live schedules?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POVersion control for web apps - how to handle revisions and go-live schedules?
      1. USDaveE
      1. VTFavorite
    1. COHow many copies of the "Live Version" exist in production? One? More than one?
      singulars
      1. POVersion control for web apps - how to handle revisions and go-live schedules?
      1. USbraveterry
    2. COIt sounds to me like you would potentially need a playground site per branch. If cutting new branches is too expensive (whether that's at the VCS level or in terms of setting up playground sites) that is intrinsically an argument that you (corporately) should consider changing your setup so it becomes cheaper - though I appreciate this can be hard ...
      singulars
      1. POVersion control for web apps - how to handle revisions and go-live schedules?
      1. UScrazyscot
    3. CO@braveterry - 2 exported copies of the project live in production, on load balanced servers. @crazyscot - Before I typed it earlier, I hadn't really thought of creating a new site each time we branch. But it might make sense. Thanks both!
      singulars
      1. POVersion control for web apps - how to handle revisions and go-live schedules?
      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