Call it what you want, it’s software testing in flight.Its more an alpha program
(intrinsically unstable, features pulled)
Call it what you want, it’s software testing in flight.Its more an alpha program
(intrinsically unstable, features pulled)
This is beta device, thanks for the tip.
[doublepost=1534244758][/doublepost]
Yeah, on a beta device an now I must waste the time to restore it.
[doublepost=1534244811][/doublepost]
This is beta device, thanks for the tip. Next snarky response?
Speaking as a developer, I don’t know why you’d be so upset about this issue if it were on a device solely used for testing or why you’d refer to a test device as “my X,” and iOS devices take next to no time to restore, but whatever you say...Yeah, on a beta device an now I must waste the time to restore it.
I dont see a repost in the Apple developer portal....I skipped the beta yesterday. Too busy. It's reposted and downloading now to my X. *crossing fingers*
Just amazing how a trillion dollar company still releases heavy broken beta versions, and can’t manage to test/qc by theirselves.
Amazing how many people keeps defending Apple. In my opinion a trillion dollar company shall not depend of external beta feedback at all. They have enough money to setup an armada of paid testers, and simply just release final versions. But why invest if you can have testers for free. Their plan works out. This just reflects their greedy attitude, which also can be seen in their current bug bounty program. They should at least pay us for each non duplicated bug report.
That's weird. I wonder why the performance would get better with time. Oh, by the way, you are famous now!![]()
Yeah but I can't think of many times they've had to actually pull a beta this late in the process. That a bug that big could make it through a month from launch is not a great sign. By now most of the big bugs should be worked out or at least well documented. They didn't even know it was in there!Actually, it's a great sign. It's called a BETA TEST and they found a problem, removing the BETA. Exactly the way it's supposed to work.
That a bug that big would have made it into production, would have been bad. That it was caught in a beta, where these types of bugs are supposed to be caught, is great.Yeah but I can't think of many times they've had to actually pull a beta this late in the process. That a bug that big could make it through a month from launch is not a great sign. By now most of the big bugs should be worked out or at least well documented. They didn't even know it was in there!
I'm not arguing that it's not a good thing that it was caught! What I'm arguing is that it's pretty late in the process to be finding bugs that big which is a troubling sign that there are other big bugs in there which may not be caught in the time remaining before launch. Do you understand? You expect lots of big bugs early in the process, not late. Therefore it's a troubling sign, nothing more, nothing less.That a bug that big would have made it into production, would have been bad. That it was caught in a beta, where these types of bugs are supposed to be caught, is great.
I understand.I'm not arguing that it's not a good thing that it was caught! What I'm arguing is that it's pretty late in the process to be finding bugs that big which is a troubling sign that there are other big bugs in there which may not be caught in the time remaining before launch. Do you understand? You expect lots of big bugs early in the process, not late. Therefore it's a troubling sign, nothing more, nothing less.
Same here. iPhone X (Qualcomm) 64Gig. OTA, about 30 mins after b7 was released. Odd. Working great this morning as well, even after a reboot.Been running B7 since it dropped and I did not have a single issue whatsoever.
When I may call it as I like, I’d opt for:Call it what you want, it’s software testing in flight.
Or one could call it the greatest thing since sliced bread. Whatever it’s called it’s not going to change the outcome.When I may call it as I like, I’d opt for:
Misusing customer eagerness and overhype to compensate the lack of structural internal testing.
This is not how software engineering works. Fixing bugs (and implementing new features) will sometimes introduce new bugs which will not necessarily be less major than the bug/feature need that preceded the work. In other words, sometimes implementing a new feature or bug fix introduces even worse bugs. It happens! And it’s fixable, of course, but it takes time.What I'm arguing is that it's pretty late in the process to be finding bugs that big which is a troubling sign that there are other big bugs in there which may not be caught in the time remaining before launch. Do you understand? You expect lots of big bugs early in the process, not late. Therefore it's a troubling sign, nothing more, nothing less.