As a user in the field who is bringing a development team from web development across to embedded development using QML and Qt/Embedded I second Bill's call for qt-creator's git to be put under some form of automatic build testing. I need this stable so that my team will have confidence to move ahead on our project.
brett On Thu, Mar 25, 2010 at 10:46 AM, Bill King <[email protected]> wrote: > Bringing this over here as was requested ;) > > > I was just criticized for criticizing the quality of creator ("on the > basis of one bug report"). > > I thought we were an open company, part of that is being open to > criticism when things are not working. > > Creator mainline is not working. I have reports both from internal and > external users on a regular basis of either creator not building, or > creator crashing upon startup. I have pushed the externals to submit > bugreports, but, again, my experience here has been less than glowing. > Being close to the front lines of the project, sometimes this can be > missed. > > To fix these issues, can we implement some sort of staging/CI system > like we have for Qt? > > For qml usage, bleeding edge is the only choice currently, and the > perceived quality of creator from the bleeding edgers is that > creator's... not usable at all. That is not the Qt way, and not a > perception we should be having. Creator is an excellent product, and one > I use daily, and I'd like to go back to bleeding edge, as that's where > all the cool new features are :) > > -- > Bill King, Software Engineer > Qt Development Frameworks, Nokia Pty Ltd > Brisbane Office > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-creator > -- Brett Morgan http://www.google.com/profiles/brett.morgan
_______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
