no new GM release before launch?

[iMcLovin]

So since the launch of El Capitan is on wednesday I assume the current GM is the final version before release. If they have changed anything wouldnt they release another GM v.2 to developers?
I find this whole thing strange, because even I have all ready reported like 3 -4 bugs on the current GM and I wouldnt mind apple actually fixing the bugs before launching their OS.

Then again I have comitted bugs to Apple Maps 4-5 times since launch and none of them has ever been fixed, so I assume apple just simple dont care unless thousands of people scream and complain.

 

[beebarb]

@iMcLovin
While true that this is likely the only GM candidate prior to the release date, we have the possibility that the release build will differ slightly from the it, and since 10.11.1 is in testing already, it's possible some of the reported bugs in the GM candidate that weren't fixed will be addressed when that update is officially released.

 

[chrfr]

So since the launch of El Capitan is on wednesday I assume the current GM is the final version before release. If they have changed anything wouldnt they release another GM v.2 to developers?

Apple did not release the final retail version of 10.10 to developers except when it was released to the public. The same is all but guaranteed to happen with 10.11. The 10.11 GM Candidate was built on OS version 15a283, and Apple will want both developer and public beta users to be on a common build after the OS is released to the public.

 

[dogslobber]

So since the launch of El Capitan is on wednesday I assume the current GM is the final version before release. If they have changed anything wouldnt they release another GM v.2 to developers?
I find this whole thing strange, because even I have all ready reported like 3 -4 bugs on the current GM and I wouldnt mind apple actually fixing the bugs before launching their OS.

Then again I have comitted bugs to Apple Maps 4-5 times since launch and none of them has ever been fixed, so I assume apple just simple dont care unless thousands of people scream and complain.

Bugs need to be classified and prioritized. If a bug caused a kernel panic then that's one thing but if it's an annoyance that can be fixed in the next update then it will be. It's very expensive to fix bugs late in the release cycle as it increases risk to the release.

 

[MrNomNoms]

Bugs need to be classified and prioritized. If a bug caused a kernel panic then that's one thing but if it's an annoyance that can be fixed in the next update then it will be. It's very expensive to fix bugs late in the release cycle as it increases risk to the release.

It also has to be replicable at Apple to differentiate whether it is a hardware issue, a configuration issue or an actual bug with the operating system component itself.

 

[xgman]

And since Apple is already beta testing 10.11.1 . . . maybe they will just pull the plug and fix anything in the .1 release which is usually pretty soon after.

 

[maflynn]

And since Apple is already beta testing 10.11.1 . . . maybe they will just pull the plug and fix anything in the .1 release which is usually pretty soon after.

That's my thinking at this point, though I do find it odd to see the beta more or less just sitting there and not released while they roll out the .1 to developers.

 

[Queen6]

That's my thinking at this point, though I do find it odd to see the beta more or less just sitting there and not released while they roll out the .1 to developers.

To me 10.11 as ever is being released on a predetermined schedule, so all ongoing fixes will be pushed to .1 El Capitan is more commonly regarded as a "fix" rather than bringing an expansive set of new features, I am sure Apple does not want any more negative comments than are absolutely necessary regarding the new iteration of the OS.

The aggressive push by Apple releasing .1 Beta can be read two ways; Apple are looking to get ahead of ahead of the game and are placing more focus on OS X or the initial .0 release still has issue across a significant number of Apple`s hardware. Personally I be holding off until .2/.3 allowing the third party dev`s time to release updates to their Apps, coupled with I have zero issues across multiple Mac`s on 10.10.5 so the imperative to upgrade is currently low.

Q-6

 

[maflynn]

The aggressive push by Apple releasing .1 Beta can be read two ways;

I think this whole annual major release is a bit wacky anyways. I think they produced a better product when they didn't live by a 12 month release schedule.

I think though you're right - they're trying to get ahead of the bugs/complaints.

 

[Queen6]

I think this whole annual major release is a bit wacky anyways. I think they produced a better product when they didn't live by a 12 month release schedule.

I think though you're right - they're trying to get ahead of the bugs/complaints.

Same sentiment; I far preferred the 24 month cycle, OS X being a desktop OS I don't see any need or benefit for such rapid change, or needless complication, in some respects OS X is moving closer to Windows at each major release, with myriad options across the GUI that the majority of users will never use, terminal has always been the doorway for the OS X "Power User". Very much agree that when OS X was on a longer development cycle the OS was a better product.

For many 10.10 was only stable after the .3 release, now at .5 it`s basically done with, barring security patches, and so the cycle repeats with 10.11. Personally I want Apple to focus on security & stability, less on "bells and whistles" OS X is close to being in permanent "Beta", which is far from what I want, and it`s origins...

Q-6

 

[dogslobber]

And since Apple is already beta testing 10.11.1 . . . maybe they will just pull the plug and fix anything in the .1 release which is usually pretty soon after.

In the final days, they won't fix anything unless it will impact the stability of the release. E.g. a panic at boot time on a 2012 iMac or all the user's email being deleted from their account. If a bug is not deemed to be critical to fix, which is totally different from what you/I'd think of a critical bug as, then it will be fixed in the next point release. In other words, the build is pretty much 99.8% ready at this point for release.

 

[dogslobber]

That's my thinking at this point, though I do find it odd to see the beta more or less just sitting there and not released while they roll out the .1 to developers.

They have different release trajectories and predefined marketing release dates. One release is independent of the other release so you will get overlap for whatever reasons; maybe there's a lot of bugs that are minor so they're rolling them up quickly, like 9.0.1 is out a week or 2 after 9.0.