RC/2009-05-20 RC meeting
From Symbian Developer Community
Back to main Release Council wiki page
Contents |
Agenda
Chair: Jim Clarke Apologies: Victor Palau Minutes: Mark Skrebels
(BST Time)
- 8:00 - Roll call
- 8:10 - Approval of previous minutes and Actions from last RC
- RC230409_1 Ratification of CRs to Charter - Result: Approved
- 8:40 - Update on contributions - Nokia
- 8:50 - Update on Tools Contribution - Nokia
- 9:00 - PDK update - Jim Clarke
- 9:15 - Agreement of key principles of the release model
- 9:55 - Closing remarks
Material
Attendees
- Riku Mettälä, Nokia (RM)
- Anders Josefsson, SEMC (AJ)
- Moussa Belkhiter, TI (MB) unavailable
- Philippe Peruset, STE (PP)
- Seishi Tsukada, DoCoMo (ST)
- Yoshiiku Hanai, Fujitsu (YH)
- Stefan Fager, Fujitsu (SF)
- Chandrashekar Challagonda, Teleca (CC)
- Kim Aitto-oja, Elektrobit (KA)
- Tero Savolainen, Elektrobit (TS) unavailable
- Petri Poikolainen, Digia (PP)
- Victor Palau, Symbian (Interim Chair) (VP) unavailable
- Jim Clarke, Symbian (Chair) (JC)
- Laurent Le Gal, TI (LLG)
- Ilkka Korhonen, Teleca (IK)
- Philippe Gaudillat, STE (PG)
- Miyauchi-san, DoCoMo
- Mark Skrebels, Symbian (Minutes) (MS)
Minutes
Update on Actions from last RC meeting
See updates to actions table below.
Further discussion on RC230409_9 - RM to clarify if all Symbian 9.4 functionality is available standalone with no dependencies on S60.
Stefan asked which components are impacted (by legal restrictions for example). Riku asked that a list of required components is provided so that he can respond whether these are or are not affected.
A new point was raised related to this discussion on access to the list of components. Jim responded that there is currently not a standardised way of showing content of builds. This is being worked based on the System Model but is not straightforward due to restructuring of code.
ACTION: JC to update the status and issues of providing this at next RC meeting. This is an issue that should be shared with the community.
Hanai-san asked when a list could be made available. Jim responded that a "simple" list could be sent soon (TBD).
Agenda and additional actions
Transparency
RC proceedings are by default publically available.
Jim raised the point that there may be instances where material is not ready or suitable to be made public and should remain within the Council. This could be because material is not standalong or may be misinterpreted externally. Therefore, by exception, material could be distributed to members only. Members should indicate whether should be the case.
Related to the above, members should ensure that templates used for presentationjs or documents have security settings cleaned up. For example, some material currently available shows "Company Confidential".
TPIP (Third Party IP) List
Current list (spreadsheet) needs to be updated/improved to clearly show the impact, priority and actions needed for any components which are missing as a result of TPIP filtering. Expect subscription to the list to be available in next couple of weeks.
Update on Contributions from Nokia for Symbian ^2 and ^3 (Riku)
Symbian ^2: TB9.1 branch will be after w22 (this is based on S60 5.1 and Symbian 9.4). Defect fixes and some new functionality will come in after the branch.
Philippe wanted to know how we could find out what this would be.
ACTION: Riku to send list of post-branch content and defect fixes.
Symbian^3: (5.2/9.5+). Enters internal MCL w24.Exact date depends on TPIP cleansing.
Anders asked whether the two releases are being submitted to the SF at the same time. Riku responded yes and these will be available biweekly.
Chandrashekar asked how to know what features and fixes are coming in so that product integration planning can be done.
Also, what is the lifetime of a platform, i.e. may only have three releases active at any given time. Jim responded that if required, we could continue to keep a release active (but perhaps at the expense of other releases).
How do we know what works or not in releases?
Jim: There will be release notes (but these are static). The latest info will come form Bugzilla.
Riku: Nokia will at least ensure showstopper defects are captured in Bugzilla.
Hanai-san: Raised question on TPIP situation in releases.
Riku: TPIP R&D licences are being negotiated (where there is no agreement to make code available open source). The SF should maintain a list of what is and is not licenced. This is made (or will be made?) via email subscription. (See the TPIP agenda item discussion above).
Hanai-san: Who has responsibility for TPIP in the SF?
Jim: This impacts every council. The FRC has the long-term view of agreements. Maintained via a spreadsheet which shows when the TPIP technologies will be available in releases. The RC is ultimately responsible for what gets delivered in releases.
How do we know if action is being taken on a defect?
Jim: Workflow in Bugzilla shows the status.
Update on Tools (Riku)
How are tools made available?
Riku clarified that Members have access to tools. This may take longer for non-members due to availability of source code. For some tools the source code is the executable (i.e. there are no binaries).
How are tools dependencies on new functionality known? Is that via the FRC?
ACTION: Jim to discuss and clarify within the SF
Kits Overview (Jim)
Hanai-san: Are releases functionally complete?
Jim: Releases are functionally complete based on Nokia release but question is over how much of the TPIP R&D solutions are in place.
When do the limitations on p4 of the presentation disappear?
Jim: Graphics is a larger problem. Problem is for S60 emulator (public release of emulator). Different issue for HW.
ACTION: Jim to explain impact of emulator and HW and what we expect OEMs to do.
Next RC Meeting
The next meeting will be 23rd June in London (f2f meeting)
Actions
| ID | Status | Action Description | Assigned to | update |
|---|---|---|---|---|
| RC230409_1 | CLOSED | Victor to email requesting approval of council Change Requests. | Victor | click here to see vote thread.
Approval of Charter was via email. Victor to update forum wiki to indicate approval of Charter. Victor to check & update mailing list (some members missing). victor: Done - deleted the thread |
| RC230409_2 | CLOSED | Victor/Jim to clarify grant-back time for innovations for SFL and EPL. | Victor/Jim | see email
Victor responded by emailo and archived |
| RC230409_3 | IN PROGRESS | Jim/Victor clarify the difference between VT4 and functionally complete. | Jim/Victor | Emailed Nokia, awaiting response.
Material to be available for next RC meeting (23rd June) |
| RC230409_4 | CLOSED | Victor to distribute the release model details for ratification. | Victor | Click here to discuss
Link available in last RC minutes. Will be added to agenda for next RC meeting |
| RC230409_5 | CLOSED | Victor/Riku distribute existing Symbian and S60 Milestone definitions with SF milestones | Victor/Riku | This will be combined with RC230409_3 and this action closed. |
| RC230409_6 | IN PROGRESS | Victor to initiate the following offline actions
| Victor | Requested participants from RC members
Victor to follow up with proposal in next two weeks |
| RC230409_7 | CLOSED | Victor/Jim to validate that R&D license can be used to perform operator testing | Victor/Jim | see email |
| RC230409_8 | CLOSED | Victor to clarify if CDB, CBR are command line tools or eclipse plug-ins. | Victor | response can be found here |
| RC230409_9 | CLOSED | Riku to clarify if all Symbian 9.4 functionality is available standalone with no dependencies on S60. | Riku | response can be found in post meeting note
Riku: In general, components are available unless removed as a result of TPIP filtering. Source code still available for components which are not used by S60 but these won't be maintained by Nokia. |
| RC200509_1 | OPEN | Update the status and issues of providing list of components (content of builds) at next RC meeting. This is an issue that should be shared with the community. | Jim | |
| RC200509_2 | OPEN | Riku to send list of TB9.1 post-branch content and defect fixes | Riku | |
| RC200509_3 | OPEN | How are tools dependencies on new functionality known? Is that via the FRC? Jim to discuss and clarify within the SF | Jim | |
| RC200509_4 | OPEN | Jim to explain impact of emulator and HW and what we expect OEMs to do | Jim |
Comments
Sign in to comment…
