RFC: Phase UI (revset, phase command and others)

[Jesper Schmidt]

On Tue, 03 Jan 2012 00:20:11 +0100, Isaac Jurado <diptongo at gmail.com>  
wrote:

> On Tue, Jan 3, 2012 at 12:05 AM, Jesper Schmidt <schmiidt at gmail.com>  
> wrote:
>>
>> Therefore I suggest that we call the final phase 'stable', since it
>> provides a stable foundation to build on, which is not the case for
>> other two.
>
> "stable" is a particularly bad name for a phase, as it can be very
> confusing if you do standard branching:
>
>     http://mercurial.selenic.com/wiki/StandardBranching
>

Okay, I don't use that branching model/naming convention myself, but I
agree that it is problematic since mercurial does.

What about 'solid' then instead of 'stable'?

I really think that 'public' is misleading since a 'draft' changeset
can be shared as well. Am I missing something here?

> If the "public" phase is the last phase, why not just call it "final"?
>
> Cheers.
>


-- 
Jesper