> > If anything broke from the transition from 1.2 to 1.4, it is because you > were > using something that was deprecated in 1.2. What we had attempted to do > in deprecation modes was to print the warning ONCE for each deprecated > operation, per Asterisk startup. I think that this was much too > conservative. > It is very easy to miss that deprecation warning, since it occurs so few > times. Of course, the opposite side is that we don't want deprecation > warnings to fill up your logs, so there's a balancing act here. But we > could > probably do with making the deprecation warnings a bit more prominent > and print them multiple times (for example, every 10th usage). That > should > make it more clear that there's something to change. > > Of course, all of these deprecations should be covered in UPGRADE.txt, so > please read that file every time you upgrade to a new version. It will > contain everything that has changed in a possibly incompatible way. And > if > you find something that broke that wasn't in this file, please let us > know, so > we can revise that file. We may not have gotten everything, but we do > try. >
I don't think there is an issue with people reading UPGRADE.txt as there is re-doing all of our custom code. _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
