I need some guidelines regarding how to deal with API changes (such as removing the "new" method).
I think those guidelines should become part of the "development-standards". Some random thoughts (not necessarily my opinions): - we'd rather have Right than Stable. - people _know_ the modules are unstable, but they don't _like_ unstability. - API unstability delays projects. - we know more-or-less which methods are stable - this could be documented. OTOH, we might know which methods are _less_ stable - we could warn the user. - API and "code" stabilize at different paces. Even if we have a stable API, the code might be "not for production". - at some point in the project, the API should try to keep itself backwards compatible. - Flavio S. Glock
