[RFC] Anti-AsyncCalls

Following some detailed discussion around the AsyncCalls issues and why
it blocks 3.1 release we have come to the point of withdrawing the
current implementation.

With one conditional; if during the reversal TMF can complete and
satisfy the rest of the developers that the blocker issues have been
completely fixed it may be aborted.

My plan for this is to;

   tag HEAD for re-reversal, then branch a duplicate of the current
3-HEAD into launchpad for public preservation. This is to provide a
fairly stable branch where AsyncCalls can be matured past its current
problems before a re-merge is requested.

Following that; the reversal of known AsyncCalls patches from HEAD.

This to start on HEAD early September. Though initial testing will begin
in private by me almost immediately.

Followed by several weeks where 3-HEAD is to be tested for stability to
locate any assumptions in code subsequent to AsyncCalls merge.

When 3-HEAD is deemed stable, to make a 3.1 release with all other
current features. Then strike out again down the RoadMap.

Goalpost #1 is to have 3.1.RC1 on the web before 31 October in a stable
and usable state.

Maybe fanciful, but...

Goalpost #2 is to have 3.2.PRE on the books and relatively stable with
limited features for performance testing by January 2009.

Amos

-- 
Please use Squid 2.7.STABLE3 or 3.0.STABLE8