[Adium-devl] Synchronizing with libpurple

[Ofri Wolfus]

I'm not saying we should do it either, but isn't one of the goals for  
frameworks is to provide backwards compatibility (I'm speaking about  
that version/current directory structure)?

It seems to me that updating only the framework is the same as  
updating the entire app. In both cases the app would have to be  
restarted, so the only benefit of updating only the framework is a  
smaller download.

- Ofri

- - - - - - - - - - - - - - - - - - -
http://www.dpompa.com
- - - - - - - - - - - - - - - - - - -


On 29/05/2007, at 23:58, bgannin wrote:

> Just because it may be a separate framework does not imply API or
> feature parity. With any given update underlying parts may change in
> a way that exposes a new issue in previously fine code, creates an
> entirely new issue, or much more. This may not be the case, but its
> certainly a possibility. Moral of the story - being a framework (and
> if I recall correctly, we actually build the framework manually, not
> just 'get' it from Pidgin) doesn't mean you can assume a 1:1
> relationship at any time allowing replacement. Updating a core
> component requires a proper QA cycle to vet any breakage that may
> occur and shouldn't be foisted on the user to do so.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070530/24897e8d/attachment-0001.html>