doc: add more warning This is not "stable"

update implementation details

Doc: several update

Prepare 0.1.0 by merging default into stable stable is now compatible with 2.3 only.

pkg: rewrote the install process We now have a single extension. - enable is dropped - a setup.py is added - the doc is updated to reflect this

evolve: add the odiff alias

[pkg] Add a setup.py

Ignore build directory

update documentation

doc: some terms update

rename `stabilize` to `evolve` stabilize keep being valide but as Matt still like "Changeset Evolution" as a name evolve make more sense. Stabilize is a bit too tight to unstable too.

merge evolve and obsolete

sort import

Fix mercurial version check

Start a mercurial 2.2 branch This branch contains and old version compatible with mercurial 2.2. It's less complete and safe than later version.

update changelog

fix typo

evolve: stabilize now handle conflicting changeset Some a lot of rough edge but it just damn work.

stabilize: conflicting changeset are considered if "." if not unstable changeset are found, the current parent directory may be stabilize if conflicting

Introduction of olog as an alias This will won't stay as such long.

evolve: fold command First crude version of a fold command

evolve: touch command command to easily revive a changeset.

obsolete: ignore hidden changeset when resolving `branchname` revision

obsolete: add obsolete data to summary.

update changelog for upcoming 1.0

merge with stable improvement

[evolve] amend: display proper error message while trying to amend non ancestor

[evolve] amend: check phase before starting the transition We better abort before starting a useless transaction.

test: turn the base public usefull for followup that test phases enforcement.

obsolete: prevent bare hg update to select hidden changeset The issue remain with branch name.

obsolete: prevent rebasing of public changeset Because we force keep we have to check this on our own.

obsolete: warn when the whole rebase set was remove because extinct

obsolete: use flag to detect that a obsolescence marker fix a latecomer Otherwise latecomer fix will be latecomer too.

stabilize: handle latecomer Merge are not handled yet.

stabilize: rework stabilize code to allow selection of latecomer and conflicting They are still unhandled but the tool now explicitly state this fact.

obsolete: add a "troubled" revset returns all changeset with troubles whatever the trouble is.

stabilize: handle killed changeset in stabilize.

stabilize: --continue support !!! Based on graft one.

stabilize: rename "node" variable to "orig" It's a not a node at all. this is a context.

obsolete Move merge failure handling into stabilize code This violate less Layer. For this purpose we crate an easy to recognize Exception Class.

obsolet: fix extension help code about extension wrapping

merge

obsolete: filter out nullid from possible successors This have several bad effect as wrong late comer detection.

obsolete: more typos and cleanup

obsolete: fix indentation in obsolete import block

obsolete: fix docstrings

obsolete: simplify module docstring

obsolete: simplify rebase wrapping code and change relation creation We have don't have changeset simply pruned by rebase. When they disapeared, that means that destination is a valid successors for them.