Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are a lot of great writeups up Mercurial workflows, including:</p> <ul> <li><a href="http://stevelosh.com/blog/2010/02/mercurial-workflows-branch-as-needed/" rel="nofollow noreferrer">http://stevelosh.com/blog/2010/02/mercurial-workflows-branch-as-needed/</a></li> <li><a href="http://stevelosh.com/blog/2010/05/mercurial-workflows-stable-default/" rel="nofollow noreferrer">http://stevelosh.com/blog/2010/05/mercurial-workflows-stable-default/</a></li> <li><a href="https://www.mercurial-scm.org/wiki/StandardBranching" rel="nofollow noreferrer">https://www.mercurial-scm.org/wiki/StandardBranching</a></li> </ul> <p>All of those use <a href="http://stevelosh.com/blog/2009/08/a-guide-to-branching-in-mercurial/#branching-with-named-branches" rel="nofollow noreferrer">Named Branches</a> very minimally -- definitely not one per feature, which with clones as branches sounds like the work mode you (and I) prefer.</p> <p>Hitting your specific question, if the combination LiveCode+FeatureA+FeatureB is failing tests the the best way to handle it is to just keep repairing FeatureB and then merging those changes down into FeatureA + Feature B. However, before you get to that stage it's a good idea to have QA hit LiveCode+FeatureA and LiveCode+FeatureB separately too, it's slightly more work for them (more test targets) but having each feature in isolation helps find the cause of the defect more quickly.</p> <p>Once LiveCode+FeatureA and LiveCode+FeatureB are passing QA, <em>then</em> you merge them into LiveCode+FeatureA+FeatureB and if that still passes tests merge the whole thing into DefaultStable. There should be no need to <em>remove</em> FeatureB from a LiveCode+FeatureA+FeatureB because you can always just create a new clone of LiveCode and merge in only FeatureA if you want it.</p> <p>Here's a <strong>great</strong> writeup of a Mercurial (Kiln) based QA/release process:</p> <p><a href="http://blog.bitquabit.com/2011/03/10/when-things-go-well/" rel="nofollow noreferrer">http://blog.bitquabit.com/2011/03/10/when-things-go-well/</a></p>
    singulars
    1. This table or related slice is empty.
    1. POMercurial - Delivering Isolated Features to Test and Live
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USVadim Kotov
    1. USRy4an Brase
    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. 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. VTUpMod
    1. COI'm not suggesting named branches either, although I think that's what you're implying. If you aren't implying that, then my apologies.
      singulars
      1. PO
      1. USMikezx6r
    2. COCheers, thanks for your answer, we will look at the references. In my mind I was assuming default, test branches in the Stable, Test and FeatureA, FeatureB clones. Perhaps there should be FeatireA, FeatureB named brancjes in the all the repos everwhere. That way we know which chnageset nodes were in which Feature ...
      singulars
      1. PO
      1. USuser206890
    3. COCheers, thanks for your answer, we will look at the references. In my mind I was assuming defaultStable, test branches in the Stable, Test, FeatureA, FeatureB clones repos. Perhaps there should be FeatureA, FeatureB named branches in the all the repos everwhere. That way, we know which changeset nodes were in which Feature when the chnagesets hit the defaultStable branch ... ?
      singulars
      1. PO
      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