Some initial impressions of phases

[Martin Geisler]

Pierre-Yves David <pierre-yves.david at logilab.fr> writes:

> On Tue, Jan 24, 2012 at 12:48:55PM +0100, Jason Harris wrote:
>> 
>> On Jan 24, 2012, at 12:22 PM, Pierre-Yves David wrote:
>
>> Point 13:
>> BTW for the documentation there is no help in the hgrc about phase.
>> Eg 'hg help hgrc' doesn't mention anything about phase settings.
>
> breaking news: Phase documentation is still a stumb and something to
> be heavily working on during the freeze. Any help is welcome on this
> side.

I think Jason's overall point here is that it's dangerous to go into a
code freeze with an entirely new and undocumented feature. I must admit
that I'm also somewhat nervous about this.

So far I guess you and Matt are the only one who know how phases work.
The rest of us have played around with it for maybe 5 minuttes each. We
haven't done serious work with phases and so we're afraid of how it will
impact the release. Especially since there's no comprehensive end-user
documentation.

>> It might be simple, but it's highly highly inconvenient for working
>> with clones. This is really a case where we should separate what is
>> easy to for implementation and what works well for users.
>> 
>> At least there needs to be *some* way to get the behavior that most
>> users will find the most useful.
>
> There is a way. Setting your development repositories as "private"
> (not public, not publishing). This is simple and *available in 2.1*
> way to do that.

Is there a concept of a "private" repository?

Anyhow, I can see that adding

  [phases]
  publish = False

to my config file means that 'hg clone' preserves draft changesets as
drafts.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://www.aragost.com/mercurial/customer-projects/