On Thu, Oct 1, 2009 at 9:20 AM, Peter Firmstone <[email protected]> wrote:
> -Major Release, new Features, Packages & API, API Changes that Break Source > (compile time) compatibility but not binary (runtime) compatibility. What are you going to call a release that breaks binary compatibility? Personally, I think this requirement is too ambitious. If source compatibility is broken, you might as well allow for binary compatibility to break as well. I doubt the constraint is valuable enough, and instead try to keep both source and binary compatibility as long as possible and aggregate changes into any major releases very seldomly. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug
