[Adium-devl] Leopard Tickets
David Smith
catfish.man at gmail.com
Wed Jun 13 18:06:56 UTC 2007
On Jun 13, 2007, at 10:48 AM, Evan Schoenberg wrote:
>
> On Jun 13, 2007, at 1:33 PM, Eric Richie wrote:
>
>> Obviously we can't commit fixes for the issues mentioned and it's
>> also
>> possible that the issue itself could change before it goes final.
>> Should we
>> just make an official policy of closing them as invalid and telling
>> the
>> submitter to reopen it one release day if it's still a problem, or
>> should we
>> keep them around for those of you running Leopard to maintain
>> locally and
>> then commit as soon as it's no longer NDA'd (yes, I know, October
>> is a VERY
>> long time from now so I don't really like this idea either). Just
>> looking
>> for some additional input on this issue.
>
> Fixing Leopard bugs is not a violation of the NDA. Revealing non-
> public information, however, is. Since, generally speaking, all
> programs which run on 10.4 should be able to also run on 10.5 so
> long as they are not (a) using deprecated APIs which were removed in
> 10.5 or (b) taking advantage of coincidental bugs or internal APIs
> of 10.4 which are fixed/changed in 10.5, it should be the case that
> all crashes in 10.5 can be fixed using only 10.4-compatible code.
> The betas exist so that programs are compatible with Leopard from
> Day 1 of its release.
>
> If the crash is a result of a 10.5 beta bug, of course, it's a
> different story -- one hopes the issue itself would change before
> 10.5 is final. Such crashes should be milestoned "Waiting on Apple"
> with a note that this appears to be a 10.5 regression; a developer
> with official access to the Leopard builds should file a radar and
> note the radar number in that ticket.
>
> -Evan
How about private APIs we use on 10.4 that no longer exist on 10.5,
but do have a new public version in 10.5? :(
(the buddy icon picker)
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070613/bd74cbf1/attachment-0001.html>
More information about the devel
mailing list