Hi Dahlia, yes - thats to be expected, what you're talking about is our "trunk" branch which is what will eventually become 0.8 now that 0.7.0 is officially released. We maintain API and Binary compatibility for all all changes based on version numbering, for example 0.7.0 - 0.7.9 will stay compatible and not cause any breaking changes. (same is true for 0.6.x numbered versions). We've been doing this since around our 0.4.0 release over a year ago. we will maintain this policy at least until a "1.0" release so that as we continue to develop the library people can sticking to major revisions can expect not to have anything break. Switching from any major revision ie: 0.6 to 0.7 is guaranteed to introduce some breaking changes, major revisions like this give us the opportunity to atone for past sins we've made during the development of the library.
As the library is further developed towards 0.8 additional portions of what is now in "OpenMetaverse.dll" will be moved to "OpenMetaverseCore.dll", this won't happen in one big monster commit, but as incremental changes so time and care is given in unwinding the dependency mess we've currently got. Regards, Jim On Sat, 25 Jul 2009 16:17:39 -0700, Dahlia Trimble <[email protected]> wrote: > I've noticed one issue already with the "core" split after 0.7, references > that were originally resolved to OpenMetaverse.dll now are in the new Core > dll. This broke binary level compatibility with third party dlls, and > source > projects now need to be distributed assuming either configuration. > !DSPAM:370,4a6b9bdf312361612317443! _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
