Performance branch review strategy

Hi devs,

During the Apache Retreat we came up with a plan
how to review larger parts of the performance branch,
so that these parts may be become part of 1.7.

We identified the most promising parts and I will
present these patches in a way / grouping that they
can be reviewed somewhat easier. In addition to
that, I will post a list of smaller, independent revisions
for the "review snack on the side".

Once these patches have been reviewed, there will be
some risky changes (file handle cache - not part´of 1.7)
and a number of smaller improvements left on the branch.
Depending on the progress of 1.7, I would then either
select further patches or postpone their integration.

Due to the regrouping of changes, some revisions will
only get merged partially. Before closing the branch,
the leftovers should therefore be identified by diffing
against /trunk (likely sometime during 1.8).

-- Stefan^2.
Received on 2010-09-19 21:59:16 CEST