On Wed, 2007-10-03 at 10:15 +0200, Tollef Fog Heen wrote: > * Ben Collins > > | On Mon, 2007-10-01 at 15:29 -0700, Matt Zimmerman wrote: > | > On Mon, Oct 01, 2007 at 11:11:27PM +0100, Colin Watson wrote: > | > > On Mon, Oct 01, 2007 at 12:00:11PM -0700, Johnson, Charles F wrote: > | > > > Did the upload, where the missing psb.ko module was included in the > lpia > | > > > kernel, occur ?? > | > > > | > > No, it's still only in git. The best group to contact about this would > | > > be the Ubuntu kernel team. > | > > | > Escalating to Ben, as this bug was reported 5 days ago and is a severe > | > blocker for mobile builds. > | > > | > > https://bugs.edge.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/147792 > | > | We planned an upload for Friday, but that was delayed over till today. > > It's quite important that when this happens, you tell us so we can > communicate this to Intel and the mobile list. > > [...] > > | Perhaps Amit can get you a build of the flavor you need, that can be > | wedged into the mobile build for immediate testing. Would this get > | things going until the upload? > > We have an explicit policy of having the daily images be built from > the archive and nothing else, I would not want this to change. > > Also, the problem here isn't that I can't work around psb.ko being > broken, but rather that the dailies have been broken for quite a while > due to the kernel being uploaded too seldomly. At UDS, I'd like us to > discuss how we can prevent this problem in the future.
We explicitly decided to do this, and in part were forced into it. We have about an 8 day window to do uploads in a 2-week (milestone-to-milestone) period. Usually that allows us one upload. every milestone. A lot of projects are expecting regular kernel side changes: server team (xen, apparmor, etc), sparc port, IHV's, UME...and the list keeps expanding. Everyone wants a little bit fixed/added/developed in each kernel upload. Coordinating that so that each project benefits in every upload is a task in itself. I think the best way to overcome this is to have a set kernel development schedule for the release, with relative dates bound by milestones, freezes, and other dates on the main release schedule. I think keeping the projects informed about what they can expect from the kernel, and how they need to interact with the kernel team for their schedules, would benefit all. I already have a planned UDS agenda item for this. The UME project's input would be greatly appreciated at this meeting. -- Ubuntu : http://www.ubuntu.com/ Linux1394: http://wiki.linux1394.org/ SwissDisk: http://www.swissdisk.com/ -- Ubuntu-mobile mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
