please read: new "filtering" feature need testing *now*

[Pierre-Yves David]

Mercurial 2.5 is the first release to use "low level filtering". This
new feature is a very big change in the way mercurial internal works:

- Low level filtering likely introduce bugs in Mercurial.
- Low level filtering is **very likely** to breaks third party code.

There is still one week to report and solve those issue before 2.5
release, please help.

You can help by testing both Mercurial and third party extensions.

A) Testing third party code
B) Testing secret changesets
C) Testing obsolete changesets


A) Testing third party code
---------------------------

Internal representation of a repository have been altered since 2.4.
this may break some third party code.

Tests the behavior of third party extensions and visualisation tools
with 2.5-rc and report any issue to their maintained

Discussion about how to solve the issue will happen on
mercurial-devel at selenic.org.

B) Testing secret changesets
---------------------------

The changes affect the way secret changeset are internal handled in
several place. If you are a secret changesets please make extensive
testing of them with both Mercurial and third party code. Some
regression have already been found for secret changesets server-side
(issue3783).  Carefully test this setup.

When you find a bug, check if it is already in our regression list:

http://bz.selenic.com/buglist.cgi?keywords=regression&resolution=---&list_id=1890

If it is, add a description of your instance of the issue.
Otherwise, create a new issue


C) Testing obsolete changesets
---------------------------

Obsolete changeset are now fully excluded form all commands. Obsolete
changeset are part of the changeset evolution plan[1].

If you are an early evolve[2] user, please test 2.5-rc with whatever
official or third party extension you use.

If you are the maintainer of a third party code, please test it with some
obsolete changesets:

1) with an obsolete changeset somewhere in the history
2) with an obsolete changeset changeset somewhere is the domain of
   activity of the command/extension used.
3) test with tip most part of the history fixed

Example of resulting fix: http://selenic.com/hg/rev/07771e233cf1

When you find a bug, check if it is already in our regression list:
If it is, add a description of your instance of the issue.
Otherwise, create a new issue


Happy testing

-- 
Pierre-Yves David

[1] http://mercurial.selenic.com/wiki/ChangesetEvolution
[2] http://hg-lab.logilab.org/doc/mutable-history/html/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130125/a2659f1e/attachment.asc>