Build and Integration
From Symbian Developer Community
Contents |
Plan for Availability of Graphics and NGA in Symbian^3
You can find about the plan for PDKs with NGA improvements here
For more information on the bring up efforts please see the Graphics_Package/KhronosReferenceImplementation wiki
Kit Release Schedule
FROM PDK2.0.0 and PDK3.0.b (both included) all PDKs are now publically available
| Date | PDK | RnD | iSSK | PDT | Phase | Status | Key content |
|---|---|---|---|---|---|---|---|
| wk50 | PDK_2.0.2 | rnd2.0.2 | issk2.0.2 | pdt_1.3 | Hardening | Available | includes OpenVG Khronos reference implementation |
| wk10 | PDK_3.0.h | rnd3.0.h | issk3.0.h | pdt_1.6 | Evolving | Available | Nokia's week07 contribution |
| wk12 | PDK_3.0.i | rnd3.0.i | issk3.0.i | pdt_1.6 | Evolving | Forecast | Nokia's week10 contribution |
| Q1 | PDK_2.0.3 | rnd2.0.3 | issk2.0.3 | pdt_1.? | Hardening | on demand | if required by the community |
| Q1 2010 | PDK_4.0.a | ?? | ?? | ?? | Evolving | Forecast | Current plan for S^4 Start |
| Q1 2010 | PDK_3.0.0 | ?? | ?? | ?? | Baseline | Forecast | Current plan for S^3 FC |
- Available = ready for download
- Planned = included in the current agile iteration for the build team
- Forecast = Best estimate based on contribution information and community priorities
- on demand this PDK will only be created if requested by the community
NOTE: Nokia's Week49 was cancelled due to delivery issues.
Significant Past Kit Releases
| Date | PDK | RnD | iSSK | PDT | Phase | Status | Key content |
|---|---|---|---|---|---|---|---|
| 2009wk23 | PDK_2.0.b | rnd2.0.b | issk2.0.b | pdt_1.0.b | Evolving | Available | First graphic based S^2 PDK |
| 2009wk42 | PDK_2.0.0 | rnd2.0.0 | issk2.0.0 | pdt_1.1 | Hardening/baseline | Available | Baseline for S^2 - move into hardening |
| 2009wk43 | PDK_3.0.b | rnd3.0.b | issk3.0.b | pdt_1.1 | Evolving | Available | first S^3 public PDK |
| 2009wk43 | KTK | - | - | pdt_1.1 | - | Available | one off Kernel Taster Kit to work with opensource Kernel |
| 2010wk01 | PDK_3.0.e | rnd3.0.e | issk3.0.e | pdt_1.3 | Evolving | Available | Fist UI enable Emulator for S^3 |
| wk07 | PDK_3.0.g | rnd3.0.g | issk3.0.g | pdt_1.5 | Evolving | Available | Nokia's week05 contribution - Build from a fully EPL base line! + Caldav from Sun |
For other Previously released kits click below:
Tip: Check this link or here to convert week numbers to dates.
For details on kits content see here. The detailed preparations for the next Symbian^2 PDK release are recorded here, and questions or comments should be directed to the Build and Integration forum.
Note that the build team follows biweekly Scrum Iterations, with Planning and Demos on a Thursday , so expect updated information on Fridays.
To receive the latest information on kits releases, please subscribe to our email list.
Kit Release Phases
- Evolving = Kits from a release that has not yet reach Functionally Complete (FC) and it is open for contributions. Expect significant new functionality to be added from previous release
- Baseline = API baseline for the release
- Hardening = Kits from a release that has reach FC. Expect mainly churn due to bug fixes and small enhancements
- Stable= Kits from a release that has reach the end of hardening. Expect very little churn only due to critical defects.
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.
Kit Release Naming Convention
We are follow a naming convention which will be used for package releases as well as PDK and SDK releases:
[ Name ] _ [ major ] . [ minor ] . [ patch ]
A change to [ major ] implies a significant change in functionality. A change to [ minor ] implies a smaller change in functionality that is fully backward compatible. A change to [ patch ] implies bugfixing and other minor changes.
The numbers start at "a" for a pre-release, increase though "b", "c", ... "aa", "ab", ... until the release is ready, at which time the sequence switches to numbers, starting from 0.
For PDKs the major release version number is the Symbian Platform release number. The alphabetic patch number indicates where we are in progress towards the definition of the associated API baseline, and will change to be numeric when the baseline is declared. We don't currently expect to use the minor number for PDKs, so it will stay at 0.
Examples:
| PDK_2.0.a | Pre-release "a" of PDK for Symbian^2 |
| PDK_2.0.b | Pre-release "b" of PDK for Symbian^2 |
| PDK_2.0.0 | First release of the PDK which implements the Symbian^2 API baseline |
| PDK_2.0.7 | Bugfix release of the PDK which implements Symbian^2 |
| PDK_3.0.a | First pre-release PDK for Symbian^3 |
An increment on a "more significant indicator" would reset a "less significant indicator". i.e. the first S^3 PDK will be pdk_3.0.a. Therefore only one indicator would change from one update to the next.
How often will I get a new PDK version?
We are striving to achieve a common release rhythm for all kits, the following picture represents the delivery model that we are aiming at. The intention is to achieve weekly kit releases once contributions become more regular.
Other Related Symbian Release Planning Pages
- The Symbian Release Plan
- The Symbian Integration Plan
- The Symbian Kit Schedule
- The Symbian Release Model
- The Release Council
Comments
Sign in to comment…
