[Testing] Build 472 - testing
rchokshi at marvell.com
Sun Jul 1 13:15:44 EDT 2007
True. Please treat our suggestions of builds only as recommendations.
The final decision of which build should be used for the major
milestones should come from within OLPC based on the accomplishments
planned for that milestone. This is the model we usually follow with
most of our other customers/projects as well.
From: testing-bounces at lists.laptop.org
[mailto:testing-bounces at lists.laptop.org] On Behalf Of Michail Bletsas
Sent: Sunday, July 01, 2007 6:11 AM
To: Dan Williams
Cc: testing at laptop.org; Kim Quirk; OLPC Developer's List;
testing-bounces at lists.laptop.org
Subject: Re: [Testing] Build 472 - testing
No we don't....
Dan Williams <dcbw at redhat.com>
Sent by: testing-bounces at lists.laptop.org
06/30/2007 11:37 PM
Kim Quirk <kim.quirk at gmail.com>
testing at laptop.org, "OLPC Developer's List" <devel at laptop.org>
Re: [Testing] Build 472 - testing
On Sat, 2007-06-30 at 08:10 -0400, Kim Quirk wrote:
> It looks like we may need/want to get the latest Marvell firmware and
> all known flag day updates into the build on Monday (if possible). At
> some point we just have to take the hit and ask everyone to upgrade,
> laptops and servers.
> As you mention, Dan, we need to do this in Cambridge first... so maybe
> this should be in Monday's build. I know we have the Marvell firmware
> (or can get it). Is there anything outstanding that we are still
> waiting on to have this flag day?
We need to get Ronak's sign-off on any firmware that we plan to put in
public builds. That can take a few days, though sometimes it's quick.
> Is there a reason NOT to do this as soon as possible?
> On 6/30/07, Dan Williams <dcbw at redhat.com> wrote:
> On Fri, 2007-06-29 at 21:37 -0400, John (J5) Palmieri wrote:
> > On Fri, 2007-06-29 at 11:23 -0400, Kim Quirk wrote:
> > > Test Groups,
> > > Build 472 is available, but the biggest problem is that it
> doesn't get
> > > on the mesh or infrastructure AP. Some activities are
> working and
> > > there is more to see in the Journal than the previous
> > >
> > > I'm hoping that we can get another build today with the
> > > problem fixed since that would be important for our
> 'Release Candidate
> > > 1'. Today's milestone is to get to RC1 which has most of
> the basic
> > > functionality that was available in 406 builds. If we can
> get the mesh
> > > connecting again, that would be great!
> > >
> > > Test release notes:
> > > (Anyone can add notes about this release page -- please
> > I couldn't fix the mesh issues with the current
> NetworkManager so I have
> > backtracked to an earlier working version in build478. This
> one gets on
> > the mesh and also on AP points.
> So thinking about it again, we don't expect the new svn2621 NM
> bits to
> work with any existing mesh networks because the server
> software and
> hardware needs to change.
> We have to have a flag day in Cambridge too before we can get
> the new NM
> automeshing bits, because the new bits aren't compatible with
> the old
> bits on the server side.
Testing mailing list
Testing at lists.laptop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel