UPDATE (Monday 10:42 PM PST): Unfortunately, during this evening’s testing we found a rendering bug on Table View with auto heights. We’re working on a fix and hope to have it fixed before the morning. As soon as we fix this issue and can do another round of testing, we’ll have the release up. Stay tuned to the blog for updates. Sorry for the delay!
UPDATE (Monday 11:45 PM PST): Drop is now available. Details here.
For the past 4 weeks we’ve been working very hard and fast on 1.4 and we’ve made a ton of great fixes and improvements. We’ve already resolved several hundred issues and have a number of issues we’re trying to complete before the release.
We need your help.
In 1.3, we encountered a number of regression issues and unexpected problems — a number of them that we flat out should have caught in final testing. However, a significant number of them we’ve found are simply issues we just didn’t expect or didn’t have good test coverage for. As the community and number of apps have skyrocketed over the past few months, so has the impact on the platform and our ability to support you. We’re working as fast as we can (some of us, 7 days per week) and hiring as fast as we can. We thank everyone that continues to help out in Q&A, helping us find and reproduce weird issues and working with us with patience and grace as we try and help you with your problems. We also really appreciate when you say “thank you” and tell us how much you appreciate what we’re doing.
Going forward, there’s a few things that we’re doing on a Quality front that I’d like to outline here and to ask for your help:
- First and foremost, we’re adding full-time QA engineering. Up until recently, we had formal QA but it was done as a part-time activity by several of us near the end of a release cycle. I’m proud to announce we’ve recently hired our first full-time QA engineer that will simply do nothing but test, build tests, run more tests and work with you to get your issues so we can build more tests. Every…single…day. Proactively, as it should be done.
We’re working on several fronts around automated testing both for the platform itself but also something that would be useful to you – as you test your own apps. This is going to take some time to work through and we’ll do it like we do everything else, in a number of iterations. The first iteration is that with 1.4 we’re going to be introducing a new command line tool that will allow you to do some of the common tasks in Titanium Developer from the command line. For example, you can build your entire project and even run your app from command line. This will serve many different use cases – but one of the major ones is automated build and unit testing.
We’re going to start pre-releasing updates before they’re pushed automatically to the community-at-large. We’re going to make this something that’s more automated once the new Titanium Developer comes out – much like you can do with Chrome today. We’ll use a streams concept – something we already have in place in our infrastructure – to allow you to switch to more stable or less stable release streams automatically. For now, however, we’re going to manually push the SDK for download as a candidate release. Once we’ve completed our full round of regression and gotten sufficient feedback from the community, we’ll then push to everyone through the normal release channel. Our hope is that one of the ways you can help us help you is that you’ll download and test the candidate build(s) on your apps before we push them as final.
Documentation and Training. We’ve been investing heavily in training and documentation and you’ll see more content and announcements around that soon. Additionally, we’re in the process of producing a ton more written documentation, tutorials and more complete documentation sets and you will see a lot more of this over the next 4-6 weeks. In addition, as you’ve seen, we’re blogging several times a week more complete examples and tutorials here. Training and Documentation are things you’ve asked us to provide you more of – and we’re fulfilling on that promise as quickly as possible. Also, we have an upcoming San Jose Titanium training on June 26-27th.
Of course, there’s a lot more things we’ve got on the drawing board I’ll share over the next couple of weeks and months.
OK, back to 1.4.
Now that you have some context, let me tell you our plan for 1.4.
We’re going to release the 1.4 release candidate on Monday, June 21st. We’ll make the announcement here – most likely late in the afternoon West Coast time (PST) with instructions on how to download and how to report any issues you might find. We’ll also tell you what’s fixed and what we’re trying to finalize. I can tell you now that we’re wrestling with a few iOS 4.0 issues and we want to test on the new 4.0 device before we ship. Depending on how things play out, our goal would be to get you the release, get your feedback and turn around any blocking issues before June 28th for the officially targeted release. However, that date will largely depend on what we hear from you.