Meego Wiki
Views

SDK/Meetings/20110209 Weekly

From MeeGo wiki
< SDK | Meetings(Difference between revisions)
Jump to: navigation, search
(Added minutes)
 
(3 intermediate revisions not shown)
Line 16: Line 16:
== Attendees ==
== Attendees ==
-
*  
+
* Veli Kaksonen, Bob Spencer, Ville Lavonius, Maurice Kalinowski, Jarmo Kant, Juha Peisanen, John Chen, Jackie Wu, Taru Laine,Kerry Jiang
 +
 
== Agenda ==
== Agenda ==
Line 23: Line 24:
* SDK F2F Meeting in Helsinki on week 7 (16.-18. of February)
* SDK F2F Meeting in Helsinki on week 7 (16.-18. of February)
-
** Intel attendees: Zhiyuan, Max, Jackie, Bob and Arcadie
+
** Intel attendees: Jackie, Bob and Arcadie
-
* Telco 28th of Jan
+
** http://wiki.meego.com/SDK/Meetings/20100216-18_F2F_Helsinki
* Next F2F in Portland
* Next F2F in Portland
* OSTS is March 10-11  (Portland. Intel internal, but invitations for partners is common)
* OSTS is March 10-11  (Portland. Intel internal, but invitations for partners is common)
Line 57: Line 58:
==== Features (Ville) ====
==== Features (Ville) ====
-
* OLD: We are working with those this week...
+
* Proposal: rework the entire feature mess to be better aligned with reality, more easily browsable and maintainable.
 +
** Create a two-level hierarchy of items, and use the description field better to place an individual feature within the hierarchy.
 +
** Top level items:
 +
*** SDK m(aintenance)
 +
*** Target m(aintenance)
 +
*** Project m(aintenance)
 +
*** Create
 +
*** Build
 +
*** Test
 +
*** Publish
 +
*** Host support
 +
** Every requirement is to be placed within that hierarchy, and renamed to reflect its position, and linked to the appropriate components (the component list is outdated, and the one used in the bugs shall be taken into use, and expanded as needed).
 +
 
 +
** Immediate steps (right here, right now):
 +
*** Agree that the set above is a decent enough working assumption.
 +
*** Open issue: documentation - shall a separate top level item be created for it, or will all documentation-related items be folded into the appropriate items (in which case something along the lines of "SDK productization" is probably required: release notes, installation instructions and generic documentation does not have a good home in the above).
 +
 
 +
** Next steps (by the workshop next week):
 +
*** Rework the entire current set into the new form, renaming features as needed.
 +
*** Add features as potential content.
 +
*** Review the set in Helsinki (Thursday or Friday), especially tagging things out of 1.2 as realistic.
 +
 
 +
** Steps after that
 +
*** Roll in the comments from the workshop.
 +
*** Cross-link to internal requirements DB.
 +
*** Request comments from the other programs (this set is extremely handset-centric).  
Line 90: Line 116:
* MeeGo 1.2
* MeeGo 1.2
** Toolchains IA32/ARM promoted to Tools:SDK:Host on week 4
** Toolchains IA32/ARM promoted to Tools:SDK:Host on week 4
 +
*** Fedora 14 support is ongoing
** kickstart file should have only minimal set of packages listed (BMC#11607) (Fathi)
** kickstart file should have only minimal set of packages listed (BMC#11607) (Fathi)
** Qt 4.7.1/Qt Creator 2.1/Qt tools promoted to Tools:SDK:Host on week 4 (Fathi)
** Qt 4.7.1/Qt Creator 2.1/Qt tools promoted to Tools:SDK:Host on week 4 (Fathi)
Line 97: Line 124:
* Qt simulator
* Qt simulator
** Qt simulator for Linux is in progress. (Jackie Wu) (DONE)
** Qt simulator for Linux is in progress. (Jackie Wu) (DONE)
 +
*** Need Fathi's final review.
*** simulator-qt standalone? or qmake extra package only? (Jackie Wu/Fathi) simulator-qt standalone works.  
*** simulator-qt standalone? or qmake extra package only? (Jackie Wu/Fathi) simulator-qt standalone works.  
** Windows:  Max has trouble with Qt Simulator on Windows.  It is 4GB.  It is still developer build, for Tim's formal scripts doesn't work. Tim should help to fix the scripts. Maurice will ping Tim when he is back to office.
** Windows:  Max has trouble with Qt Simulator on Windows.  It is 4GB.  It is still developer build, for Tim's formal scripts doesn't work. Tim should help to fix the scripts. Maurice will ping Tim when he is back to office.
** MeeGo devices are missing, aava skin for IA32. It's in progress. (Jackie)  (Jun Tian)
** MeeGo devices are missing, aava skin for IA32. It's in progress. (Jackie)  (Jun Tian)
-
*** Create gitorious project? (Jackie)
+
*** Create gitorious project? (Jackie) (DONE)
* QEMU
* QEMU
Line 114: Line 142:
==== Mac OS X port ====
==== Mac OS X port ====
-
* David Lawlor starts at Portland, OR (Intel) on Jan 31st.
+
* David Lawlor starts at Portland, OR (Intel) on Jan 31st.
* Server has been discussed at intel
* Server has been discussed at intel
* ARM toolchain available
* ARM toolchain available
Line 125: Line 153:
* There is a silicon bug in Cortex-A8 (also in N900) which prevents the use of Thumb2 instructions ( http://cateee.net/lkddb/web-lkddb/ARM_ERRATA_430973.html). Therefore only NEON optimized toolchain can be used in the N900 reference.  
* There is a silicon bug in Cortex-A8 (also in N900) which prevents the use of Thumb2 instructions ( http://cateee.net/lkddb/web-lkddb/ARM_ERRATA_430973.html). Therefore only NEON optimized toolchain can be used in the N900 reference.  
-
* 20110119: RPM changes are done by Carsten Munk to detect armv7nh and armv7nhl architetcures. Patch will be submitted to upstream.
 
-
* 20110119: Open question still whether to allow Thumb2 instruction set by default or not. May lead to new subarchitectrue "armv7tnhl" to indicate Thumb2. Thumb2 provides more compact code than the normal ARM instruction set. Discussion ongoing.
 
-
* 20110126: Thumb2 is supported. Two new architectures more: armv7thl (Thumb2 with VFPv3-D16) and armv7tnhl (Thumb2 with NEON). Also RunFast is supported in glibc. Change wikipage updated accordingly.
 
-
 
-
* GCC has been updated to 4.5.1
 
-
** Planned deliveries
 
-
*** Toolchain delivery (Linux) for 1.1.80.11, 2010-12-16 -- 2010-12-22
 
-
*** Toolchain delivery (Windows) for 1.1.90.0, 2011-01-20 -- 2011-01-2
 
Line 139: Line 159:
* Taru Laine is the doc team lead.
* Taru Laine is the doc team lead.
-
* status of Windows SDK and API reference (updates for 1.1) - when can documentation be finalized? Windows SDK OK, no known update needs for API reference, but info on Qt Mobility backend needed. -> MeeGo 1.1.2 update blog post and release notes cover the Windows SDK issue. No new information on Qt Mobility received, this issue will be discussed Taru: would you please send me details about issues with Windows SDK? -Max Taru: Done, I was merely referring to the official announcement on Windows support for MeeGo 1.1.
+
* Documentation backlog for MeeGo 1.2 SDK can be found here: http://wiki.meego.com/Documentation_Backlog_for_MeeGo_1.2  
-
** Blog post on MeeGo SDK 1.1.2 release update to be issued as soon as possible. Draft from Fathi available already, but needs to be reviewed. -> content for release notes and blog post finalised on 14 January and sent to Fathi for publishing.  
+
* Weekly documentation telco meetings have been postponed for now and will be restarted in March closer to the April release date.  
-
* 20101215 AP doc team: go through open action points from review sessions for SDK 1.1 release ONGOING This will probably be covered by the blog post on MeeGo SDK 1.1.2, apart from Qt Mobility issues.
+
* Issues to discuss at next week's face-to-face meetings in Helsinki:
-
* MeeGo SDK Documentation status meetings have started again. This week's agenda can be found here:
+
** Current documentation process: described in http://wiki.meego.com/SDK/Documentation
-
http://wiki.meego.com/SDK/Documentation/MeetingMinutes/20110120
+
** New feature hierarchy and its impacts on documentation
-
The plan is to discuss, for instance, community participation in the documentation (especially best practices and sample applications) and the responsibilities assigned to team members.
+
** Community contribution for MeeGo 1.2 documentation, especially for ''Instructions and best practices'' and ''Sample applications''.
-
 
+
** Finding owners for the following tasks: Device provisioning instructions for netbook, Netbook UI guidelines, Debugging instructions for MeeGo 1.2 SDK (currently part of Other documentations feature), Creating a Hello world application (currently part of Other documentations feature), Instructions for building MeeGo image/QEMU image (currently part of Other documentations feature)
 +
** Publishing channels for MeeGo 1.2 SDK documentation
 +
** Timetable for MeeGo 1.2 SDK developer documentation features (based on the milestones assigned for the MeeGo 1.2 SDK features)                                                                             
 +
* Question: Since API is a relatively separate topic from the rest of the developer documentation, should there be an independent slot for it in team meetings? (or is this already a part of the Architecture team as a task force?)
=== QA (Juha) ===
=== QA (Juha) ===
-
* Sync between Intel & Nokia QA about test set
+
* Sync between Intel & Nokia QA in weekly meetings
-
** Sanity test focus on daily sysroot check
+
* All QA reports at http://qa-reports.meego.com/
-
** Basic feature test focus on weekly Qemu image and SDK Host packages
+
* Feature status :
-
** Extended Feature test will be part of full pass for milestone release
+
** Released :
-
** Performance test will be part of full pass test for milestone release
+
*** total 5
-
** Reliability test will be part of full pass test for milestone release
+
*** test case exists 2
-
*All QA reports tracked at http://qa-reports.meego.com/
+
*** under work 2
-
* Bug status:  
+
** Resolved :
-
** Open 92 = Windows 10 + Linux 82
+
*** total 39
-
** Closed 89 = Windows 46 + Linux 43
+
*** testability checked 31
-
** 6 critical bugs:
+
*** test case exists 20
-
*** #8887 [Windows] ARM QEMU binary for Windows is missing
+
*** under work 1
-
*** #11271 Qemu can't launch from Qt Creator
+
** Accepted :
-
*** #11109 MeeGo 1.1 API delivered many tap gestures for a swipe gesture
+
*** total 108
-
*** #8365 Unable to Play Audio/Video Files in Emulator
+
*** testability checked 7
-
*** #10075 QEMU does not launch when installed and launched in Ubuntu 10.10
+
*** test case exists 3
-
*** #9737 [Windows] Fail to run application in Qemu
+
* Testing
-
* Testing for 1.1 update is done in rest of the distros ( Debian, Fedora12 &13, openSUSE11.2 & 11.3 and Windows), test reports can be expected latest tomorrow in qa-reports.
+
** Tested updated tools on Ubuntu 10.10 32bit and Fedora13 32bit with latest available sysroot.
-
** Created bugs :  
+
*** Results are in qa-reports.
-
*** 12236        Compiling simple example does not work in Qt Creator
+
*** No new bugs, but on Ubuntu bugs #12561, #12853 and in Fedora13 #12561 are still valid.
-
*** 12460        QtCreator cannot load library libQmlProjectManager.so to OpenSuse11.2
+
** Testing ongoing on latest available sysroot (1.1.90.1.20110201.1) in Ubuntu 10.10 64bit and Fedora14 32bit.
-
*** 12522        Qt console application building with qtcreator fails
+
-
*** 12561        All installed SDK content is not removed when uninstalling SDK
+
-
*** 12702      apt-get update is failed in Debain 5.0-32 while meego Sdk 1.1.2 install
+
* Test transition is still in progress.
* Test transition is still in progress.
-
 
* Review test cases on tl (BMC#12536)
* Review test cases on tl (BMC#12536)
* Formalize bug handling workflow
* Formalize bug handling workflow

Latest revision as of 06:23, 9 February 2011

Contents

MeeGo SDK Weekly Meeting 20110209

This document contains agenda and minutes (added after the meeting) of SDK weekly teleconference meeting on 20110209 07:30 EEST.

Conventions of this document

  • AP: = Action point agreed on this meeting
  • yyyymmdd AP: = Action point agreed on previous meeting
  • yyyymmdd AP yyymmdd: = Action point agreed on previous meeting with a deadline
  • yyyymmdd AP DONE: = Action point done
  • yyyymmdd AP CANCELLED: = Action point cancelled
  • AGREE: = Item that has been agreed by the team
  • POSTPONED: = Agenda item postponed from last meeting
  • OLD: = Info from previous meeting (delete during the meeting)

Attendees

  • Veli Kaksonen, Bob Spencer, Ville Lavonius, Maurice Kalinowski, Jarmo Kant, Juha Peisanen, John Chen, Jackie Wu, Taru Laine,Kerry Jiang


Agenda

SDK Program (Veli)

  • SDK F2F Meeting in Helsinki on week 7 (16.-18. of February)
  • Next F2F in Portland
  • OSTS is March 10-11 (Portland. Intel internal, but invitations for partners is common)
  • MeeGo Conference May 23-25 (San Fran)
  • 20101215 AP: What is the date of Open source of IFW? (Maurice)
    • Meeting with legal on Friday
  • List of attendees to this meeting:
    • The guys who should be there... :)
      • Veli Kaksonen
      • Bob Spencer
      • Ville Lavonius
      • Nishant Tandon
      • Kamal Bhatt
      • Maurice Kalinowski
      • Max A Yu
      • Fathi Boudra
      • Jackie Wu
      • John Chen
      • Haitao Feng
      • Zhiyuan Lv
      • Jun Tian
      • Cathy Shen/her replacement
      • Prepelita, Arcadie
      • Daniel Mihai
      • Kerry Jiang
      • Al Nikolov
      • Riku Voipio
    • Optional attendees


Features (Ville)

  • Proposal: rework the entire feature mess to be better aligned with reality, more easily browsable and maintainable.
    • Create a two-level hierarchy of items, and use the description field better to place an individual feature within the hierarchy.
    • Top level items:
      • SDK m(aintenance)
      • Target m(aintenance)
      • Project m(aintenance)
      • Create
      • Build
      • Test
      • Publish
      • Host support
    • Every requirement is to be placed within that hierarchy, and renamed to reflect its position, and linked to the appropriate components (the component list is outdated, and the one used in the bugs shall be taken into use, and expanded as needed).
    • Immediate steps (right here, right now):
      • Agree that the set above is a decent enough working assumption.
      • Open issue: documentation - shall a separate top level item be created for it, or will all documentation-related items be folded into the appropriate items (in which case something along the lines of "SDK productization" is probably required: release notes, installation instructions and generic documentation does not have a good home in the above).
    • Next steps (by the workshop next week):
      • Rework the entire current set into the new form, renaming features as needed.
      • Add features as potential content.
      • Review the set in Helsinki (Thursday or Friday), especially tagging things out of 1.2 as realistic.
    • Steps after that
      • Roll in the comments from the workshop.
      • Cross-link to internal requirements DB.
      • Request comments from the other programs (this set is extremely handset-centric).


Architecture (Bob) 

(Meetings held weekly, as needed)

Topics for future meetings:

Covered in past weeks (Resolutions here: http://piratepad.net/qqICWdiYLl )


Releasing (Fathi)

  • MeeGo 1.1.2 is out \o/ Hooray!
  • MeeGo 1.1.2 QA results successfull even without MADDE hotfix. Need investigations.
  • MeeGo 1.2
    • Toolchains IA32/ARM promoted to Tools:SDK:Host on week 4
      • Fedora 14 support is ongoing
    • kickstart file should have only minimal set of packages listed (BMC#11607) (Fathi)
    • Qt 4.7.1/Qt Creator 2.1/Qt tools promoted to Tools:SDK:Host on week 4 (Fathi)
  • MWC will get QEMU GL ES for IA32
  • Qt simulator
    • Qt simulator for Linux is in progress. (Jackie Wu) (DONE)
      • Need Fathi's final review.
      • simulator-qt standalone? or qmake extra package only? (Jackie Wu/Fathi) simulator-qt standalone works.
    • Windows: Max has trouble with Qt Simulator on Windows. It is 4GB. It is still developer build, for Tim's formal scripts doesn't work. Tim should help to fix the scripts. Maurice will ping Tim when he is back to office.
    • MeeGo devices are missing, aava skin for IA32. It's in progress. (Jackie) (Jun Tian)
      • Create gitorious project? (Jackie) (DONE)
  • QEMU
    • Images missing since 2 weeks because release team switched to weekly build and forget to create them in time (manual creation...)

Windows port (Max)

  • The second preview of MeeGo 1.2 SDK has been released. Qt simulator is included.
  • Winchow will be working on update toolchain.
  • Build server: handling by IT (http://bugs.meego.com/show_bug.cgi?id=11762). (Al)
  • TODO: Attica/OBS plugin to build only (skip usability for now)

Mac OS X port

  • David Lawlor starts at Portland, OR (Intel) on Jan 31st.
  • Server has been discussed at intel
  • ARM toolchain available


Toolchains (Jarmo)

  • Still some changes done to communication wiki. Hopefully can be published this week.
  • There is a silicon bug in Cortex-A8 (also in N900) which prevents the use of Thumb2 instructions ( http://cateee.net/lkddb/web-lkddb/ARM_ERRATA_430973.html). Therefore only NEON optimized toolchain can be used in the N900 reference.



Documentation (Taru)

  • Taru Laine is the doc team lead.
  • Documentation backlog for MeeGo 1.2 SDK can be found here: http://wiki.meego.com/Documentation_Backlog_for_MeeGo_1.2
  • Weekly documentation telco meetings have been postponed for now and will be restarted in March closer to the April release date.
  • Issues to discuss at next week's face-to-face meetings in Helsinki:
    • Current documentation process: described in http://wiki.meego.com/SDK/Documentation
    • New feature hierarchy and its impacts on documentation
    • Community contribution for MeeGo 1.2 documentation, especially for Instructions and best practices and Sample applications.
    • Finding owners for the following tasks: Device provisioning instructions for netbook, Netbook UI guidelines, Debugging instructions for MeeGo 1.2 SDK (currently part of Other documentations feature), Creating a Hello world application (currently part of Other documentations feature), Instructions for building MeeGo image/QEMU image (currently part of Other documentations feature)
    • Publishing channels for MeeGo 1.2 SDK documentation
    • Timetable for MeeGo 1.2 SDK developer documentation features (based on the milestones assigned for the MeeGo 1.2 SDK features)
  • Question: Since API is a relatively separate topic from the rest of the developer documentation, should there be an independent slot for it in team meetings? (or is this already a part of the Architecture team as a task force?)

QA (Juha)

  • Sync between Intel & Nokia QA in weekly meetings
  • All QA reports at http://qa-reports.meego.com/
  • Feature status :
    • Released :
      • total 5
      • test case exists 2
      • under work 2
    • Resolved :
      • total 39
      • testability checked 31
      • test case exists 20
      • under work 1
    • Accepted :
      • total 108
      • testability checked 7
      • test case exists 3
  • Testing
    • Tested updated tools on Ubuntu 10.10 32bit and Fedora13 32bit with latest available sysroot.
      • Results are in qa-reports.
      • No new bugs, but on Ubuntu bugs #12561, #12853 and in Fedora13 #12561 are still valid.
    • Testing ongoing on latest available sysroot (1.1.90.1.20110201.1) in Ubuntu 10.10 64bit and Fedora14 32bit.
  • Test transition is still in progress.
  • Review test cases on tl (BMC#12536)
  • Formalize bug handling workflow
Retrieved from "http://wiki.meego.com/SDK/Meetings/20110209_Weekly"
Personal tools