Question

Hello! I have two questions:

1) There are two options when you create a new branch: "Central repository" and "Branch Repository". What is the difference between this two approaches? As I understand in both cases Kiln creates full-fledged Mercurial repositories. Yes, I've noticed that there is difference in how repositories appear in web-interface and I can do everything with original repository and branched repository if I choose "Central Repository". But are there any more essential or functional differences?

2) What does the field "Parent Repository"? If I set "Parent Repository" field for the repository, I can do the same things with it, as if "Parent Repository" field is empty. Please correct me if I am wrong.

Thanks!

Update: Today I created a new "Central Repository" branch and Kiln automatically set "Parent Repository" to the original repository. But then I pushed some changes in the branch and got an error: my branch repository doesn't has the same history of changesets as parent repository and Kiln set "Parent Repository" of the branch repository to "None" for me to solve the problem. (I don't remember exact message. I think it would be useful to have ability to see the history of notifications.)

Why this problem occured? I think it's obviously that history of changesets may be different for some time. And how "Parent Repository" field works in this case?

Answer 1

Hey Anton,

The difference between branching to a "branch repository" or a "central repository" is really just a UI distinction. The distinction is there for a reason, though. We found that during the course of development there were some repositories that we created that were just "more important" than others. The central repository is there to say, "This is the repository that we all share, and I should take a second to think before a plop a broken feature in here." The branch repository is there to let you move feature development out of a central repository while still giving an indication that the feature is ultimately going to be delivered to the parent. There are no real functional differences, however, and we are actually working on a feature that will let you "promote" a branch repository to become a central repository.

The Parent Repository field is there to set the default target of the "Outgoing" tab and the "Push" control. It can be thought of as the default path for the repository on the server (to borrow from Mercurial's terminology).

I don't fully understand the situation you mention in your update. If you can reproduce the problem, please send us a screen shot to customer-service@fogcreek.com and I will see if I can sort out exactly what happened.