[lsb-discuss] LSB conference call agenda (Tuesday, January 30, 11am ET) (and LSB 3.1 Update 1 status update)

[Ian Murdock]

Dial in details are unchanged:
Toll Free Number: 877-954-0722 (United States)
Toll Number: 203-566-1295 (International)
Participant passcode available on request

(The participant password is the same as before. If you don't already
know it and want to join, feel free to drop me a note.)

Agenda:

* LSB 3.1 Update 1 progress update

For those who haven't attended the past few calls, here's the current
status (please provide updates if appropriate):

* All beta packages are built now, but we're missing S390 and S390X and
Debian packages. The Debian package support has been added to the build
process, so we will have Debian packages when we do the final build.
Marvin is looking for an S390X build host (question: can we
build the S390 test packages on S390X)? [Marvin Heffler owns these.]

* RAS is delivering the beta build of the Distribution Testkit today.
RPMs for IA-32, IA-64, AMD64, PPC32 will be provided. We will need
to do builds for PPC64, S390, and S390X as well as Debian packages.
[RAS owns this. Jeff or Marvin will build for PPC64. Marvin
will build for S390 and S390X. Jeff will help with Debian support.]

* Final builds of the SDK and Application Testkit need to be produced.
For the tarball versions, we need to ensure the same install
process is used that the Distribution Testkit uses. [Jeff owns this.]

* APT and yum repository generation support is ready. All we need
now are the final builds of the beta packages. As a reminder, our
goal here is to have APT and yum equivalents for the Distribution
Testkit, Application Testkit, and SDK tarballs. [Jeff owns this.]

* We need to prepare whatever errata etc. are needed. [Mats owns this.]

* Once we have our deliverables (tarball, APT repo, and yum repo of
Distribution Testkit, Application Testkit, and SDK), we will update
the LSB Downloads page and announce the beta release. [I own
the Downloads page, Mats owns the release notes, announcement, etc.]

* We will work with key distribution vendors to test the beta, with a
goal of completing the beta period and releasing the final LSB 3.1 by
mid-February. Note that distros and apps will continue to certify to
LSB 3.1, *not* LSB 3.1 Update 1, as per our previously discussed policy [1]
(looks like I still need to add that to the wiki--I'll do that today).

To keep everything together, the policy is this:

  From time to time, the LSB workgroup may issue updates to the
  LSB standard.

  From the point of view of certified distributions and applications,
  the original version and the update shall be equivalent (i.e.,
  distributions and applications will certify to LSB 3.1, not LSB 3.1
  Update 1). In other words, recertification to an update is unnecessary.

  To achieve this, no change will be made in an update unless the
  change results in all certified implementations remaining complaint
  after it is made--or, put another way,
  the original version is FORWARD COMPATIBLE with all of its updates.

[1] http://lists.freestandards.org/pipermail/lsb-discuss/2006-November/003225.html

-ian
-- 
Ian Murdock
317-863-2590
http://ianmurdock.com/

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