Project Plan for LSB 3.1 Release
The tracking bug for the LSB 3.1 complete release is bug 1092.
Since the Core specification is in the process of being adopted by ISO, we have tight, inflexible, deadlines associated with that component. As a result, it is proposed that the 3.1 release be staged, and not require all parts of the spec to be updated at once. The modules are hyperlinked to the appropriate tracking bug.
|Core||bug 866||RC1 by 9/30/05, to ISO by 10/31/05|
|Graphics||bug 1090||RC1 by 1/15/2006, GA by 2/15/06|
|C++||bug 1091||RC1 by 1/15/2006, GA by 2/15/06|
Once a module is released, it must be regarded as frozen until all the other modules have caught up with it. No changes can be applied. If the specdb is updated after one module is released, that released module will not get the db updates published; bear this in mind when planning or contemplating a db change!
Once all the parts have moved to 3.1, the product standards used for certification can be upgraded to refer to the 3.1 set.
In the interim, the product standards for a 3.0 certification require LSB xxx 3.0 "and subsequent minor revisions". As soon as any module is finalized, it becomes the base against which conformance is measured.
Additonally, once the Core specification has gone to ISO, changes to it are necessarily a lot more complex. Do not assume that anything can get added, subtracted or otherwise altered in the Core document for another year!
The initial desktop release is intended to align with the full 3.1 release, and tools which need to be "desktop aware" will be so for the 3.1 release, with the default being to not check or use the desktop modules so that they can be used for base 3.x certification, but with options to turn on desktop. The checklist for the desktop release in included below in addition to the base release.
Remainder of the Release
Once the specification has all reached the 3.1 level, all of the other parts (tests, application battery, sample implementation, etc) can be brought up to the same level. The tracking bugs for these parts are:
- bug 1093 - runtime tests (incl. libchk)
- bug 1102 - application battery
- bug 1103 - sample implementation
- bug 1104 - application checks (appchk, pkgchk, archk)
- bug 1105 - development environment
The current plan for releasing the test suites and development environment is as follows:
- RC1 - 01/15/2006
- GA - 02/15/2006
There are several bugs still targetted at 3.1 that do not have a clear resolution. If the bugs listed below fail to progress within the timeframes given above, they will be moved to 4.0 (see ProjectPlan40).
- bug 862 No specification of 27 C++ interfaces
- bug 1009 zcat: is the command in or out?
- bug 1036 Does amd64 spec need to talk about medium model?
- bug 1089 Are headers complete enough?
LSB 3.1 Desktop Completion Checklist
|gtk Test Suite||n/a|
|qt Test Suite||n/a|
|graphics-ext Test Suite||n/a|
|xml Test Suite||n/a|
LSB 3.1 Completion Checklist
|Core Release Notes||X||n/a||n/a||n/a||n/a||n/a||n/a||n/a|
|Core SC Vote||X||X||X||X||X||X||X||X|
To add comments to this page, click on [wiki:ProjectPlan31/Comments User Comments] and select edit.