Symbian Release Planning
From Symbian Developer Community
So what is ‘Planning Flow’ anyway?
The diagram below depicts the set of plans we use to define, manage and track our releases, and the relationships between these plans, or put another way, how the different planning artefacts link to each other.
Why do we need them? To provide a common understanding and basis for agreeing: what will be delivered, when it gets delivered and how it gets delivered and then to manage the execution of releases against these plans to a successful outcome.
This starts from the Platform Plan (or Roadmap) owned by the Platform Propositions team and reviewed with the Features & Roadmap Council, and develops into the set of plans owned by the Release Management team and reviewed with the Release Council. These include the Platform Release Plan, the S^n Release Plans, the Integration Plan, the Test and Quality Plan and the Kits Schedule.
Click on the picture above to drill down on a specific item or use one of the following Quick Links to Symbian Release Planning Pages
- The Symbian Release Plan
- The Symbian Integration Plan
- The Symbian Kit Schedule
- The Symbian Release Model
- The Release Council
Contents |
The Release Plan
Part of the remit of the Release Council and the Release Management Team is to ensure the delivery of the agreed roadmap. The latest progress towards the fulfilling the platform plan is capture in the Release Plan:
The Integration Plan
The Integration Plan contains a group of selected package features from the package backlogs that are followed closely by the Release Council in order to understand that status of the releases and availability of content in the kits.
Kits Release Schedule
Once you look at the plan to deliver new features to the latest release you might want to see when the next kit will be available for download and what does it contain . You can find all this information in the Kit Release Schedule
Build Results
We regularly build the platform in order to create candidates for new kits. If you want to keep up to date on the progress towards the next pdk, you can follow the published build results:
"FCL Builds" are currently the ones used to create PDK candidates, this means that the build contains at least one FCL.
Details on how to rebuild the platform build can be found in the release notes of each PDK.
Test and Quality Plan
- For the latest release quality metrics please see the Metrics Snapshot Archive
- For information on testing follow the progress of the Test Working Group
Hot Topics
A few threads which are currently interesting in the Release Council Forum
Symbian^2 Defect Scrub
We are preparing a scrub exercise for Symbian^2 as we near hardening. You can find more information on the wiki
Test Working Group
Test is a hot topic in the Release Council - you can follow the progress on the working group here
MCPs
The RC has reviewed the minimum content MCPs should contain for delivery purposes and voted on the need to review Qt, Orbit, DirectUI and SHAI as well as approving SMP and Single Tap. (Release Council MCP Review Criteria)
The results can be found here: MCP comments
Release Management Team
The release management team facilitates the Release council and also provides project management services for the Symbian Platform Releases.
- Jim Clarke - The boss
- Victor Palau - S^2 and Integration/Contribution Planning
- Mark Skrebels - S^n Release Programme and Release Council Chair
- Urmi Shah - S^4 and SDKs
- Nithya Rajendrababu - Tools and Quality working group
- Sebastian Brannstrom - Compatibility and SDKs
Useful Release Information
Symbian Release Model
SF_Release_Model_Description_r3.1
Symbian Release Council
Comments
Sign in to comment…
