Accelerating the release of Kernel related bug fixes

The Problem Being Addressed

Several customers have complained that Solaris Kernel related bug fixes take too long to release. This includes bug fixes in the Kernel Update itself and in any patch which has a dependency on a Kernel Update which has not yet been released.

The Process to Address the Problem

A comprehensive SunSigma quality review of the Kernel Update process has resulted in a proposal to dramatically accelerate the release of Kernel related bug fixes without compromising quality.

The Current Kernel Update Train model
  • The Kernel Update (KU) process uses a Train release model. That is:
  • Releases are scheduled for set intervals, typically 6-8 weeks apart
  • Bug fixes which are ready before the KU train leaves will be included
  • Bug fixes which are not ready when the KU train leaves must wait for the next KU train
  • Each KU goes through a dedicated and largely serial test process which was developed prior to the current standardized patch test and release process.
(See sys-and-perf-test for an overview of the standard Solaris patch test process.)

The Proposed Solution
  • Kernel patches will be created more frequently, as often as once every 2 weeks, if required.
  • Kernel patches will continue to have the same structure, look and feel that they do today.
  • Kernel patches will leverage the effective and efficient standard creation, test, and release process which is used for all other Solaris patches, while retaining those areas of Kernel specific testing which add value.
For example, instead of one Kernel Update being produced every 8 weeks and containing, say, 15 new bug fixes, there may be three or four Kernel patch revisions released in the same timeframe, each containing just 3 or 4 new bug fixes. The result is exactly the same: 15 Kernel related bug fixes released in an 8 week period.

The Schedule
  • The new process will be rolled out and the first patches will be available to customers before the end of 2003.
  • The Advantages of Kernel Patches for Customers
  • Much faster time-to-release for Kernel related bug fixes.
  • Eliminates the need for Supplemental Kernel Updates (SKUs).
  • Each Kernel patch revision contains less code change.
Customers will see Kernel patches being released more frequently. Customers are not expected to install every Kernel patch revision. Instead, customers can check if a particular revision contains any fixes which they want – for example, a security fix - and decide on a case by case basis whether to install it.

Many customers have a regular maintenance cycle. Often this maintenance cycle is timed to coincide with a Kernel Update release. The more frequent release of Kernel patches will give customers increased flexibility in deciding when to start a maintenance cycle, so that it can be optimized to match their business cycle.
 
Login Required

You must login and have a valid contract to access Sun's Premium content which includes:

  • Sun Alerts
  • Bugs
  • Patches
  • Solutions
  • White Papers
  • Documentation
  • Support Knowledge

Login Required

You must login and have a valid contract to access Sun's contracted features

Access Legend:

(Login to access)   Sun Contracted Content
(Login to access)   Sun Contracted Feature

Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.

 
Contact About Sun News & Events Employment Site Map Privacy Terms of Use Trademarks Copyright Sun Microsystems, Inc. | SunSolve Version 7.4.0 #1