On Fri, Mar 17, 2006 at 11:47:08AM +0100, Martijn Faassen wrote:
> I'm not talking about a proposal. I'm talking about a document that
> describes the changes. I'd suggest basing it on the proposal as you're
> halfway ther already.
> What I'm asking for is change documentation per release, at least the
> beginnings of it, for at least the larger changes that impact end user
> code. Deprecation warnings are nice but in addition it's also nice to
> actually have a document that spells out what is going on and what you
> should be doing. It is also better for marketing as you can actually
> spell out the motivation for breaking people's code, instead of just
> presenting them with terse deprecation warnings.
Zope3-dev mailing list