Re: River and Backward Compatibility
Dennis Reedy <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
> as the original > question was "How much backward compatibility does everybody expect in > this first release?". Greetings all, For the first River release I expect complete backwards compatibility. The first release should contain a next steps section that will document jars that will be deprecated (and why), a roadmap of changes that the community can expect, and thoughts around release cycles. If the River team can provide this, I think the first release will be able to set the stage for the upcoming changes. I certainly expect that subsequent releases will introduce backwards compatibility issues, package changes and potentially utilities to get from he JSK to River release x.y. I also expect that some adaptive layers can be created by members of this community. Bottom line, getting the first River release out is critical. The release should be easily folded into existing Jini technology based projects (I know I'll do this for Rio). Next, set the expectation that things are changing, and what consumers of the technology can expect. Regards Dennis -------------------------------------------------------------------------- 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]