Comment 1 for bug 1211253

a) The Ubuntu SDK is a fairly complex project. It has 4 major subdomains:
1. The APIs what are delivered from the https://launchpad.net/ubuntu-ui-toolkit project
2. The stock QtCreator what comes from Qt and lands in our SDK with minimal changes and lives in https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtcreator_2.7
3. The Ubuntu plugin to the QtCreator what makes QtC look and behave like Ubuntu SDK. This project lives here https://launchpad.net/ubuntu-qtcreator-plugins
4. The device connectivity scripts and application templates as static content live in https://launchpad.net/qtcreator-plugin-ubuntu

All of these projects are under control of the SDK team (https://launchpad.net/~ubuntu-sdk-team)

We are monitoring all bug reports to all projects, and most of the users file the API specific bugs against the ubuntu-ui-toolkit project and the tools specific bugs agains the ubuntu-qtcreator-plugins or qtcreator-plugin-ubuntu

The namings are odd, but these projects were not set up in one day by one person :) So some diversity is the result of organic evolution of the SDK.

b) The ubuntu-sdk link to the qtcreator is created and the fix is landed on the trunk (https://code.launchpad.net/~ubuntu-sdk-team/qtcreator-plugin-ubuntu/trunk) Jenkins and the core-devs will do their jobs and the ubuntu-sdk CLI command will be available in the 0.1-0ubuntu4 in Saucy archive or in the SDK PPA (https://launchpad.net/~ubuntu-sdk-team/+archive/ppa/) in version 0.1bzr21saucy0