10.5 issues

Hey folks,

Before I start, this may all change by next week. But here’s what I/we have so far with regards to 10.5

So with 10.5 we’ve got some issues, like we always do with releases. The main problem we’re going to have here with fixing them is that folks who legally have access to 10.5 right now who are having issues are still under an NDA regarding 10.5. However, due to the GPL, any changes released in a binary must provide source code should the person request it. We typically release source with a release because that’s just the right thing to do.

So we’re between a rock and a hard place. It’s caused at least one person (a user who is not affiliated with the Adium team in any way) to question the project in general.

Here is what we’re going to do. If you have 10.5, you went to wwdc. If you spent all of the money going to wwdc, you are most likely a developer. So, we need your help fixing things. Some of our developers are at wwdc and have access to 10.5, but of course we don’t have the assortment of things with the 10.5 situation that we normally would, i.e., beta testing to a mass audience.

So, if you have 10.5 and you notice a crasher or a problem, if you can create a patch which doesn’t reveal any of the new API’s in 10.5, that would be the best way of getting things fixed. Even a patch that disables the feature on 10.5 is OK by us, if there’s no other non-compromising alternative—we’ve already done this with the Image Picker. (And yes, we will bring back the feature when 10.5 is released, since the changes needed to make it work will then no longer be covered by NDA.) If you have another solution, please post them in the comments here.

What we don’t need are tickets saying that something crashed but with no patches. We can’t do much of anything with them without asking for logging normally, which may (doubtful, I know, but still) reveal some private info which would violate your NDA in some way. Right now tickets without patches are just being closed asking folks to reopen them if they are still issues when 10.5 final is out.

Licenses suck. NDA’s suck. Ugh.

Anyhow, so if you have any questions about this, have suggestions, or whatever, hop on into #adium on freenode, or comment on this post. We’re open to suggestions.

If someone from Apple Legal were to give us confirmation that we could post commits with the new API’s in them to our subversion repo, I’d be more than thrilled.

We basically don’t want people sued over breach of NDA due to something submitted to us.


  1. Honestly I can’t see how anyone could expect you guys to do anymore than you’re doing.

    People, especially developers, should know that by installing beta software there are going to be issues. Being a prat because someone(s) are attempting to err on the side caution (regarding the NDA’s), is just silly.

    Keep up the awesome work!

  2. didn’t you just reveal that the image picker API has changed, and thus violate NDA?

  3. As far as I know, WebKit already uses 10.5 APIs (like the new APIs for Objective-C 2.0), and has done so for quite a while (side note: I don’t have 10.5). That certainly sounds like it would be acceptable post commits with new APIs.

  4. @ian No, we didn’t actually. We use a private call there and are being prudent by turning it off, assuming that it changed since we “borrow” it from iChat, which probably changed with 10.5.

  5. (Actually, borrow it from Address Book, which is where iChat gets, it too — but the point remains that it’s one of the few private APIs Adium uses.)

    In any case, the Objective-C 2.0 API is public, because gcc is open source. Additionally, making changes which fix bugs in 10.5 without utilizing new 10.5 APIs is perfectly acceptable by the terms of the NDA.

  6. This is utterly ridiculous. Yeah, it is a short term problem where 10.5-related bug fixing is, for all intents and purposes, stopped for the public, but it is only a temporary thing. An NDA is an NDA and you are just playing by the rules. Forks should be reserved for extreme circumstances; stuff like the fiasco.

    Thankyou (most of the) Adium team for still making sense, and I look forward to future releases.

  7. I have an idea, i didnt know where to post it so i’ll just lay it out right here. For the chat transcripts, they should be able to be saved. All of them, for example..I want to reformat my drive, and take my transcripts with me. There should be some sort of simple option to save them. I dunno, just an idea.

  8. is there possible to fix message visualization with the new safari 3 beta webkit?

  9. @nishad joshi

    it’s in big red letters at the top of the page…

  10. nishad joshi: The place to request features is the RequestingFeatures page, which you can find from the “Support & Development” tab.

    There’s no need to request that one, though, as we already do that. Transcripts are saved in Library/Application\ Support/Adium\ 2.0/Users/Default/Logs, unless you turned off logging in the General prefs.

  11. thanks a lot, and sorry about the request in the blog comment thing.

  12. i would write an mail to ADC and just ask them. probably there are some adium users over at ADC, so maybe you’ll find someone willing to help.

    as someone before pointed out. webkit is already using new api’s.

    what about setting up a private trac for the 10.5 guys. the problem will be: how to check if someone really attended wwdc (posting a pic of the badge on flicker.. haha) 😉

  13. 10.5 WWDC Seed is now availiable for the rest of you ADC members via ADC Login, so i consider this problem is now solved 🙂

  14. Every page in in the developer site contains a warning that pre-release software is confidential information.

    The seed is only available to those with a seeding key (mine has expired).

  15. sorry. i missunderstood an adc mail. but it WILL be availiable very shortly to ALL adc members.

  16. now the wwdc built has been released to all adc members. so happy hacking! 🙂

  17. not all members, but at least select and premier.

  18. Im having problems, i keep having disconnecting problems.

Post a Comment

Logged in as - Logout