Re: River and Backward Compatibility
Mike Morris <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Dan Creswell wrote: > Following Jim's advice, I'm pushing this discussion over to our other lists. > > Any thoughts from the community on how much backward compatibility is > desirable in the first releases from River much appreciated. Respectfully, I have to disagree with those who have said "chuck backwards compatibility overboard." Anybody who has a significant deployed installation (I don't) will have nightmares at the thought. My fear is less about compiled code than about all the deployment scripts, permissions files, etc., that will need to get modified along the line in a production setup (assuming, too, that I've understood the framing of Dan's original question.) Important to remember, IMHO, that the primary purpose of this next release is to get the River community working within the Apache framework, adapting the long legacy of Jini Community ways of thought, ideas, etc. to Apache norms and processes. My 2c-worth: change the absolute _minimum_ that /must/ be changed (package names, what else?) to get the release out. Nothing else. As close as possible to 100% backwards compatibility. Bear in mind that Jim Hurley has also proposed a follow-up release fairly soon after the first River release (IIRC November sometime?); /that/ would be the point to start making incompatible changes. i.e. This release is about process, not about the codebase or packaging. -- mike morris :: mikro2nd (at) gmail (dot) com http://mikro2nd.net/ http://mikro2nd.net/blog/planb/ http://mikro2nd.net/blog/mike/ -- A day without chillies is a day wasted -- -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]