I'm starting a review of the public API changes for 1.7.  This is what I
intend to do.  If you have done or are doing any of these, or think of
other things, please say.

  * Check that all changes from the 1.6 public API are marked as new or
deprecated as appropriate.

  * Check that new functions have sensible signatures (prototypes) and
semantics and seem suitable for being public.

  * Check that wrapper implementations of deprecated functions look at
least vaguely likely to be correct.

I'll fix any trivial things, and post separately about anything that
looks like it needs more eyes on it.

I'm comparing 1.6.17 with trunk@1130950.

- Julian


Reply via email to