I like to think of Daily Builds as living on the bleeding edge. For the most part, daily builds are “reasonably stable”. Corona Labs does a pretty good job of unit testing the things they are releasing and I’ve had pretty good luck with dailies, only having had to roll back a couple of times. I’m feature driven. For instance when iOS 6 stopped showing print statements in device console logs and I’m doing things that need tested on devices (and the only feed back I can get from testers is console logs), there was no choice but to get the daily build that fixed the problem.
Given that bugs get fixed and new features added, I feel that staying up-to-date is important.
Now flip the coin. I have a couple of apps that use tableView’s that were built way back in the 720’s build number wise and I’ve not had to touch them. With today’s version (stable or not), I’m probably going to have to update the code to modernize it with today’s variant of tableView… But in this case I have to do it or my may not work with new devices.
In this case, if B&N can’t work out this DRM issue on their side and Corona Labs has to change something for us to submit apps, then you won’t have a choice but to upgrade. Now Coronal Labs did set a precedent with the retina iPad by going back to a previous stable build and updating it. But it was a pain in the butt on our part to deal with different versions of build 704. I can only imagine how much of a headache it was on their staff to have to maintain the code.
[import]uid: 19626 topic_id: 31547 reply_id: 126080[/import]