SDK/Meetings/Release/Agenda/20110118

Add your proposed item with name in parenthesis.

MeeGo SDK 1.2 Linux

• 1.2 Toolchain promote to Tools:SDK:Host
• Qt Creator promote to Tools:SDK:Host
• Qt Creator update to 2.1 release
• Qt Simulator status

MeeGo SDK 1.2 Windows

• Toolchain
• Qt simulator
• [Viorel Mirea] Sanity testing on Windows
• [Viorel Mirea] Test cases categorization (ex: Installation exists in basic but not in sanity)
• [Viorel Mirea] Testing daily/weekly builds (how to find out if new builds must be tested on Windows and where to find them)

Madde related proposals

• Proposal 1: The components create madde configuration file and add into madde folder (/usr/lib/madde/xxx) during installation. Taking ia32 toolchain as example.
  • The IA32 toolchain package will create a meego-core-ia32-toolchain-1.2.conf and install it to /usr/lib/madde/xx/cache/madde.conf.d/. The contents in the conf file has only the section to describe the toolchain, like:

toolchain meego-1.2-sdk-ia32-toolchain
       linux-i686 meego-1.2-sdk-ia32-toolchain-linux_i686.tar.gz
       linux-x86_64 meego-1.2-sdk-ia32-toolchain-linux_x86_64.tar.gz
       w32-i686 meego-1.2-sdk-ia32-toolchain-w32_i686.tar.gz
end

Same rule can be applied on qt-tools,

• Proposal 2: Namespace of components in madde configuration files.
  • Use only one conf file to describe the triple set of target/sysroot/runtime, which are against a same meego version.
  • Both Linux and Windows use same target name for a release with same sysroot/runtime.There is no "meego-handset-ia32-w32-x.x" but only "meego-handset-ia32-x.x" for both windows and linux and Mac in future. To achieve that goal, we should always unify our namespace and always use "w32-i686", "linux-i686", "linux-x86_64" to identify different options.
  • For any tarball file definition, they should follow rule like "name-<runtime_arch>-<version>-<host_arch>.tar.gz.
    • Known problem is "qemu-meego.tar.gz".