Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

EricJD

macrumors regular
Original poster
Aug 15, 2007
169
0
I have my computer registered to install beta updates, but the App Store refuses to acknowledge this and is not showing the 10.10.3 update.
 

Attachments

  • Screen Shot 2015-02-12 at 6.20.33 PM.png
    Screen Shot 2015-02-12 at 6.20.33 PM.png
    229 KB · Views: 141
  • Screen Shot 2015-02-12 at 6.21.59 PM.png
    Screen Shot 2015-02-12 at 6.21.59 PM.png
    58.8 KB · Views: 103

redheeler

macrumors G3
Oct 17, 2014
8,626
9,275
Colorado, USA
Thought so. It seems like every Apple news blog was reporting it as "available to the public."

Yes, I do find it quite disappointing that people in the Public Beta (which I'm sure give plenty of helpful feedback on updates like this) are still being withheld from. There's just no excuse for it.
 

tywebb13

macrumors 68040
Apr 21, 2012
3,079
1,750
It is better to release to developers first before it goes to public beta.

If there is some serious bug with an early beta, developers are usually better able to deal with it than the public. Less computers will be damaged this way.
 

redheeler

macrumors G3
Oct 17, 2014
8,626
9,275
Colorado, USA
It is better to release to developers first before it goes to public beta.

If there is some serious bug with an early beta, developers are usually better able to deal with it than the public. Less computers will be damaged this way.

They could always give the option for Public Beta to receive buggier releases, yet they choose not to. 10.10.3 has been shown to be stable enough, however, so for this particular update that's not an issue.
 

cincygolfgrrl

macrumors 6502
Apr 2, 2012
346
227
Somewhere In Time
They could always give the option for Public Beta to receive buggier releases, yet they choose not to.
At the risk of appearing offensive, you'd probably just put it on your primary drive on your primary computer and then when all your data suddenly disappeared you'd whine that Apple destroyed your life.

There's a reason they don't do public beta releases for the first drop. And you don't really need 10.10.3 for anything right now, do you?

If you absolutely have to have it right effing now, spend the $99, or whatever it is these days, to become a registered Apple "developer."
 

redheeler

macrumors G3
Oct 17, 2014
8,626
9,275
Colorado, USA
At the risk of appearing offensive, you'd probably just put it on your primary drive on your primary computer and then when all your data suddenly disappeared you'd whine that Apple destroyed your life.

There's a reason they don't do public beta releases for the first drop. And you don't really need 10.10.3 for anything right now, do you?

If you absolutely have to have it right effing now, spend the $99, or whatever it is these days, to become a registered Apple "developer."

You seriously think I'd put a beta on my primary computer? My 13" rMBP has always gotten the betas, I wouldn't touch my Retina iMac with any sort of beta (unlike some people on this forum, hence all the complaints).

The Mac dev program is for serious developers who want to sign their apps and put them on the App Store, not for people who want access to the latest betas. Suggesting I spend $99/year just to get the latest betas is downright ridiculous.
 

cincygolfgrrl

macrumors 6502
Apr 2, 2012
346
227
Somewhere In Time
Suggesting I spend $99/year just to get the latest betas is downright ridiculous.
Whining that Apple isn't making the first release available to non-developers is just as ridiculous. You're the one who said, "Yes, I do find it quite disappointing that people in the Public Beta … are still being withheld from. There's just no excuse for it."

Back in the day the saying was "Put up, or shut up."
 

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
Whining that Apple isn't making the first release available to non-developers is just as ridiculous. You're the one who said, "Yes, I do find it quite disappointing that people in the Public Beta … are still being withheld from. There's just no excuse for it."

This, definitely this.

redheeler - There are perfectly good reasons for a phased release via Developer and Public beta's, one of them is that the public beta's are increasingly attracting inexperienced public users who simply want "latest version bragging rights"...

If you want apps updated promptly on public release then developers of same have to be given a head start to do so, for which they pay.
 

redheeler

macrumors G3
Oct 17, 2014
8,626
9,275
Colorado, USA
There are perfectly good reasons for a phased release via Developer and Public beta's, one of them is that the public beta's are increasingly attracting inexperienced public users who simply want "latest version bragging rights"...

I acknowledge you have a point here, an unfortunate side effect of the Public Beta despite Apple's warnings of buggy software. However, the builds that are released to Public Beta are beta quality software nonetheless, and whether or not Apple chooses to release the developer builds to Public Beta these users will still become aware of that fact.

If you want apps updated promptly on public release then developers of same have to be given a head start to do so, for which they pay.

This part is nonsense. The Public Beta could easily be given access at the same time as developers without hindering their "head start" to tweak their apps for the final release. What's more, smaller developers who choose not to pay will be given that same "head start".
 

simonsi

Contributor
Jan 3, 2014
4,851
735
Auckland
This part is nonsense. The Public Beta could easily be given access at the same time as developers without hindering their "head start" to tweak their apps for the final release. What's more, smaller developers who choose not to pay will be given that same "head start".

You need to consider that the Developer seed isn't the same SW as the Public beta, hence it can be made available earlier to developers who can use it to confirm the structural state of new code for new functions and carry out compatibility testing, but it isn't considered stable enough for the Public Beta program.

Its as easy as that, it would serve no purpose to make the Dev code available to the Public Beta users except to generate noise from those that shouldn't be in the beta program in the first place.

You may as well ask why production prototype cars aren't offered to the general public...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.