[Adium-devl] My status, and some 1.4 planning
evan.s at dreskin.net
Tue Aug 5 22:40:28 UTC 2008
On Aug 5, 2008, at 6:29 PM, Peter Hosey wrote:
> We should make sure they get bug fixes. They're still more than a
> third of our user base.
> The problem is that if we start rewriting stuff with Leopard-only
> APIs, providing bug fixes for Tiger users becomes much, much harder
> (since you have to find the bug twice, and maybe fix it twice).
When we dropped 10.4 support, at least, it didn't significantly
increase the difficulty of backporting fixes for quite some time.
However, if we're going to be actively moving large swaths of code to
10.5 code, new objective-C, etc. this might make such merges quite
> So I think we should continue with the original plan, of switching to
> 10.5-only closer to the release date of 10.6.
Does anybody else have strong feelings about this? I weighed in early
on with the same thought Peter is expressing, but I really want to
make sure that we're facilitating development in the best way possible.
>> (which I think is the bottleneck)
> Shark would like to have a word with you. ☺
Oh. Heh, you're right. The shark log in #10543 is all in
AudioContextSendMessage() after it's told to play. I wonder if the
same problem occurs if we haven't configured the aduio context to go
to the default alert output.
>>> Comments in the source indicate that the paranoid locking is due to
>>> SearchKit issues.
>> *grumbles about SearchKit*
> Do these problems in SearchKit still exist in Tiger? Do they still
> exist in Leopard?
Yes and yes.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 194 bytes
Desc: This is a digitally signed message part
More information about the Adium-devl