[lsb-discuss] LSB 3.2 timeline

Ian Murdock imurdock at imurdock.com
Tue Nov 7 14:50:57 PST 2006

On 11/3/06, Dirk Hohndel <dirk.hohndel at intel.com> wrote:
> On 11/3/06 9:26 AM, "Banginwar, Rajesh" <rajesh.banginwar at intel.com> wrote:
> >>
> >> So I would like to step back with the existing versioning
> >> proposals for the
> >> time being. Please keep your solution for your current needs
> >> (as if this
> >> discussion did not happen). I hope to be back some day later after we
> >> investigate the topic in detail globally for the entire DB.
> >
> > If we really plan on having this done for LSB 3.2 (May 2007), we should
> > put some timeline for this to happen. Say, something like the DB schema
> > can not be changed after LSB f/f or we at least have a final proposal by
> > then.
> I think this is something we definitely should tackle for 3.2 (so that we
> have the kinks figured out and can have a solid solution for 4.0). Delaying
> the issue only seems to make it harder to solve.

Agreed. The current plan is to have the new framework in production
by LSB 3.2, and for all new development to take place in the new
framework. Since that framework isn't ready yet, we need to make sure
we at least agree on the "interfaces" now--i.e., markup for the
specification text and tests to do the linkage when the new system is
in place. The RAS team is actively working on this. And, of course, if
we intend to have the new framework in production by mid-2007, we
need to bake in lead times for finalizing the schema and
many other things, to make sure everything gets adequate testing.

> Ian, do you have a time line in mind?

Yes. Here's my current working LSB 3.2 timeline. Comments welcome. The
plan is to finalize this at the f2f, but let's try to hammer it out on
the list in advance of that.

Nov 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.).

Dec 2006   LSB f2f

           - LSB roadmap finalized and tasks assigned

           For an idea of what I'm looking for here, take
           a look at the LSB Printing roadmap, finalized
           at the FSG Printing Summit October 23-25, 2006:


Dec 2006   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)

Dec 2006   LSB Application Testkit released with new and improved
           appchk tool

Dec 2006   Spec/test "interfaces" finalized (e.g., markup for annotating
           spec assertions, linking tests to those assertions, etc.)

Dec 2006   New framework alpha (prototype)

Dec 2006 - Spec/test development
Apr 2007

Jan 2007   LSB SI VMware images released

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

Q2 2007    New framework beta

Apr 2007   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)

May 2007   LSB 3.2 Release Candidate, public comment period

           (specs and tests are fully integrated now)

Jun 2007   New framework in production

Jun 2007   LSB 3.2 final

Ian Murdock

"Don't look back--something might be gaining on you." --Satchel Paige

More information about the lsb-discuss mailing list