We don't know any more than you. It will be done when it is done.
I think the JQM team learned since the 1.0 release the dangers of releasing on a timeline. Each new release has been both delayed vs. the projected timeline, but of better quality than the previous release. I hope they do not change this policy, and rush out releases because of pressure from developers.
And as an open-source project with multiple stakeholders, there is not (and should not be) any drop-dead date for releases.
(Just speculation) I think with 1.0 there might have been some pressure from one or more major partners to release on a timeline, and now they have learned their lesson. In fact, Adobe shipped a version of DreamWeaver with either an alpha or beta 1.0 release (I don't recall) and it caused no end to pain amongst developers who treated it as if it were a production release because it came in a box.
I hope the JQM team continues to stand their ground, and not be pressured to rush something out because somebody wants to put it in a box on a schedule. If somebody puts an alpha or beta in a box, at least it's only egg on their face. (Though it's hard to explain to developers that what they got in the box wasn't ready for prime time, and it's no fault of the developers of the unfinished product, when they come here for support.)
Leave a comment on watusiware's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic