Toolkit Development Process - and API maintenance
I'm interested in understanding how Sun and other 'toolkit' providers manage their software development cycles to maintain public APIs from release to release.
I am currently part of a large software project which plans to deploy a large existing codebase as a toolkit for others to develop on top of. I'm concerned about our ability to manage changes to our public APIs once we provide our toolkit to external developers. Once they start extending our classes and interfacing with our APIs, we have to be very careful about what we change - and ideally we should have some way to 'deprecate' things.
How does a company like Sun manage this for the JDK? Or how do other companies that do similar things work through this? Anyone know of any good reference material (books / online / etc.)?
Thanks,
Aaron Schmidt

