sugar-core for Update.1 - was: [sugar] What's left for Update.1

2008-02-08 Thread Simon Schampijer
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 -

Re: [sugar] What's left for Update.1

2008-02-02 Thread Dennis Gilmore
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 asking

Re: [sugar] What's left for Update.1

2008-02-02 Thread Walter Bender
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 - to fix

Re: [sugar] What's left for Update.1

2008-02-02 Thread Mitch Bradley
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

Fontconfig Bug (#6046) [WAS: Re: [sugar] What's left for Update.1]

2008-02-02 Thread Sayamindu Dasgupta
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: note