Databases
StackOverflow2013
Postsdbo
POMercurial - Delivering Isolated Features to Test and Live
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMercurial - Delivering Isolated Features to Test and Live
    primarykey
    data
    text
    <p>We are going to swap to Mercurial. A piece in our plan that is missing is how to manage branching/merging of build to Test Box (and LiveBox) so isolated features can be mixed with the StableRelease and built to TestBox.</p> <p>For instance, it seems the predominant usage is to have </p> <ul> <li>DefaultStableBanch</li> <li><ul> <li>TestBanch</li> </ul></li> <li><ul> <li><ul> <li>FeatureABranch</li> </ul></li> </ul></li> <li><ul> <li><ul> <li>FeatureBBranch</li> </ul></li> </ul></li> </ul> <p>Development on FeatureA and FeatureB, will happen at the same time. It looks like predominant usage is to have cloned repositories with branches for the above.</p> <p>Scenario 1 : If we build to test, we would merge LiveCode+FeatureA+FeatureB. If all goes well then we can merge the changesets to upstream to DefaultStable branch and build to LiveBox with FeatureA and FeatureB. job done.</p> <p>Scenario 2 : If we build to test, we would merge LiveCode+FeatureA+FeatureB, and QA shows there is a problem with FeatureB. We do not want to build FeatureB anymore. We do want to progress FeatureA. We want to re-test with FeatureA on it's own and let QA pass that. Then release that to Live and hence business agility.</p> <p>Questions : If FeatureB fails QA , we need to take out FeatureB changeset nodes from the Test Branch, build to TesBox again and then hopefully then merge upstream to DefaultStable branch to LiveBox.<br> What is the best way of removing the FeatureB changeset nodes, from the TestBranch, since 1. we need more dev on FeatureB, and the FeatureB nodeset is not finsihed. 2. We need to isolate DefaultStable+FeatureABranch and build that to test</p> <p>How are other people managing this ?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser206890
    1. USuser206890
    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
    1. VO
      singulars
      1. POMercurial - Delivering Isolated Features to Test and Live
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMercurial - Delivering Isolated Features to Test and Live
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMercurial - Delivering Isolated Features to Test and Live
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you foreseeing problems with B when A is present, or B by itself? or both?
      singulars
      1. POMercurial - Delivering Isolated Features to Test and Live
      1. USLasse Vågsæther Karlsen
    2. COI am trying to defend against a Bug in A, which the developer of A does not see. But, is fixed by some code in B. So, delivering A and B together to test will not manifest the bug. Releasing A to test on it's own will manifest the bug. Perhaps to others it seems unlikely BUT, an ORM dal is shared between A and B and ... aggregate roots are significant shared peices of code that are being worked on all the time that can cause this scenario. Also, SQL build files etc etc ...
      singulars
      1. POMercurial - Delivering Isolated Features to Test and Live
      1. USuser206890
 

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