The truth is that none of the 26.3 betas have fixed the errors reported in 26.2. As for error resolution, Apple has been very lazy lately, let's hope that in beta 3 or RC of 26.3 we will have good news in this regard, because 26.4 will come with many changes and a base that is as solid as possible would not hurt to start the path in the best possible conditions.They sure do take their time not fixing any bugs…
That’s not how it’s working . 26.4 has probably existed for months already. Maybe even before 26.0 went public. Fixes and changes in the meantime is merged into 26.4.The truth is that none of the 26.3 betas have fixed the errors reported in 26.2. As for error resolution, Apple has been very lazy lately, let's hope that in beta 3 or RC of 26.3 we will have good news in this regard, because 26.4 will come with many changes and a base that is as solid as possible would not hurt to start the path in the best possible conditions.
That they have been working on a smarter Siri is not debatable, but 26.4 I'm almost sure that it came into the picture when they signed the deal with Google. and I think that happened at some point in the 26.2 beta cycle, hence the atypical releases. I think that from that moment on, 80% of the development team is focused on 26.4, leaving fewer people working for the current version and hence these delays in the schedule or even a skipped week in the beta cycle of 26.2, which we can see in 26.3 as well.That’s not how it’s working . 26.4 has probably existed for months already. Maybe even before 26.0 went public. Fixes and changes in the meantime is merged into 26.4.
They'd have to acknowledge the bug before fixing it 😉They sure do take their time not fixing any bugs…