Symbian developer community

 
Home > Wiki > 2009-10-29 RC meeting
wiki

RC/2009-10-29 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 immediately after the SEE event 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 - 29th October: Workshops

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

Workshop 1 0900 - 1200: Vision & Strategy

Participants: All RC members

Facilitator: Lauren Sarno (Lauren is part of the Member Programs team in SF)

The intent of this workshop is to be visionary and strategic. Let's look ahead to see where we want to be a year or two down the road and what we need to put in place to get there. This is a great opportunity to air your views and influence the direction of Symbian releases!

The theme for the session will be: How will Symbian open source software change the way mobile phones are delivered in the future?

Our mission: How does the Release Council make this happen? What’s our part in it? By the end of the workshop, we want to have answered this question by identifying a few (3-5) specific actions that we can execute to achieve this.

Some food for thought before the workshop. To get us all thinking, here is a sample of the questions we should consider:

  • Why are we here?
  • What does your company want from the Symbian Foundation?
  • How is that related to your being on the Release Council?
  • What does your company want to achieve by your being on this Council?
  • What do you, personally, want to achieve by being on this Council?
  • What is success?
  • What does success look like for the Symbian community?
  • What does success look like for the Release Council, in terms of achieving the Symbian community’s success?
  • What should our group goals be?
  • What do we, as a group, need to do to achieve that?

Make A Pledge! More on that at the session!


Workshop 2 1300 - 1600: Running Symbian Releases

Participants: All RC member

Facilitator: Victor Palau (SF)

The intent is to cover tactical direction in this workshop and is a key one for influencing how releases are planned, managed, reported and delivered. Some RC members have asked to have discussions on this so this is a great opportunity to get you views raised and discussed.

An example of the topics which could be covered:

  • What do members want and need from the SF and RC
  • How do we improve planning, tracking and risk mitigation and provide visibility and flexibility in the management of releases?
  • How do we establish the feature baseline for a release and what is needed for this?
  • How do we ensure quality is achieved?
  • How do we ensure milestones are successful?
  • How do members get involved more closely in release projects and in the RC itself
  • What do the members need from release managers?
  • How do we interact with other councils and what information should be shared?
  • What can we learn from the way other OSS projects run and deliver their software (Android, Eclipse, Limo, etc)?
  • Draft and agree the mandate of the Test WG to help define the test strategy for releases

The plan is to have one of the non-SF RC members facilitate this workshop.

DAY 2 - 30th October: RC Meeting

  • 0900 Welcome & Agenda
  • 0915 Key outcomes, highlights, views and follow-up from Day 1 workshops
  • 1000 Actions review - Mark/all
  • 1030 Break
  • 1045 SDKs and Non-member PDKs - Urmi
  • 1100 S^2 baseline and BC break handling
  • 1115 S^2 Status - Victor/Mark
    • TPIP status
    • Defect handling - showstopper defects
  • 1130 S^3 Status - Victor/Mark
    • High level plan
    • Key features update and ratification
    • Integration Plan
    • Key issues & risks
    • Release Start assessment & decision (ratification)
    • Feedback from RC members on PDKs
    • ZoomSW Plan progress - TI
  • 1230 Lunch
  • 1330 S^4 Status - Urmi
    • Release Start criteria
    • Draft plan
    • Draft KFs
    • Key risks
  • 1400 Working Groups review
    • Quality - Nithya
    • Packaging Tools
    • Getting the Test WG started
  • 1445 Proposals pipeline update - Mark
  • 1500 Break
  • 1515 How do we foster better RC involvement?
  • RC calendar - next meetings
  • 1600 Adjourn

Actions

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

Material

Background information on API definitions for AC approval:


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

Attendance

  • Symbian : Mark Skebels (Chair), Jim Clarke, Urmi Shah, Victor Palau, Sebastian Brannstrom (Public API presentation), Nithya R (QWG presentation)
  • Digia: Petri Poikolainen
  • Elektrobit: Kim Aitto-oja
  • Fujitsu: Yoshiiku Hanai, Chandra Narayanasamy
  • Nokia: Riku Mettälä, Jussi Asikainen
  • NTT DoCoMo: Manabu Matsuura, Seishi Tsukada
  • Sony Ericsson Mobile Communications: QuakOnn Liew
  • ST Ericsson: Philippe Gaudillat
  • Texas Instruments: Laurent Le Gal, Sonia Ferrante (guest)
  • Teleca Ilkka Korhonen
  • Samsung No representative

Existing Open Actions

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

The following actions were agreed to be closed:

RC050809_2, RC270809_1, RC270809_12, RC270809_13, RC240909_1, RC240909_3, RC240909_4, RC240909_5, RC240909_6

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


Workshops Update - Mark & Victor

Both workshops were well attended and productive. Thanks to all RC members for their contributions! Thanks also to Lauren Sarno and Victor for facilitating.

Details and actions of the workshops will be published on this link: http://developer.symbian.org/wiki/index.php/RC/RC_Workshops_2009_10_28

A specific action worth bringing out in these minutes is the involvement of the RC in Major Contribution Proposals (MCPs). The RC agreed that we should play a more active role in reviewing the MCPs (see this link http://developer.symbian.org/wiki/index.php/Proposals_pipeline) and provide timely feedback to the FRC. The RC does not need to vote. The proposals pipeline wiki will be updated to indicate which MCPs the RC should review (by default it should be all).

  • ACTION RC301009_1: Mark to add agenda item to RC meetings for MCP input. Due: Latest 1 week before RC call.

The main purpose of the RC reviewing MCPs is to determine whether there is sufficient information on delivery timeframes and releases. The RC should not become a bottleneck or cause a delay. Two examples of current MCPs are SMP which clearly defines which releases content is planned for and SHAI which has no such information.

There was also a proposal from TI to agree the level of detail required per package feature in order to decide whether they should be part of the "Key Feature List" or not.

  • ACTION RC301009_2: Laurent to create a forum discussion by posting TIs proposal on the detail to be provided in each feature. Due: 13/11/09


SDK & Non-member PDK Status - Urmi

Urmi presented the SDK/PDK status. Refer to SDK Status charts.

Beta SDK will be for full public release. Intent is to get feedback on usability.


S^2 baseline and BC break handling - Sebastian Branstromm

The list of public APIs has been made available on the wiki as already communicated to the RC.

The AC is reviewing this list to ratify the baseline. A whitelist of breaks is also available but does not have any details behind teh reasons for approving these breaks.

  • ACTION RC301009_3 Sebastian to to talk to Daniel Rubio about outcome of AC discussion. Due: 6/11
  • ACTION RC301009_4: Sebastian to clarify the plan for identifying 'real' breaks. Due: 13/11


Sebastian presented the process for break handling (refer to BC break process charts). No disagreement with the process was tabled by the RC. He also clarified that we currently run static validation for BC, and the plan is to start including dynamic testing in the near future.


S^2 Status - Mark & Victor

Refer to S^n Release Plan presentation.

The RC discussed the decision on when S^2 is stabilised relative to the current hardening activities (by Docomo and Fujistu).

This led to questions and discussion on what the 'Stabilised' milestone and Hardening phase mean. Although these are defined in the Release Model, there is confusion over this in relation to quality criteria and levels.

Points to note:

  • the Hardening phase refers to activities undertaken by users of the release (the Community), such as unit and system test. These activities should lead to raising the quality of the platform. This requires that defect fixes are made available by the community (i.e. contributed back).
  • it is difficult (if not impossible) to set generic quality criteria to be satisfied at the outcome of this phase since the SF does not have direct control over how that would be achieved. Quality is largely dependent on hardening activities in the community. OEMs/ODMs productising on a release will define quality levels that must be met for their purposes and ensure activities are in place to meet these. The community as a whole also need to contribute to the hardening of a release where possible.
  • information on defects that have been discovered should be made available (via Bugzilla) by anyone engaged in hardening. There may be some instances where such information is commercially sensitive and cannot be made public, but this should be the exception.


  • ACTION RC301009_5: Chandra N to lead a discussion to clarify the conditions for 'Stabilised'. Mark emphasised that the intent is not to reopen the Release Model but to clarify these points. Due: Forum to be set up within 2 weeks of the RC. Review to be held at next RC call.


S^2 conditions for FC

LBS SUPL is planned for w45. Will be available in PDK2.0.1 as source code, also to be delivered for S^3 in the same week.

Helix will also be delivered as binary (we are engaging with Real with respect a possible source contribution).

With these and ratification of the API baseline, all conditions will be satisfied.


A question was raised on how many other TPIP items were remaining (the ones listed for the FC were the 'must-haves').

  • ACTION RC301009_6: Victor to come back with a response to this. Chris Davidson will also be asked to present the status at the next RC meeting. Due: 3/12?


Hanai-san (Fujitsu) commented that Java is important but SF is not delivering in S^2. Victor commented that SymbianJ is planned to be delivered in S^3, the current plan is for a Q1 delivery, this will be a combination of open source contribution and binaries under R&D. The solution will not work out-of-the-box in S^2, however Fujitsu-san should be able to access enough source to back-port it.


Showstopper Defects

SF confirmed that Nokia has published a set of showstopper defects against S^2 in Bugzilla.


S^3 Status - Victor & Mark

SF confirmed that PDK3.0.a and .b are both available.


Release Start

Conditions for this milestone are in place except for ratification of the KF list (and associated integration plan items).

KF Status:

  • 3PC and WDP delivered in PDK3.0.a
  • SymbianJ forecast delivery is March 2010 which is post FC. SF proposed that this can be handled as an exception due to its self-contained nature (i.e. minimal external dependencies). (Note that SymbianJ is currently available from Nokia under a separate agreement if required until made available in S^3). No objections raised by RC.
  • NFC: Delivery of this has changed from w48 to w06 and therefore puts FC at risk. PkO has confirmed possibility of w04 delivery as well as earlier drops (staged integration). However, Jussi commented that his understanding was that NFC would not make it for S^3. RC agreed to red flag this until teh plan is confirmed (see action below).
  • Execution Environment: Confirmed that Zoom2 baseport is available for S^3. However, original ZoomSW plan dates beyond this are not clear. (See action below).
  • NGA: IP has been under dispute leading to potential delay of NGA. Approval of APIs under review 30/10. (Update: This has now been approved). (If approval was not received, alternative GCE would need to be sourced).
  • SHAI: SF confirmed that nothing beyond currently available APIs/components will be delivered in S^3. AC will need to ratify existing APIs as part of baseline going forward. RC agreed that SHAI will remain in the KF list and existing components will be checked as delivered.
  • SMP.1: SMP kernel propotype now available under EPL. S^3 plan is to have all OS packages validated for SMP Safe. Current rate will be tracked on the platform release plan.

ACTIONS:

  • RC301009_7: Jussi to confirm NFC availability and dates. Due: 13/11??
  • RC301009_8: Laurent to provide update to ZoomSW plan. Dependencies need to be understood. Due: 20/11


The outcome of the above discussions was that Release Start (RS) is approved on the basis of the currently identified KFs and associated actions. This list will be baselined for the release and KFs can be added or removed under change control.


S^4 Status - Urmi

Urmi presented overview of KFs and high level plan for S^4 (refer to S^n Release Plan presentation). Features of significance are:

  • Qt
  • Orbit
  • DirectUI
  • SMP.2
  • SHAI


A plan for binary compatibility is being discussed with Daniel Rubio.

RS is planned for Dec 09 but significant work needs to be done to approve MCPs and secure delivery dates. Urmi to ensure FRC and AC understand urgency of release deadlines.

ACTIONS:

  • RC301009_9: Add delivery dates for KFs on the table (and ensure alignment with integration plan). Due: 3/12/09
  • RC301009_10: Urmi to prepare status update on RS for RC conf call in December with view for RC to ratify either at that call or before the Christmas break. Due: 3/12/09 (1 week before conf call).


Working Groups Update - Nithya/Mark/Jim

QWG

Nithya (QWG lead) presented the QWG status. Refer to Quality Metrics Workgroup presentation.

The team has made good progress on defining metrics and the quality dashboard is now available here: http://developer.symbian.org/wiki/index.php/Quality_Metrics/Snapshot_20091002

The QWG landing page with further information can be found here: http://developer.symbian.org/wiki/index.php/Quality_Metrics/Metric_Snapshot_Archives

  • ACTION: RC301009_11: RC to feed back comments to QWG via QWG email: qwg@lists.symbian.org. Due: 20th November.


Packaging Tools

Quorum membership now available. Jim to kick this off in November.


Test WG

Quorum membership now available. Thanks to all volunteers and to their companies. The WG will be kicked off within the next 2-3 weeks, chaired by the SF. The membership list is:

  • Chandra Narayanasamy (Cell/Fujitsu)
  • Pierre Leblond (STE)
  • Mikael Christersson (SEMC)
  • Janne Kolari (Digia)
  • Fred Maurel (TI)
  • Andrew Cooper (Nokia)
  • Plus SF members


Meetings Calendar

Next meeting: Conference call will be held on 10th December, 2009. This may be an extended call (call is normally 2 hours) since combining November and December meetings.

Next f2f: Kindly hosted by Docomo in Tokyo the week of 11th January, 2010. The proposal is for the RC to hold meetings 13-14th January. Council members should confirm whether they are able to attend these in person.

Retrieved from "http://developer.symbian.org/wiki/index.php/RC/2009-10-29_RC_meeting"

Comments

Sign in to comment…