RC/2009-12-10 RC meeting
From Symbian Developer Community
Back to main Release Council wiki page
Contents |
Agenda
Please note that this conference call will be 2 hrs 30mins (08:00 - 10:30 GMT)
- Welcome & Agenda - 5
- Actions update - 15
- TPIP Status - 15 - Chris Davidson
- S^2 status - 10
- Quality Metrics
- S^3 status, progress, issues - 20
- Extended KF list ratification
- FC criteria revisit: Quality levels, testing
- S^4 status, progress, issues - 20
- Planning status
- RS review
- Zoom2 plan update - 15
- MCP update - 15
- WG updates - 10
- Test WG - Mark
- Packaging Tools WG - Jim
- UI WG - Urmi
- January f2f RC - 10
- 12th Jan: TBD
- 13th Jan: Workshops
- 14th Jan: RC f2f
Actions
Both Open and closed Actions have been updated with to reflect the output of the council meeting
- Click here to access the Release council Open Actions
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
Attendance
- Symbian : Mark Skrebels (Chair), Jim Clarke, Urmi Shah, Victor Palau, Chris Davidson (TPIP)
- Digia: Petri Poikolainen
- Fujitsu: Yoshiiku Hanai (start only), Chandra Narayanasamy
- Nokia: Riku Mettälä (until 0940GMT)
- NTT DoCoMo: Manabu Matsuura, Seishi Tsukada
- Sony Ericsson Mobile Communications: Anders Josefsson
- ST Ericsson: Philippe Gaudillat, Pierre-Henri Maitre
- Texas Instruments: Laurent Le Gal
- Teleca Ilkka Korhonen
Did not attend
- Elektrobit: Kim Aitto-oja
- Samsung No representative
- QuiC: Rob Dunder, PJ Bostley
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 were agreed to be closed:
RC301009_1, RC301009_2, RC301009_4, RC301009_6, RC301009_7, RC301009_8, RC301009_9, RC301009_10, RC301009_11
New actions appear in these minutes and have been incorporated into the actions table.
TPIP Status - Chris Davidson (SF)
Chris presented the latest TPIP status. Refer to the TPIP charts in the Materials section of these minutes.
Noted that 20 items are currently open and are being worked.
Laurent (TI) asked what percentage of closed items do OEMs need to take action on. Chris responded that it depended on exactly what features an OEM was interested in shipping on a device and the data is best sourced from the TPIP spreadsheet available here
STE representative asked what is the link between features in a S^n release and any related IP items that are needed for the features. Victor responded that these are not (normally) covered in the integration plan. The release notes cover the IP needed.
Victor also requested that if RC members believe there is any information around IP that is missing to please email Chris and Victor.
No more questions were raised.
Chris also gave a 'sneak preview' of work in progress to define Core Components required for a phone as well as Complementary Components. This information is planned to be available by year end and will be published.
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.
No question raised.
S^2 Status - Victor
Compatibility: A question from the council was what was the baseline for the compatibility comparison. Victor responded that this is measured against S^1.
Laurent (TI) commented that the information on compatibility breaks is good. He asked if the "resolution" field could be added to the wiki table. Victor agreed and implemented it during the meeting.
Quality: Laurent (TI) asked how many of the defects raised against S^2 are raised by the community vs raised by SF.
- ACTION RC101209_1: Victor to provide this information.
Mark asked how we know which components a defect impacts. Victor responded that this information is available via the metrics wiki pages by drilling down.
Pierre-Henri (STE) commented that at least the critical defects surely must be fixed. Victor responded that the severity shown for defects is assigned by the person raising the defect. The PkO must assess what severity applies to the defect.
Victor also pointed out that there is little engagement by PkOs on the defects at this point. It is also up to the community to fix the defects. If the community does not believe a defect needs to be fixed then this is probably a reflection on its criticality or importance.
Chandra (Fujitsu) suggested a working 'committee' is set up to look at the bugs and decide which are critical. Victor commented that this may be useful. The committee should look at the impacts these defects have but it is up to the PkO to decide the severity.
The criticality (severity) is an assessment of the impact on the assets but does not imply a priority to fix. Again, there has been limited engagement by PkOs on addressing defects. The SF has been trying to engage PkOs with limited success.
Mark asked whether it was possible to get a quick assessment of the defects currently marked as critical. Victor agreed this may be possible.
ACTION RC101209_2: Victor to take the critical defects to PkOs and get them to give their view ASAP.
PDK2.0.2: includes an software implementation of OpenVG provided by Khronos. This can be use for normal OpenVG commands and it is also use to rasterise icons
S^3 Status - Mark & Victor
Key Features: Victor took the council through the extended KF list (including original KF's). Key points and issues:
- SymbianJ: 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 (RED): Riku (Nokia) explained that Nokia has re-prioritised this feature and plans for delivery are under review, however, it will not be available for FC. Nokia still plans to contribute this to SF but timeline for this is not known yet. It could be delivered on S^3 via a FCL. Jim (SF) proposed that we keep NFC on KF list and track as part of S^3 until or if a decision is made to deliver in a subsequent release. NFC is marked RED until delivery plan and strategy understood and agreed.
- The RC unanimously agreed to keep NFC on KF list and continue to track.
- REE: Good progress. Buildable and bootable UI ROM based on modified S^2 baseport. Not releaseable yet but gives confidence that we can create an S^3 solution.
- NGA (AMBER): We now have a FCL release of NGA. A new PDK will be available this week (3.0.d) with a graphics-based emulator. Some issues will still exist and there will be a further delivery from the UI accelerator pkg scheduled for end Jan. PDK3.0.d will not have icon rendering. So far we are on track to have a wokring NGA solution by FC. The amber status is due to existing risks which are being managed.
- Laurent (TI) asked to clarify what will be delivered in 3.0.d. Victor responded that PDK will be NGA-based with OpenVG and OpenWF but not rendered icons (UI accel needs to be delivered for this).
- SHAI: as discussed in the last RC, the proposal is to mark 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 MCL. Substantial update expected before end of the year.
- CalDav (AMBER): The amber status is due to dependence on a UI enabled PDK. Petri (Digia) asked if there is more information available on this feature.
- ACTION RC101209_3: Victor will send a link to the wiki page to the RC.
- Qt4.6.1 (AMBER): There is no pkg backlog available for this, however, delivery expected Feb. The strategy for support in S^3 is not clear as the view is this is not a compulsory feature for inclusion in S^3 based phones. However, it should at least be available in SDKs to allow early visibility to app developers and smooth the transition to Qt-based frameworks in S^4 onwards.
- Riku (Nokia): Cannot confirm yet when this gets delivered or if it will be in time for FC. Riku does not support having this on the KF list yet since there is not enough delivery information.
- Mark (SF) asked each RC member for their views on keeping Qt4.6.1 on KF list. All members present agreed (with the exception of Riku as noted). Therefore, it was decided to continue to track via KF list.
- Seishi (Docomo) asked whether inclusion of Qt means Avkon is removed in S^3. Victor responded no.
- Riku asked what does accepting a feature on the KF list mean? Victor responded that this means we actively track the feature and it has a significant impact on FC (therefore a decision needs be taken by the RC on any KF feature which is impacted in some way). Riku asked if FRC has reviewed these. Victor responded yes but we will sync with FRC in case there are any significant objections.
- Mark reiterated that the RC owns the KF list and it is our decision which features are tracked. Of course this is done with input from the FRC and AC as required.
- No other comments or issues were raised on the remaining KFs (all of these are GREEN).
- Mark asked each RC member to give their view on ratifying the updated KF list noting the above comments and discussion. All members confirmed they agree with the list as presented. Mark noted that Riku's comments on Qt4.6.1 will be minuted (as above). KF list ratified.
Riku gave his apologies and left at this point due to other commitments.
FC Criteria:
Mark presented the FC criteria the RC had ratified at RS. There are two issues to be examined:
- ability to define quality targets ("X" and "Y")
- availability and execution of sanity tests
Quality criteria are only meaningful if PkOs are engaging on bug review and resolution. As Victor noted previously this is generally not the case at the moment. The defect management process is not being followed.
- Victor suggested holding a workshop to review this at the next f2f in Tokyo.
- Anders (SEMC) and Chandra (Fujitsu) agreed and no objections to this were raised.
- Laurent asked whether we have a good view of the test suited which would be run for FC. Urmi (SF) commented that smoke tests are defined (link is shown in release plan charts). However, there are no sanity tests available yet. Mark commented that Test WG is looking at the whole test scenario and will come up with recommendations.
- ACTION RC101209_4: SF to set up workshop for FC criteria including Quality and Testing and covering S^3 and S^4. This will be planned for the 13th Jan.
S^4 Status - Urmi
Urmi identified they key issues and risks in S^4 around delivery plans for the KFs. In particular, DirectUI and SHAI have no delivery information. Two options for proceeding with Release Start were put forward (see release plan presentation). The discussion and proposals centred around the value of delaying release start.
- Option 1: Approve RS on the basis of the KFs that have delivery information (Qt, Orbit, SMP, BT LE, Internet Radio). Add other KFs (DirectUI, SHAI) as informatio becomes available. The question is whether the release is viable without DUI and SHAI. Mark noted that the FRC views the core value of S^4 as Qt, Orbit and DUI.
- Option 2: 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.
Pierre-Henri (STE) commented that SHAI is a concern since there is no delivery info and that it is not under control for S^3 and S^4. Urmi commented thatS^3 does have existing APIs and implementations that are SHAI compliant.
Mark asked the RC members for their view on option 2. That is, approve RS with red KFs as exceptions but a plan for delivery information is needed to pass RS. The forecast for RS is Jan 2010 and would be tabled for RC approval at the f2f.
- All RC members present, except Anders agreed.
- Anders: unsure of the implications but agrees that it is important to start the release. What happens if DUI for example does not deliver for FC?
- Riku had left the call by this time so the decision also needs to receive Nokia's input
Zoom2 Plan - Laurent
There was not time to cover this in the call. Laurent has emailed an update to the RC members. Please provide any commets back to him.
MCPs - Mark
Input has been received from all members except Elektrobit.
- ACTION: RC101209_5: Mark to summarise the information and provide a way forward via email or forum.
WG updates
- Packaging Tools WG: Jim proposed to cancel this WG as a quorum could not be found (despite some volunteers). He proposed to turn this into a fact-finding mission and pursue via forum or other means.
- Test WG (Mark): This is underway with the 3rd meeting held 15th Dec. Good representation across the member companies. The progress and outputs of this WG can be found here: http://developer.symbian.org/wiki/index.php/Test_Working_Group
- UI WG (Urmi): ACTION RC101209_6 Urmi to provide an update via email.
Next f2f in Tokyo
This is being hosted by Fujitsu with support from Docomo. Hanai-san stressed earlier that it is important to have a quorum for these sessions and current attendance figures look low across councils. Fujitsu and the SF strongly encourage members to attend. If there are issues with this please contact Mark. Also please respond to Miriam Mickail's email asking for input on attendance. The RC sessions are:
- 12th Jan: use for 1-1's. Also councils dinner in the evening.
- 13th Jan: RC workshops. One of these will be the FC criteria discussion
- 14th Jan: RC f2f meeting. SF will provide draft agenda for comment.
Meeting adjourned 1034 GMT. Thanks for your attendance!
Happy Christmas & New Year from all of us at the Foundation!
Sign in to comment…
Hi Mark,
I have added my recollections to the minutes, thanks
--Victor 10:03, 15 December 2009 (UTC)