LSB conf call notes for 2008-10-08
Submitted by licquia on Wed, 10/15/2008 - 13:30.
Printer-friendly versionWichmann, Darren Davis, Russ Herrold, Robert Schweikert, Jesper
Thomschultz, Kay Tate, Jiri Dluhos, Ted Tso, Alexey Khoroshilov
4.0 beta. Alexey: SI tools may be totally overlooked. Jeff: tested?
Alexey: against 3.2, not necessarily 4.0. Jeff: will pull in manually
if necessary. Ted: will we have to integrate the SI tools with the SI?
Alexey: yes, have made a RPM of the SI tarball. Ted: should merge the
4.0 SI with the 4.0 SI tools and do a check to make sure everything
works. Should probably do tests on our side as well. Jeff: can Alexey
do one set, and I do other? Alexey: yes. Have built a RPM based on the
4.0 SI from yesterday on one architecture.
Mats: tagging? We might have a slight moving target, with commits going
in during the autobuilds; fixes being checked in during the builds.
Ted: not a build from scratch? Mats: a build from scratch, but each
build ends at a certain point. Jeff: probably should have tagged before
doing the builds. Ted: delay? Jeff: 1 day. Ted: with SI and other
stuff, will this actually delay anything. Jeff: were their commits last
night? Mats: there were. Stew: core-test, appchk-perl and -python.
Mats: dtk-manager. Ted: what needs to be built? Jeff: depends on build
order. Stew: all my changes were accompanied with build version bumps,
so should be obvious. Mats: maybe should redo the builds; the
dtk-manager fix. Jeff: could also add SI tools to builds. Ted: full
build? That could add a day and a half. Jeff: depending on how long
the SI tools integration takes. Ted: need to get the beta out this week
if we can. Worried that much more delay would cut into beta time.
Jeff: plan, then, is to use the builds finishing up, rebuild
dtk-manager, do si tools and app-checker integration, and release with
that. Mats: do we need si and si-tools integration? Ted: if it takes
too long, could decouple.
Jeff: attention? Brian: press or specific? Jeff: specific. Russ: post
to public bug trackers and lists. Jiri: Novell knows; keeps an eye on
things. Brian: maybe talk to Mike Wooster; has the best ISV list?
Also, do a distro announcement on LDN. Jeff: can do a post to
distributions list. Ted: can also use contacts at Red Hat and Ubuntu.
Biggest thing to do is draft release notes, specifically what's new.
Also, ISV announcement should be targeted at their needs. Mike has
volunteered to follow up with ISVs as well. Probably busy until early
next week due to End User Summit. Maybe abstract the release notes into
three docs: one eah for distros, ISV, and more general press release.
Brian: could help with that. When? Jeff: today? Brian: could have
some of this tomorrow if the release notes that are done today. Ted:
Navigator shows 14 apps that will move into certification, 75 or so very
close, so that would be a good thing to point out in the press release.
Russ: Certification? Ted: this will be key to do next year. Russ:
going through ChipHopper; if the LSB cert is part of ChipHopper, that
should be made more clear. Want to work more closely with companies
with ISV teams like ChipHopper. Russ: do we want to get those figured
out? Ted: is happening. Agree that we should do this. Brian: should
we schedule Mike for working on LSB stuff after the Summit? Ted: yes.

