Meego Wiki
Views

SDK/Two weeks delay proposal

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
-
Initial author: Bob Spencer
+
Initial author: Bob Spencer<br/>
Interested parties:  <place your name here>
Interested parties:  <place your name here>
Line 14: Line 14:
If the SDK were tested by the same OS team that tested the image and the SDK bugs were included in the showstoppers for release then the delay would be unnecessary.  However, that is not the case currently.
If the SDK were tested by the same OS team that tested the image and the SDK bugs were included in the showstoppers for release then the delay would be unnecessary.  However, that is not the case currently.
-
 
-
Bob
 

Revision as of 14:40, 19 September 2010

Initial author: Bob Spencer
Interested parties: <place your name here>

This page describes the reasons for delaying the release of the SDK two weeks after the release of each MeeGo OS.

The SDK uses images from the MeeGo OS images. After MeeGo OS images are released the following must be done:

  • Ensure image is stable. Constant image instability (on device and in VM) has delayed current SDK updating for months.
  • Image content changes can impact QEMU. Example: Recent X version update broke both QEMU and Xephyr for x86 handhend and netbook.
  • Modify the handheld image with x86 kernel for QEMU.
  • Validate the image inside the SDK

Sometimes the MeeGo OS changes right up until release. Even minor changes require re-validation of the SDK. Due to the above tasks, it is safer for the release date for the SDK to be a couple of weeks after the release of the MeeGo OS image.

If the SDK were tested by the same OS team that tested the image and the SDK bugs were included in the showstoppers for release then the delay would be unnecessary. However, that is not the case currently.

Retrieved from "http://wiki.meego.com/SDK/Two_weeks_delay_proposal"
Personal tools