Kristian, On Mar 8, 11:01 am, kristian <[email protected]> wrote: > since I have at least one or two libraries which produce a lot of > deprecated warnings which is not a problem as such. but I am worried > about these deprecated features to disappear in the coming release of > DM. these libraries use dependency requirement: > > ~> 0.10.1 > > which I understand to be the range [0.10.1, 0.11.0) - see > alsohttp://docs.rubygems.org/read/chapter/7#page26- but seeing the last > digit to be the minor version number in DM. > > so this is just to verify that DM is following such schema or what > versioning schema is DM following ?
Well, for the most part we have been following that, but we've been mostly considering anything pre-1.0 as not having a totally "stable" API. Anything 1.0 and greater will be guaranteed to work, perhaps with deprecation warnings in some cases, at least until 2.0. Perhaps until we reach 1.0 it'll be better to think of a Category 3 change as changing the minor number (eg. 0.10.0 -> 0.11.0), and a Category 1&2 change as a build number increase. I'm not sure if there will be a bump from 0.10 -> 0.11, at the moment it doesn't look like it will be necessary -- 0.10 will likely be the last series before 1.0. As a side note, I know deprecation warnings suck. I wish there was a way to avoid them. Well, I guess just not making the change would avoid it, but that's just dumb. Another way to avoid them would be to have perfect foresight and do it perfectly the first time, but that's not realistic. If we can make the API more consistent and/or easier to use, then the longer we hold off making the change the worse it'll be for everyone. IMHO it's better to bite the bullet as soon as you decide to make the change than to hold off until some unforeseen point when it won't be as much of a pain. The whole reason DM exists is because we wanted to provide a cleaner/ simpler/more consistent API than other Ruby ORMs, and for the most part I think we've succeeded, but it seems wrong to start becoming scared to make incremental improvements before we've made any guarantees of 1.0 level stability. BTW any upcoming API changes will be documented on the DM 1.0 Roadmap in case you're interested: http://wiki.github.com/datamapper/dm-core/roadmap If you have any comments or questions about the Roadmap, please feel free to bring it up on the mailing list or on IRC. -- Thanks, Dan (dkubb) -- You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.
