From Symbian Developer Community

Back to main Release Council wiki page

Proposed Agenda

• 0800 Welcome & agenda
• 0805 Actions
• 0825 S^2 Update:
  • Recap of announcement
  • Ratify S^2 Functional Complete (FC should have been achieved before the RC meeting by vote)
  • Status of S^2: PDK, etc
  • Confirm feedback on TPIP priorities for S^2
• 0910 Comments on S^3 plan (S^3 plan update will be posted ahead of the RC)
• 0940 Agenda for f2f RC meeting in Helsinki
• 1000 Close

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

• Release Plan

Minutes

S^2 Functional Complete candidate review

VictorP put forward PDK_2.0.D as the candidate for Functional Complete in S^2. This is supported by the Regression test that were presented by RikuM (Nokia). The test report distributed to the council is slightly older (week24) than the contribution baseline for pdk2.0.d (week26). However, it provides a good understanding of the maturity of the asset.

FredB(TI) asked if it was possible to have a list of the failing test cases, JimC suggested that publishing the showstoppers in Bugzilla instead would be more adequate. The Release council agreed to review the report and provide feedback via email if required. VictorP also presented the final prioritisation on TPIP items deem key for the release and provided an status update for each.

We briefly discussed SDK plans for S^2, and noted that SDKs are aimed at aftermarket application developers rather than the device creation community.

Actions from this discussion were:

• RC050809_1 Send an voting request o the Release Council Email list S^2 Functional Complete as PASS.
• RC050809_2 Check with Daniel Rubio what is the level of compatibility of S^2 with Symbian^1
• RC050809_3 Present a proposal for SDK in S^2 at the next f2f.

S^3 Plan

Key Feature list was presented to the release council, everyone was asked to review the list and provided feedback. Nokia was asked to provide feedback on the likelihood of the features being delivered in S^3 (RC050809_4).

FredB commented on SMP and the fact that there is no contribution proposal being presented yet for the overall programme. Question was raised on where can we provide feedback, VictorP took an action to set up a discussion in the Forums.(RC050809_5). FredB noted that he would like more information like what components are changed, which APIs are changed, etc.

S^3 FC criteria is now available for review. A Forum Voting poll will be started to capture the agreement with the high level criteria proposed (RC050809_6). FredB asked if the smoke test and sanity test content will be available, VictorP clarified that the intention is to make the coverage and content of the suites public.

RikuM raised the point of a "Must have" feature list, as this seems to be going against the concept of timeboxing the release. JimC clarified that the aim is to have a feature list set that can be baseline and tracked, the list must be agreed with the FRC. In the case that the release reaches FC and a set of features is missing this will be de-scoped as long as there is still a value/valid commercial proposition for the Release. VictorP took an action to re-phrase this criteria in the context of "Value of the release" (RC050809_7).

DaveM requested for a date when the baseline will be issued for the feature list. This is depended on the RC and FRC feedback, but we will target end of August.

Also it was clarified that the public APIs for S^3 (against to run BC testing) will be decided by the Architecture council, this has to happen before FC and therefore is a dependency on them.

Next Face 2 Face

We did a roll call on who was able to attend the face2face, this has been capture in the attendance table.

The following items were proposed to be added to the agenda:

• Milestone proposal
• SDK & Compatability story
• Test Strategy/content
• Graphics & Zoom integration

Attendees

Comments

Sign in to comment…