StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2947234
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-06-01T04:13:24.997
FavoriteCount
0
LastActivityDate
2010-06-01T04:19:51.467
LastEditDate
2017-05-23T12:09:06.757
LastEditorUserId
-1
OwnerUserId
6309
ParentId
2947220
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
As explained in the <a href="https://stackoverflow.com/questions/2704996/describe-your-workflow-of-using-version-control-vcs-or-dvcs/2705286#2705286">differences between DVCS and CVCS</a> (Centralized VCS), the main advantages are: <ul> <li>local commits (you can commit more often in private branches, then clean up the history you want to push to other repos)</li> <li><a href="https://stackoverflow.com/questions/2563836/sell-me-distributed-revision-control/2563917#2563917">publication process</a> (you pull from multiple repos, or quickly established intermediate repos to push to, where you can do intermediate tasks like continuous integration tests)</li> </ul> That last point required the most "change in thinking" and is a bit scary ("I can pull from any repo?!") But once you realize the benefits, you can really have more productive development cycles because you are able to monitor (by fetching commits from your peers) the development of some of your colleagues. If they are developing a function that you need, you can start integrating it sooner. (The thing to remember with a DVCS is that is doesn't prevent the setup of a "central" repo, for other developers to pull from) As for continuous integration, instead of pushing directly from your repo to a central server in charge of CI, you can push to a local repo on your desktop, which will run all the tests, before pushing automatically (if "green") the code to a "central" repo. It is so effective that you can now push to the official central repo a code that "never breaks the build", rendering your CI server pretty much useless ;)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat are the advantages of a distributed version control for a team that is effectively never distributed?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USVonC
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks. The points about easier integration and improvements to continuous integration were exactly what I was looking for.
 singulars
 PostPostId
 PO
 UserUserId
 USlukeck

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.