Kevin, You asked a very good question.
> I guess what I am proposing is: > ...... > - for each release, identify: > stable API's (if they exist :-) > experimental API's I wonder what the best way to identify experimental APIs is? I worry about just throwing something like that in the docs, because it's easy to miss that. Sure, someone needs to refer to the docs to use something, but maybe they're just taking a recipe they found on the wiki or something. Maybe experimental things should need to be explicitly turned on... (By the way, I'm thinking specifically about experimental APIs that are in releases. Nothing like that is necessary for svn versions, of course.) What about some varent of what python uses: from __future__ import ..... http://docs.python.org/ref/future.html ????? Mike
