Things I find worth looking at for update.1 (at least the things that
are in joyride or we have a fix for):
* In joyride and tested
- #6046 Browse is slow (rainbow.noarch 0:0.7.9-1.olpc2,
fontconfig.i386 0:2.4.2-5.olpc2)
- #5904 Grouping in mesh view: sugar-0.75.11-2.olpc2.i386.rpm
- #4781
On 2/4/08, Sayamindu Dasgupta <[EMAIL PROTECTED]> wrote:
> On Feb 4, 2008 10:31 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> > On Feb 4, 2008 11:50 AM, Sayamindu Dasgupta <[EMAIL PROTECTED]> wrote:
> > > 2008/2/4 Kim Quirk <[EMAIL PROTECTED]>:
>
> <..snipped>
>
> >
> > > For translations, I wo
On Feb 4, 2008 10:31 PM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> On Feb 4, 2008 11:50 AM, Sayamindu Dasgupta <[EMAIL PROTECTED]> wrote:
> > 2008/2/4 Kim Quirk <[EMAIL PROTECTED]>:
<..snipped>
>
> > For translations, I would also probably push Mongolian in, along with
> > Spanish. I am curre
On Feb 4, 2008 11:50 AM, Sayamindu Dasgupta <[EMAIL PROTECTED]> wrote:
> 2008/2/4 Kim Quirk <[EMAIL PROTECTED]>:
> > I think this is way too much stuff for Update.1. We are in code freeze. We
> > have items 1 and 2 scheduled to go into RC2; I would suggest that we ONLY
> > pick up Spanish, where we
2008/2/4 Kim Quirk <[EMAIL PROTECTED]>:
> Jim,
> I think this is way too much stuff for Update.1. We are in code freeze. We
> have items 1 and 2 scheduled to go into RC2; I would suggest that we ONLY
> pick up Spanish, where we really fell short in the current build; I don't
> agree with holding up
Jim,
I think this is way too much stuff for Update.1. We are in code freeze. We
have items 1 and 2 scheduled to go into RC2; I would suggest that we ONLY
pick up Spanish, where we really fell short in the current build; I don't
agree with holding up this build for either 4 or 5, as this feels like
Hi,
On Feb 1, 2008 8:41 AM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> For comment and discussion, here are the showstoppers I know of for
> getting Update.1 finished. If you think there are others, please speak
> up now (and modify the subject line to start another thread).
>
> Activity developers:
I can make a q2d12 with the fix for 6291. The fix is extremely low risk
- just a change in one number that tells how far to search for
additional nodes in a partially-written block.
The only reason why I haven't made a q2d12 already is because I can't
get to the build server - the machine "lea
I agree. We shouldn't hold up Update.1 on issues we don't already have
resolutions in hand for. Now is the time for testing, not further
changes.
-walter
On 2/2/08, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> On Jan 31, 2008 10:11 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> > 2 - q2d11 OFW - t
On Jan 31, 2008 10:11 PM, Jim Gettys <[EMAIL PROTECTED]> wrote:
> 2 - q2d11 OFW - to fix battery problems
We'll need a q2d12 to fix #6291, or plan for a update.1.1 for
deployments like Mongolia where we need to multicast-update large
groups of machines.
> 4 - UI fix for registration with the sc
On Thursday 31 January 2008, Jim Gettys wrote:
> For comment and discussion, here are the showstoppers I know of for
> getting Update.1 finished. If you think there are others, please speak
> up now (and modify the subject line to start another thread).
>
> Activity developers: note we'll be askin
Jim Gettys wrote:
> I think we need to seriously discuss about possibly/probably being
> update.1 fodder is the "kids arrive at school in the morning" problem.
>
> 5 - Use of mesh in large, crowded environments
> If everyone arrives at school running local link and resumed quickly,
> the network
For comment and discussion, here are the showstoppers I know of for
getting Update.1 finished. If you think there are others, please speak
up now (and modify the subject line to start another thread).
Activity developers: note we'll be asking you to upload updated
activities to pick up all the re
13 matches
Mail list logo
