From The Linux Foundation
Jump to: navigation, search

NOTE: This is the roadmap for LSB 3.2 - kept here for informational purposes.
Please check the LSB roadmap for current information.

LSB 3.2 (Sept 2007)

Mostly unchanged from LSB 3.0 and 3.1. LSB 3.x is based on the ABI of glibc 2.3.4. glibc 2.4 is deferred to LSB 4.0 because Debian and derivatives are not yet based on it. Some interfaces are being added, but only those that are already widely deployed via the Linux distributions are candidates.

We are also conducting a review of symbols that were previously in the LSB (during 1.x and/or 2.x) and have been removed but are still in widespread use (i.e., are still best practice). Where practical, these symbols will be readded to the LSB in 3.2 and waivers will be granted so that LSB 3.0 and 3.1 applications that wish to use them may do so. The primary consideration here are third party libraries such as FLEXlm that many ISVs use but cannot change to make their applications compliant.

In LSB 3.1, compliant applications depend on a single metapackage called 'lsb', so an LSB compliant runtime should provide that metapackage and provide all the required components when it gets installed. In LSB 3.2, we'll allow applications to only depend on the subset of the LSB they require (e.g., lsb-core). This will allow LSB applications that do not require the desktop components to be installed without pulling in the desktop components via the 'lsb' dependency.
Mostly unchanged from LSB 3.0 and 3.1. LSB 3.x is based on the ABI of GCC 3.4.3 libstdc++ (version 6). GCC 4.x is best practice now; however, it (currently) has the same major version of libstdc++ as GCC 3.4.
Will be added to 3.2. Need to find common denominator across the major distros.
Will be added to 3.2. Need to find common denominator across the major distros.
Whereas LSB 3.1 stopped at the desktop toolkits (GTK and Qt), LSB 3.2 aims to "move up the stack" and incorporate more of GNOME and KDE. Four specifications (Desktop entry, Icon theme, [http:// Menu], and Desktop base directory) are in the process of being added to 3.2 (all are already best practice). xdg-utils (aka Portland), which provides a unified command line interface to these standards, is also being considered, but their inclusion in 3.2 depends entirely on whether the distros include them in a service pack release of their current generation (RHEL 5, SLES 10, etc.). In any event, we should consider adding xdg-utils to the LSB SDK, since they can be bundled wi th the application to provide the necessary functionality. We should also revisit Qt 4. Whether this is a 3.2 candidate depends entirely on whether Red Hat ships it in RHEL 5.

Printing support in 3.2 is focused on making it possible for printer manufacturers to supply drivers that expose the full functionality of their printers and that work on any Linux distribution, as well as providing ISVs the facilities they need to access that full functionality. To achieve this, we are focused on two broad areas in 3.2: Driver support and application interfaces. On the driver side, we are adding CUPS Raster, OpenPrinting Vector and IJS, all of which are best practice (the latter two by virtue of Ghostscript integration). Also, the OpenPrinting workgroup is putting together an extension to the FHS defining standard locations in the file systems for printer drivers and filters. Whether this is a 3.2 candidate depends on whether or not the distros include it in a service pack release of their current generation products (RHEL 5, SLES 10, etc.). This is believed to be realistic because it will be possible to implement the standard in a non disruptive fashion using a symlink tree. On the application
side, a subset of the CUPS convenience API is being added. See LSB 3.2 pmap.
LSB 3.2 will focus on device level standards (e.g., ALSA, libao). LSB 4.0 will focus on the higher level multimedia frameworks (e.g., GStreamer, Helix). The LF is forming a Multimedia workgroup to lead this work. Details forthcoming.
OpenI18n is being merged into the LSB beginning with LSB 3.2. Details forthcoming.
AT-SPI (module libspi, LSB Optional with conformance testing); Keyboard I/O (a performance specification which adds no new libraries).
Font management 
Can we define a common set of fonts required to be available on LSB compliant desktops, so that a document created on one LSB compliant system looks the same on another LSB compliant system? Beyond this, the distros are interested in getting out of the font business. This is a larger issue than the LSB--we want a document created e.g. on Windows to look the same on Linux too. L

ooking into working with OASIS,, and other organizations to help address this action item.


November 2006

  • Alpha version of RAS Test Execution Framework (TEF) released. The TEF is a web based frontend to lsb-autotest which allows tests to be run in the browser and will facilitate seamless integration with the LSB certification system as well as enhanced reporting and visualization of test results (click on a test failure to see the spec assertion violated, the test case that failed, etc.).

December 2006

  • LSB f2f (LSB 3.2 roadmap and timeline finalized, tasks assigned, etc.)
  • Spec/test "interfaces" finalized (e.g., markup for annotating spec assertions, linking tests to those assertions, etc.)
  • Spec/test development begins
  • lsb-autotest replaces lsb-runtime-tests tarball as the official "LSB Runtime Testkit" used to test distros for LSB compliance (individual test packages will still be available, as they are today for the lsb-runtime-tests tarball)
  • LSB Application Testkit released with new and improved appchk tool
  • New framework alpha (prototype)

January 2007

  • LSB SI VMware images released

March 2007

  • LSB SDK expanded with packaging helpers (RPM .spec generators, alien, APT/yum repo creators, etc.)

Q2 2007

  • New framework beta

July 2007

  • Spec/test development end
  • LSB 3.2 freeze (specs and tests are final but unintegrated into the "complete" LSB--distros can begin compliance testing/certification process now in anticipation of announcing LSB 3.2 certification immediately with LSB 3.2 release)

August 2007

  • LSB 3.2 Release Candidate, public comment period (specs and tests are fully integrated now)

September 2007

  • New framework in production
  • LSB 3.2 final