(categorise) |
|||
| (10 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
This page is to collect and track status for major decisions regarding the MeeGo SDK. Please add topics under the "Topics to review" heading.<br /> | This page is to collect and track status for major decisions regarding the MeeGo SDK. Please add topics under the "Topics to review" heading.<br /> | ||
Meeting times: Thursdays at 05:30 UTC <br/> | Meeting times: Thursdays at 05:30 UTC <br/> | ||
| - | + | ||
| + | '''Minutes''': [http://piratepad.net/qqICWdiYLl http://piratepad.net/qqICWdiYLl] <br/> | ||
== Topics to Review == | == Topics to Review == | ||
| - | + | * Release Process: How to create snapshots of intermediate builds that can be used by QA, intermediate releases, and reproducing environments by engineering. | |
| - | + | * Windows builds: server - http://bugs.meego.com/show_bug.cgi?id=11762, process | |
| - | + | * How to identify the installed MeeGo SDK version. registry key, file, gconf? | |
| - | + | * QA Tools to be taken in as part of MeeGo SDK. MeeGo QA Tools team can help delivering these. | |
| + | ** Test Frameworks (check, MIN, TDriver) | ||
| + | ** Test Execution/ planning tools (Testplanner, Testrunner) | ||
| + | *** http://wiki.meego.com/Quality/Test_management_overview | ||
| + | *** As Qt Creator plug-in (https://bugs.meego.com/show_bug.cgi?id=12971) | ||
| + | ** Automation enablers (EAT) | ||
== Topics Reviewed == | == Topics Reviewed == | ||
| + | === Qt Creator 2.1 rc1 promotion / QA plans for MWC === | ||
| + | '''Date reviewed:''' Thursday Jan 20 05:30 UTC <br /> | ||
| + | Description: Qt Creator 2.1 rc1 is in devel now. Intel would like to test it in preparation for MWC, Feb 13, 2011 | ||
| + | |||
| + | Resolution: | ||
| + | * Branch Qt Creator 2.1. Fix blocker bugs on branch. Promote snapshot/fixed version | ||
| + | * Bugs may be due to our integration. ( http://bugs.meego.com/show_bug.cgi?id=11786 ) | ||
| + | |||
| + | === Content of the default sysroot === | ||
| + | '''Date reviewed:''' Thursday Jan 20 05:30 UTC <br /> | ||
| + | '''Description:''' The SDK uses a sysroot for the MeeGo libraries that can be built with on the host system. We need to clarify what is in this default set. | ||
| + | |||
| + | Resolution: | ||
| + | * Use current sysroot contents. Includes libraries for compliance with some extras | ||
| + | * ~400MB today. May be able to be [http://meego.gitorious.org/meego-developer-tools/madde/blobs/master/ext/slimtgz.sh | slimmed down] (fremantle sysroot is only 200MB) | ||
| + | * AP: Fathi -- Create 2 sysroots: small and full (all devel). See how big the "slim" versions are. | ||
| + | * AP: Fathi -- resolve ks content / organization | ||
| + | * Future: Veli is investigating how to map QEMU image and use libraries directly. | ||
| + | |||
| + | === 3rd Party Library use === | ||
| + | '''Date reviewed:''' Thursday Jan 13 05:30 UTC <br /> | ||
| + | '''Description:''' Developers need a way to use additional, custom libraries that are not part of the default sysroot. One way to do this is to recreate the sysroot, but this is timeconsuming. Another way is to allow developers to specify the location of 3rd party libraries and include them in their project in addition to the sysroot. | ||
| + | |||
| + | Resolution: | ||
| + | * Will use package injection/removal | ||
| + | * take files from RPM or DEB and add to sysroot | ||
| + | * MADDE command 'mad xdpkg' can do this for debian-based sysroots; Will add rpm feature. Works in Windows too. | ||
| + | * Qt Creator 2.1 enables adding a project target to the sysroot itself, enhancing the sysroot with libraries/applications. | ||
| + | * AP: Maurice to investigate changes needed for Qt Creator. | ||
| + | * AP: Tomi to add RPM feature | ||
| + | * AP: Jackie to play with existing feature | ||
| + | * Future: Veli is investigating how to map QEMU image and use libraries directly. If done, users could update the libraries inside QEMU. | ||
| + | |||
| + | === MeeGo SDK Installer for Linux === | ||
| + | '''Date to review:''' Thursday Jan 13 05:30 UTC <br /> | ||
| + | '''Description:''' | ||
| + | The Linux SDK needs to be easy to install. An installer could help with: | ||
| + | * Welcome / Intro | ||
| + | * authorization check and destination (/opt or ~) | ||
| + | * Disk space | ||
| + | * Uninstall previous | ||
| + | * Repo selection (with default) | ||
| + | * Progress indication during install | ||
| + | * Target / Runtime selection | ||
| + | * Start Qt Creator | ||
| + | |||
| + | Resolution: | ||
| + | * Installer will install distribution-specific packages | ||
| + | * Bangalore team working on an interface: Installer detects system. Looks online for map to repo. Pulls from right repo. Uses right tools (apt/yum/zypper) | ||
| + | * Power user can still install manually | ||
| + | * Requires build repository into OBS for every distribution release (fedora14, ubuntu 10.10, etc.) | ||
| + | * Dependencies of host distribution can be used. | ||
| + | * IFW may be extended to use Bangalore package-installing backend | ||
| + | * Timeframe: Further discussion @F2F | ||
| + | * Owner: Bangalore backend. Maurice IFW. | ||
| + | * AP: Kamal to send design and other info to Maurice / Intel (Done!) | ||
| + | * Nokia is working on a "super installer" which will allow extension for 3rd party libraries such as Intel tools. | ||
| + | |||
| + | [[Category:SDK]] | ||
This page is to collect and track status for major decisions regarding the MeeGo SDK. Please add topics under the "Topics to review" heading.
Meeting times: Thursdays at 05:30 UTC
Minutes: http://piratepad.net/qqICWdiYLl
Contents |
Date reviewed: Thursday Jan 20 05:30 UTC
Description: Qt Creator 2.1 rc1 is in devel now. Intel would like to test it in preparation for MWC, Feb 13, 2011
Resolution:
Date reviewed: Thursday Jan 20 05:30 UTC
Description: The SDK uses a sysroot for the MeeGo libraries that can be built with on the host system. We need to clarify what is in this default set.
Resolution:
Date reviewed: Thursday Jan 13 05:30 UTC
Description: Developers need a way to use additional, custom libraries that are not part of the default sysroot. One way to do this is to recreate the sysroot, but this is timeconsuming. Another way is to allow developers to specify the location of 3rd party libraries and include them in their project in addition to the sysroot.
Resolution:
Date to review: Thursday Jan 13 05:30 UTC
Description:
The Linux SDK needs to be easy to install. An installer could help with:
Resolution: