[Adium-devl] [Adium-svn] rev 20408 - in branches/adium-1.1/Plugins/Purple Service/Libpurple.framework/Versions/A: . Headers

[Evan Schoenberg]

On Jul 29, 2007, at 6:29 PM, Andreas Monitzer wrote:

> On Jul 29, 2007, at 19:25, Evan Schoenberg wrote:
>
>> Trunk is tracking im.pidgin.soc.2007.xmpp rather than
>> im.pidgin.pidgin ('trunk').  Andy has been periodically using mtn
>> propagate to get the libpurple 'trunk' changes into im.pidgin.soc.
>> 2007.xmpp; I've been handling adium-1.1, which is the real current
>> concern as far as I'm concerned, and letting him do trunk's
>> libpurple with his changes.  (Of course, eventually im.pidgin.soc.
>> 2007.xmpp will be merged back to im.pidgin.pidgin)
>
> Ah, I didn't know I was supposed to commit updated versions of
> Libpurple.framework to trunk :) I'm compiling the current version
> right now, I'll do it right away.

You didn't know because nobody ever mentioned it and we hadn't  
discussed it :)

I hit reply-to-all at the last moment; I should have revised a bit so  
that my email worked better as a mass message rather than just a  
reply to Peter.  Adium releases should track libpurple releases as  
much as possible.  I committed an update to adium-1.1 because  
libpurple is basically done for the next pidgin release (the  
remaining issues have to do with the pidgin UI), and I wanted to get  
it in there for the next 1.1 beta so we can make sure there aren't  
new issues... we were already on an in-between revision (between the  
last release and the next one) so it made no sense to keep it there  
until the release happened.

Trunk can track the xmpp branch as closely as is desired, but there's  
no need to stress out or go to undo efforts to have it be 100% up to  
date in terms of propagating im.pidgin.pidgin all the time.  With the  
scripts we have it's easy to update and build Libpurple.framework,  
but I wasn't doing so for trunk/xmpp because I wasn't sure how up-to- 
date your propagates were on im.pidgin.soc.2007.xmpp.  It's so hard  
to deal with monotone revision numbers at a glance, at least from the  
rss feed (perhaps some tool could ease the process?) :\

-Evan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070729/0b3a5325/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070729/0b3a5325/attachment.sig>