Symbian developer community

 
Home > Wiki > 2010-01-13 RC meeting
wiki

RC/2010-01-13 RC meeting

From Symbian Developer Community

Jump to: navigation, search

Back to main Release Council wiki page

Contents

Agenda

This f2f RC is to be held in Tokyo, kindly hosted by Fujitsu, and consists of a two day session. The first day is dedicated to workshops on specific topics, while the second day is for the RC meeting itself.

DAY 1 - Wednesday, 13th January: Workshops

Material, minutes and actions can be found here RC/RC_Workshops_2010_01_13

Attendance

  • Symbian : Mark Skebels, Jim Clarke, Victor Palau
  • Digia: Petri Poikolainen
  • Fujitsu: Yoshiiku Hanai, Chandra Narayanasamy
  • Nokia: Rauno Uusitalo
  • NTT DoCoMo: Manabu Matsuura
  • Sony Ericsson Mobile Communications: Anders Josefsson
  • Texas Instruments: Laurent Le Gal
  • Teleca : Ilkka Korhonen


Not able to attend:

  • Elektrobit: Kim Aitto-oja
  • QuIC
  • ST Ericsson
  • Samsung No RC representative

0930: Doors open/Coffee

1000 - 1115: Welcome and Review of October workshop actions and progress

Fujitsu will provide an initial welcome and briefing on logistics.


Vision & Strategy

Facilitator: Mark

Each actionee to present progress and way forward:

  • RCW1291009_1 Innovation: Create a nimble environment that permits innovation
    • Petri Poikolainen
  • RCW1291009_2 Cost & Speed: Fast TTM
    • Philippe Gaudillat/Pierre-Henri Maitre -> Mark S to present material provided by STE
  • RCW1291009_3 Cost & Speed: Predictability: High quality and on schedule
    • Laurent Le Gal
  • RCW1291009_4 Collaboration: Contributions
    • Jussi Asikainen & Riku Mettala -> Rauno U to present
  • RCW1291009_5 Visibility: Of success of transparency -> continuous improvement of transparency
    • Chandra Narayanasamy


Running Symbian Releases

Facilitator: Victor

Actions:

  • RCW2291009_1 Put together a kudos program to be reviewed by Petri (Digia)
    • Victor Palau
  • RCW2291009_2 Nokia to validate with NGA package owner that this is possible to support a test task force with the community
    • Riku
  • RCW2291009_3 TI to set and lead a test task force for NGA
    • Laurent


1115 Break

1130 - 1230 Workshop 1: FC conditions revisit

Facilitator: Chandra Narayanasamy (Fujitsu)

The intent of this workshop is to revisit the criteria we previously agreed for S^3 FC and determine what these should now be.

Also, we need to discuss the FC criteria for S^4.


1230-1330: Lunch

1330 - 1630 Workshop 2: What do we need to create a product?

Facilitator: Anders Josefsson (SEMC)

The intent is to review what is in place now to support product creation using the Symbian platform and to do a gap analysis to determine what is missing and how these gaps can be filled. Things to consider include processes, tools, metrics, etc.

The workshop will largely consist of brainstorming, discussing and prioritising what is currently being done and what needs to be done that we don't yet do (or do well enough).

DAY 2 - Thursday, 14th January: RC Meeting

Attendance

  • Symbian : Mark Skebels (Chair), Jim Clarke, Victor Palau
  • Digia: Petri Poikolainen
  • Elektrobit: Kim Aitto-oja
  • Fujitsu: Yoshiiku Hanai, Chandra Narayanasamy
  • Nokia: Riku Mettala, Rauno Uusitalo
  • NTT DoCoMo: Manabu Matsuura
  • QuIC: Mike Stefanick (rep Rob Dunder, PJ Bostley)
  • Sony Ericsson Mobile Communications: Anders Josefsson
  • Texas Instruments: Laurent Le Gal
  • Teleca: Ilkka Korhonen (afternoon sessions)

Additional guests (observers):

  • Fujitsu: Moriyama-san, Tomaru-san, Inoue-san (Issei)
  • Accenture (rep Docomo): Nigel Henshaw
  • Symbian: Yoshi Miyake (Head of Japan, Symbian Foundation)

Not able to attend:

  • ST Ericsson - Pierre-Henri Maitre, Philippe Gaudillat
  • Samsung No RC representative

0930: Doors open/Coffee

1000: RC Meeting Commences

AGENDA

  • 1000: Welcome, vote of thanks and introductions- Mark
    • Welcome and logistics from Fujitsu
  • 1015: Open actions review - Mark
  • 1045: Overall Release Plan - Mark
  • 1115: Break
  • 1130: S^2 hardening decision
    • Conditions for Stability - Chandra Narayanasamy (action follow up)
    • S^2 hardening status & decision - Fujitsu
    • S^2 open defects - Victor
    • TPIP - Fujitsu
    • Stability milestone decision - All
  • 1215: Lunch
  • 1315: Introduction to Japanese mobile - Ryo Inowa
  • 1330: S^3 FC status - Victor
    • Quality metrics
    • Triage plan for S^3 defects
    • Obtaining test results
  • 1415: S^4 status and RS decision - Mark
  • 1500: Proposals pipeline MCP review - Mark
  • 1530: Break
  • 1545: Tools programme - Victor
    • Proposal for release cadence
    • Integration plan
  • 1600: Test WG status - Jim
  • 1615: UI WG status - Mark (for Urmi)
  • 1630: EPL status - Victor
  • 1645: How are we doing as a Release Council - Open discussion
  • 1715: RC calendar & Wrap-up
  • 1730: Adjourn

Actions

Both Open and closed Actions have been updated with to reflect the output of the council meeting

Material

Latest Information on Releases!

The following link will take you to the latest update on the Platform Release Plan. From there you can navigate to the individual release plans, integration plan, kits schedule, release model and even the RC minutes themselves!

http://developer.symbian.org/wiki/index.php/Platform_Release_Plan


Minutes

Review of Open Actions

See updated table via link in the Actions section above. Closed actions can also be found by following the closed actions link there.

The following actions are closed:

  • RC101209_1, _2, _3, _4, _5, _6
  • RC301009_5 Discussion held in this RC meeting. Refer to S^2 minutes and follow-up action.

Actions in progress:

  • RC240909_2 Urmi. The plan is to present a proposal at the February call.
  • RC301009_3 Sebastian Brannstrom. Daniel Rubio will provide statement on behalf of AC.

New actions appear in these minutes and have been incorporated into the actions table.

Platform Release Plan - Mark

Refer to the Release Plan in the Materials section of these minutes. This also includes the release plans for S^2, 3 and 4 discussed later in these minutes.

Mark presented the overview of the releases pointing out specific achievements and issues for further discussion in the meeting.

Specific questions and comments on each release are captured in the following sections of the minutes.


S^2 Status - Victor/Chandra N/Hanai-san

Compatibility Baseline:

  • BC checks identified a number of breaks. These are down to 13 under analysis on the grey list. Of these, 2 PkOs own 10 (ClassicUI and OSservices). We have not been able to get a response from these PkOs on the status of the breaks.
    • Action RC140110_1: Riku to raise this with Jussi P. Response required by end January.


Quality Metrics

  • Approx 190 open bugs. Note that these reflect only the bugs that have been raised in Bugzilla. The SF and wider community has no visibility of other bugs which may exist in TB9.1 but have not been raised in Bugzilla.
  • Very little analysis has been done by PkOs on these bugs and so the true crticiality, and therefore the potential impavct of these bugs, is not understood. Victor proposed that a triage of these defects needs to be done requiring a task force consisting of RC memebers (or delegates). The RC agreed to this. The following have been identified or are needed:
    • A person who can represent the PkOs from Nokia. Action RC140110_2: Riku to identify by 22 Jan. Now closed. Rauno identified Kari Lammi
    • Fujitsu nominated Chandra N to the task force
    • TI agreed to provide rep. Action RC140110_3: Laurent will sit on this. This is now closed.
    • EB: Kim agreed to join task force
    • DCM: Tom Whitson nominated by Matsuura-san
    • Digia: Juha Malkki
    • Any remaining members to be identified by 22 Jan. As of Jan 29th no further volunteers have been identified.
    • Victor to send bug data by 22 Jan - DONE. See email: http://developer.symbian.org/pipermail/release_council/2010-January/000227.html


What does Stable mean? - Chandra N (presentation in material section)

  • Fujitsu state that with the current situation on quality defined by the metrics the SF has provided for PDK2.0.2, development of products based on this will have quality issues which need to be addressed.
  • Fujitsu's view on judging the end of the Hardening phase is:
    • for open defects for which the importance is Normal or higher, these should be closed under the following conditions:
      • Critical/Major defects must be resolved in S^2
      • Normal defects should be classified as Fixed or WontFix (with information on how these are addressed, e.g. by workarounds or plans to fix in future releases)

After discussion with the RC the proposal was that a view on quality needs to be gained before the Stable milestone can be reviewed and declared. The proposal is that a minimum test suite should be defined which can then needs to be executed to provided a quality assessment.

Based on the discussion the RC had in the FC criteria workshop on the 13th where we agreed that a test suite needs to be provided for FC, we also agreed that we should take a similar approach for the Stable milestone for S^2. This works as follows:

  • In the special case of S^2 where no FC test suite was defined, the test suite used for the Stable milestone is expected to be a subset of the S^3 test suite defined for FC (since not all S^3 test cases may apply to S^2).
  • For S^n [n>2] releases in general, the requirement for the Stable milestone is that the test suite defined at FC should be run as a minimum. Obviously if there are more test cases available to be run then so much the better.

The following was the vote on the need for a quality assessment via a test suite for the Stable milestone:

  • Agreed by Docomo, Fujitsu, TI, QuIC, Elektrobit, Digia, SEMC.
  • Nokia agreed that clarification of the end of hardening is needed, however, the following comments were made by Riku:
    • concerned about having to somehow harmonise the test cases at a detailed level
    • it would be useful to clarify the meaning of the (stable) milestone and its implications
  • The vote (...that a view on quality needs to be gained before the Stable milestone can be reviewed and declared. The proposal is that a minimum test suite should be defined which can then needs to be executed to provided a quality assessment) was carried.
  • Action RC140110_4: Chandra N to update the definition and implications of the Stable milestone and publish for review by the RC.
  • Action RC140110_5: Define a subset of the S^3 FC test suite for S^2. Laurent & Fred Maurel have provided a proposal to the Test WG for use cases from TI as a starting point. This action is being tracked by the Test WG.


Another point to consider is that the Stable milestone is also a message to developers that we move from beta SDK to first official SDK. There is also a message to the community that focus shifts from bug fixing to device creation (where only critical bugs will be contributed).


S^2 Productisation Status - Hanai-san

In addition to the defects discussion above, Fujitsu also pointed put that there are 7 TPIP required for global device creation on S^2.

Symbian responded that all critical TPIP items identified as gating S^2 FC have been delivered and requested that Fujitsu provide the list of missing TPIP items.

Jim pointed out that there seems to be a disconnect between TPIP identified for FC and the additional 7 for global products. He requested that Symbian provides an update on how we manage the TPIP list and process so that we ensure any gaps are covered in future.

  • Action RC140110_6: Victor to review the TPIP process/management to clarify the agreement on TPIP for S^2. Also propose any changes needed to ensure the process for TPIP agreements is clear.
  • Action RC140110_7: Mark to ask Chris Davidson to provide a TPIP update at the next RC meeting.

Note also that the FC workshop also defined the need for a minimal TPIP set to be defined (action to be followed up from workshop).

Finally, Symbian requested that Fujitsu/Docomo provide a contribution plan for submitting defect fixes to the SF.

  • Action RC140110_8: Matsuura-san to provide the plan for this (Accenture working on plan).

S^3 Status - Victor & Mark

Key Features: Key points and issues:

  • Deliveries tracking to plan for FC. 3PC, SHAI.1, WDP, Mulipage Homescreen, HD video, One-click connectivity, Song recognisiton & Music Store, Remote contact lookup all submitted.
  • SymbianJ: No change from December status. Legal process underway to agree R&D license. Expected to complete March 2010 which means this will be post-FC delivery as previously communicated. This is not seen as an issue due to the fairly isolated nature of this feature (i,e, minimal dependencies on other pkgs).
  • NFC: RC agreed that this will now be moved to S^4 and tracked there. Riku commented that this could also be delivered on S^3 later.
  • REE: Textshell booting on Zoom2.
  • NGA (AMBER): We are on track to have a wokring NGA solution by FC. Production Render Stage is next contribution expected end Jan so still within FC. We expect amber status to change to green as UI bringup issues under control.
  • SHAI: as discussed in the last RC, marked this item as delivered in the KF list as there is no new functionality above and beyond the existing APIs for S^3.
  • SMP: Kernel prototype in PDK3.0.a. SMP Safe software validation for OS layer on track (70%). HW validation not required for FC but needs to complete during hardening phase. Full SMP is targetted for S^5.
    • Fujitsu (Tomaru-san) asked if SF will provide builds for both multi and single core configurations in S^4. Jim responded that this is likely and asked why this was requested. Tomaru-san responded that this would allow more feedback from the community.
    • Riku added that the Kernel is configurable rather than there being two different Kernels (one single-, one multi-core).
    • SMP Safe for apps (MW) is targetted for S^4, however Riku identified potential risk on this due to priority on DirectUI, Orbit, Qt for S^4.
    • Request was made that an analysis is done of what core apps should be SMP Safe for S^4.
      • Action RC140110_9: Mark to request FRC/AC to look at what core or critical apps are needed as a basic config for S^4.
  • CalDav (AMBER): Provided by Sun. The amber status was due to dependence on a UI enabled PDK. This has now been addressed so this item should go green.
  • One-click connectivity: Framework is in place but not all apps. Should be tracking to FC.
  • Qt4.6.1: Delivery expected Feb but is not a compulsory feature for S^3.

Overall, S^3 is green from a KF contribution point of view and contributions are on track for FC. As noted in the FC criteria workshop, a tes suite also needs to be defined and other aspects of FC cfriteria need to be assessed.

Laurent (TI) raised the question of moving the FC to March to wait until SymbianJ is submitted.

  • Mark responded that while this could be done we are trying to keep to a timeboxed release schedule as far as possible. Unless there was a compelling reason to move the FC we should keep to the schedule to signal that device manufacturers and app developers that the release has entered the hardening phase. Note that SymbianJ has no hard dependencies on other code so can be treated in isolation.
  • Action RC140110_10: Mark to create a blog post to clarify the timelines for S^3 and ^4


Code churn

  • Churn metrics useful in validating expectations on code submissions as we approach FC, i.e. need to ensure that level of churn is in line with phase of release. We can use the trend as a measure of stability.


Quality Metrics

  • As reported for S^2, the trend on open defects shows that there is little defect management in the community. The defect median age also shows this. (Victor pointed out that the as the median age is based on averaging, the
  • The triage exercise being put together by Victor will help in actioning defects.


FC Criteria:

Refer to the workshop minutes for the outcome of this discussion.


Zoom2 Status - Laurent (TI)

  • S^3 bring up on Zoom2 is complete on PDK3.0.d.
  • Textshell image verified on Zoom2 with PDK3.0.c and .d
  • Issue: Zoom2 crashes on 3.0.e bootup. Reasons are not yet understood.
    • Action RC140110_11: Laurent to arrange call with SF to isolate cause

S^4 Status - Mark

At the last RC call in December, the RC approved "Option 2" for declaring RS on S^4. That is: Approve RS with the full list of KFs but can only pass RS if there is a plan for a plan for the red features, i.e. a plan for when delivery dates will be available.

The situation with S^4 KFs is shown on pp21-23 of the release plan material. Planning information is available for all KFs except DirectUI for which there is no plan to provide. This was discussed with the RC.

  • DUI is not its "own technology" as such, but rather provides the paradigm for consistent UI apps development in the Qt/Orbit environment. This means that DUI in itself does not involve the contribution of another technology (over and above Qt and Orbit).
    • Action RC140110_12: Riku/Rauno to drive getting further information on DUI way forward.

Other considerations raised for S^4:

  • Package backlogs are growing. At the time of the RC mtg, there were approx 90 backlogs. This has now grown to 133
    • Action: RC140110_13: Urmi to provide a plan for a plan for pkg backlogs.
  • Resource plan for S^4 needs to be approved. Issue: Resources limited to allow S^3 and S^4 build, test and integration in parallel. The proposal put forward by the SF is to prioritise between S^3 and ^4 and review with the RC. This may mean less frequent PDKs and SDKs for each release. This was felt to be manageable and no objections were raised by the RC.
  • REE to be defined.
    • Draft available. Expect AC to agree in January.
  • BC policy.
    • Policy for Qt is needed since this is a separate OSS project. Urmi is following up with AC.

RS recommendation:

  • Pass RS based on:
    • Resourcing proposal acceptable.
    • Delaying RS will not impact getting DUI information (that is, will not force this to become available earlier). Also, as stated above, DUI is not in itself a new technology.
    • Enough information and plans are available on the remaining KFs to be confident that integration plans can be created.

The outcome of the vote on approving RS:

  • SEMC: Yes. Important to get the release going (and provide visibility)
  • Digia: Yes
  • Elektrobit: Yes
  • Nokia: Yes. For stability but with right bias on S^3
  • Teleca: Yes
  • TI: Yes. With action on feature submission and test plan (as per workshop discussions on FC criteria).
  • QuIC: Yes
  • Fujitsu: Yes
  • Docomo: Yes

Vote carried unanimously by attendees. RS approved.

A request was made to define the content of the first S^4 contribution and when this would be. The question was also raised on whether it would be better to start PDK builds as soon as RS is passed. There was no definite decision on this.

  • Action RC140110_14: Urmi to communicate contents of first contribution

Tools Programme - Victor

Victor presented the overview of this programme. The proposal is that there will be Tools releases every 6 months on a sequential basis.

  • The RC agreed that we would review the programme status at every f2f RC meeting.


MCPs - Mark

Mark summarised the input from the RC on the MCP content and review proposal. This material was issued to the RC members in December and copied to Ian Hutton (FRC chair) and other chairs. The material can be found in these minutes.

The RC decision was that the following MCPs need to be reviewed to comply with the guidelines. The agreed reviewers for the MCPs are:

  • Orbit: Chandra Narayanasamy
  • Qt: Kim Aitto-Oja??
  • New Printing Framework: Riku Mettala
  • Social Mobile Framework: Victor Palau
  • Browser: Petri Poikolainen
  • SHAI: The RC agreed to defer until further input is available from the SHAI WG. This MCP seems to be in a state of flux and the SHAI rollout is not clear.

"Review" here means that the reviewer will be responsible for discussing the content requirements for the RC in line with the guidelines set out in the MCP presentation with the MCP author/owner and ensuring this information is made available.

  • The target date for completion of reviews (including discussion with authors) is 15th Feb 2010.

Review status will be tracked at each RC meeting.

Two additional MCPs were submitted by the date of the RC which will require reviewers to be assigned:

  • SHAI SW Development Kit - it is assumed that this will be addressed once the SHAI strategy is better understood
  • Podcasting - Mark S will follow up on this

Since the RC mtg, the Common Web Runtime MCP has also been submitted. However, this is awaiting WG feedback before a review can be done.

  • Petri P to review

WG updates

  • Test WG (Jim): Refer to the material posted with these minutes.
  • In summary ther are three work packages underway:
    • Test Strategy - 1st draft approved by TWG. RC members need to ensure this aligns with own organisations' views
    • Pkg Test Assets - Prioritisation of pkgs agreed. Pkg owners being consulted so we understand what test assets are available. Aim is to execute and automate tests.
    • Test Roadmap - Create the roadmap for test activities and SF test hub services in 2010. Resourcing options need to be explored.
  • UI WG (Mark for Urmi): Refer to the material posted with these minutes.
    • The LGPLv2 implications need to be understood. Need to focus on the issues affecting licencing of Qt.
    • Action RC140110_15: Urmi to invite Antti Enqvist (Legal) to the next RC conference call to provide an update.


Next Meeting

The proposal is to hold the next RC conference call on Thursday 18th February.

  • The RC agreed, however, Mark will confirm the date and logistics as this includes attendance of QuIC reps PJ Bostley and/or R Dunder.
Retrieved from "http://developer.symbian.org/wiki/index.php/RC/2010-01-13_RC_meeting"

Comments

Sign in to comment…