|
08-13-2013, 04:04 PM | #1 |
Member
Join Date: Mar 2011
Posts: 40
|
If it's a Beta release who cares if it's signed. Any developer knows how to bypass the unsigned and since we are getting it directly from the source we know it's trustable.
When you release the final version though I'd suggest signing it - but if you have something that we can test now, just put it up. We'll understand if we have to bypass the security. |
08-13-2013, 05:59 PM | #2 | |
Junior Member
Join Date: Oct 2012
Posts: 16
|
Quote:
Thanks in advance for considering... |
|
08-14-2013, 08:06 PM | #3 |
Member
Join Date: Oct 2011
Posts: 52
|
Not sure if it'll do any good, but I'm also in favor of an alpha release. Given how long it's taking Apple to fix all the 10.9 bugs I figured you'd be interested in us maximizing the amount of testing and the giving Apple the maximum amount of time to fix things before they cut bait and just release 10.9 to meet their deadlines. Seriously, I'd reckon you have more to gain than lose by letting Mavericks beta-testers try to improve your product...
|
08-21-2013, 09:02 PM | #4 |
Junior Member
Join Date: Jan 2013
Posts: 6
|
A month on and....
It's 5 days shy of a month since Apple developer sites were brought back up, and still no signed driver. I know Apple is a slow machine, being an app developer, I also know it doesn't take a month to get a signed kext. There has to be way more to this.
At this point the release version of Mavericks will be out before any update to the drivers. The release history for Windows shows releases happen on a frequency of almost 4 to 1 over Mac, hardly something that one can blame solely on Apple or its delays. This seems more of a resource issue than anything. |
|
|