Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's our typical development cycle; we're "psuedo agile"; and run on a 2 week release cycle.</p> <p>All projects begin on a branch from the trunk. No exceptions. </p> <p>Once the project is finished, and clears code review, the developer is given the green light to merge that branch into the trunk. That way; no code that hasn't been thoroughly vetted makes its way onto the trunk. We use CruiseControl for continuous integration, so after a commit to the trunk, if any tests fail, the developer is responsible for fixing them. These fixes go on the trunk.</p> <p>One week prior to the next release; we create a release "tag" (essentially another branch) and send it over to QA. If you haven't merged your code back to the trunk at this point, it's not going out with the next release. (Important note: this release "tag" is never merged back to the trunk. ever.) As QA finds bugs; they're assigned back to the developer. When the developer fixes them; their changes must be committed to both the release tag and the trunk.</p> <p>When release day comes; we release everything on that tag. In the case of post release fixes; we follow the same guidelines as when we're in the QA cycle, that way if someone merges in a new project to the trunk after the release tag is cut; it's not getting inadvertently released with the emergency fix.</p> <p>Lather, rinse, repeat...</p> <p>This might not answer your question per se; but hopefully this serves as a good outside point of view of how you might want to set up your development process. This wasn't our original process, but rather what we've come up with over the last year or two, and in my experience, this is leaps and bounds ahead of the way we used to do it before.</p> <p>If you'd like any clarifications on this; just leave me a comment and I'll update as necessary.</p>
    singulars
    1. This table or related slice is empty.
    1. POSVN web development cycle issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJim B
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSVN web development cycle issue
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO>their changes must be committed to both the release tag and the trunk. Commit to a tag? Personally, I think it would be better to commit the fixes only to the trunk and tag it again when everything is fixed. Usually tags are "read-only snapshots" of the state of the codebase in a certain moment, and shold not be modified.
      singulars
      1. PO
      1. USDavide Gualano
    2. COThe problem you run into there is that if another developer merges their project into the trunk after the tag is cut, and then you re-tag, their project is now in the release.
      singulars
      1. PO
      1. USJim B
    3. COThat mitigates the problems of running into conflicts between "immediate release items" and "development features" the OP describes
      singulars
      1. PO
      1. USJim B
 

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