Databases
StackOverflow2013
Postsdbo
POHow do we manage granular changesets in the central/shared repository?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do we manage granular changesets in the central/shared repository?
    primarykey
    data
    text
    <p>I've used Mercurial for years locally, but now we are doing a pilot of switching over from Subversion at my company.</p> <p>We're embracing the fact that developers will now be making more granular changesets--some of which may not even build. When developers push their changes to the central repository, all of these changesets will show up in the history - this is natural and expected.</p> <p>My question is: how do we deal with the fact that, because changesets are more granular, this makes it possible for developers to update to a revision that doesn't build? We are coming from a world where you can checkout anywhere in the repository and reasonably expect to be able to make a release from that point. With DVCS's, how do you tell where a "safe" revision is?</p> <p>This issue is somewhat addressed in <a href="http://kiln.stackexchange.com/questions/2947/does-it-make-sense-to-use-named-branches-and-branch-repositories-together" rel="nofollow">this question</a>, but I'm more interested in finding out how to deal with this using branch repos (and not named branches).</p> <p>I understand there are ways to modify history (e.g. the <a href="http://mercurial.selenic.com/wiki/CollapseExtension" rel="nofollow">collapse extension</a>) so that the changes get collapsed in the history of the repository, but we'd like to preserve the history.</p> <p>Looking at the <a href="http://selenic.com/repo/hg" rel="nofollow">mercurial</a> and <a href="http://hg.mozilla.org/mozilla-central/" rel="nofollow">mozilla</a> trees, I don't see a clear way to tell where safe revisions are to sync. Is this not as important as we think it is?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USbentsai
    1. USbentsai
    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. POHow do we manage granular changesets in the central/shared repository?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow do we manage granular changesets in the central/shared repository?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow do we manage granular changesets in the central/shared repository?
      1. USbialix
      1. VTFavorite
    1. COOn the Mercurial project itself, we have the guideline "every commit should pass tests". We don't keep to this perfectly, but we do pretty well.
      singulars
      1. POHow do we manage granular changesets in the central/shared repository?
      1. USmpm
 

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