GM Seed available on the dev site

[mizxco]

Mason!! What do the numbers mean, Mason!!

 

[KingOfStuff]

 

[redpandadev]

This seed will not be the GM. It's likely a GM candidate. The build number still has a letter after it. The only publicly shipping Mac OS with a letter at the end are machine specific builds that come loaded on new hardware when it's released mid-OS cycle. The next point upgrade always merges the OS back together. This will not be the GM. Guaranteed.

15A282b

15=Major (kernel) version
A=First point release (x.x.0)
282 = 282nd build in the above build hierarchy
b = This build was made for a specific target audience (AKA developer beta, public beta, internal beta, machine specific, etc.) There does not appear to be a specific meaning to the letters (b might be developer beta this time but might mean something totally different next time). No letter = public release.

They've always followed this convention, all the way back to 10.0.0

 

[lenard]

Same here, but it shows downloaded and I am unable to download....hmmmmm

I have downloaded but does not go to install and its grayed out. Can I get a new redeem code?

 

[matreya]

I couldn't download the GM Candidate via the Mac App Store on my iMac which had PB6 installed on it, so I tried the Mac App Store on my MBPr running 10.10.5, went to Purchased and it allowed me to download the GM Candidate, so I copied it back to my iMac and installed it that way. Build 15A282a

 

[tywebb13]

15A282a is public gm.

15A282b is developer gm.

 

[IeU]

If i install this, will i be able to do update from this candidate to maybe the final version (if this is not the final)?

 

[Erdbeertorte]

If i install this, will i be able to do update from this candidate to maybe the final version (if this is not the final)?

I think there will be no update because the last GM Candidate will be identical to the final version. You can use the full installer of the final version to "update".

Edit: Until then you might get updates to GM Candidate 2, 3, ...

 

[tywebb13]

It wasn't for yosemite though. The final GM for yosemite was not the same build number as first public release. And no delta update was available for that. One had to do it with the full installer.

 

[Siannath]

This seed will not be the GM. It's likely a GM candidate. The build number still has a letter after it. The only publicly shipping Mac OS with a letter at the end are machine specific builds that come loaded on new hardware when it's released mid-OS cycle. The next point upgrade always merges the OS back together. This will not be the GM. Guaranteed.

15A282b

15=Major (kernel) version
A=First point release (x.x.0)
282 = 282nd build in the above build hierarchy
b = This build was made for a specific target audience (AKA developer beta, public beta, internal beta, machine specific, etc.) There does not appear to be a specific meaning to the letters (b might be developer beta this time but might mean something totally different next time). No letter = public release.

They've always followed this convention, all the way back to 10.0.0

Would be correct to assume that something like this happens with iOS build numbers?

 

[treichert]

It wasn't for yosemite though. The final GM for yosemite was not the same build number as first public release. And no delta update was available for that. One had to do it with the full installer.

Or you simply did nothing and updated to 10.10.1 when it arrived, as that updated both builds. Problem solved.

 

[Sappharad]

This seed will not be the GM. It's likely a GM candidate.

It is most definitely not going to be identical to the release version, I agree. With each recent release since Snow Leopard, I've always made a bootable flash drive so I can upgrade all of my macs in addition to using it for recovery. Last year's GM image produced a volume called "Install OS X Yosemite". On creating a bootable drive from the new build, (using the embedded createinstallmedia tool) the volume name of the resulting drive is "Install OS X El Capitan GM Candidate".

They won't be shipping a build that mounts a volume with GM Candidate in the name. It's possible they might not change anything inside of the release build, but even if they don't the build number and volume name still need to change for the final release.

Not sure if anyone noticed that yet, I may have missed it.