ANNOUNCE: New F11 XO-1build 115 Paraguay

[Bernie Innocenti]

This is a custom XO-1 OS image released by the Paraguay Educa technology
team for field testing in Caacupé:

 http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os115.img
 http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os115.crc
 http://people.sugarlabs.org/bernie/olpc/f11-xo1-py/os115.img.fs.zip

The system is a derivative of Stephen Parrish's excellent F11-XO1
series, frozen a few weeks ago to concentrate on stability and field
testing. Our short-term goal is to meet a release criteria of "no
regressions against build 801". Once this is done, we'll re-sync with
the latest improvements from our upstreams, F11-XO1.5 and F11-XO1.


== Changes relative to the previous release (OS65 Paraguay) ==

 * Removed all translations except English and Spanish to save space

 * 3G broadband support (untested, probably buggy)

 * Pick up all fixes from fedora-updates

 * Add patent-encumbered multimedia codecs (gstreamer-plugins-bad)


== Bugs fixed ==

 * Write activity doesn't let you cut, paste or delete selection
   http://bugs.sugarlabs.org/ticket/1817

 * Robot function in Speak does not work
   http://dev.laptop.org/ticket/10059

 * Graphics artifacts with some GMail backgrounds
   http://dev.laptop.org/ticket/10076

 * Black GTK buttons in Gnome and elsewhere
   http://dev.laptop.org/ticket/7830

 * Keyboard misconfigured if A/C is unplugged on first boot after update

 * NetworkManager crashes on suspend/resume
   (we have only a temporary work-around, tch is working on a solution)

 * Disable "automatic power management" even on first boot
   (this is a temporary work-around for wi-fi and XVideo bugs)

 * Activities updates from ASLO should go through local mirror
   http://trac.paraguayeduca.org/ticket/553


== Known bugs ==

Remaining bugs are summarized here:

 http://wiki.paraguayeduca.org/index.php/Devel/Builds/Todo

In particular, these are the remaining *known* regressions wrt the
old stable build from OLPC (OS801 Paraguay):

 * Record does not record sound
   http://bugs.sugarlabs.org/ticket/1244

 * NetworkManager crashes on resume from suspend
   We have an temporary workaround. See thread with subject
   "NetworkManager from fedora-updates-testing broken on
   F11-XO1" for full details.

Many more bugs are likely to be filed over the next days, as our testing
team works through their test plan.


== How to help testing ==

Feedback from the entire community is of course welcome as well. Bugs
belonging to upstream components should be filed in the usual trackers:

 * Sugar and activities: http://bugs.sugarlabs.org/
 * Fedora 11: http://bugzilla.redhat.com/
 * Drivers and OLPC customizations: http://dev.laptop.org/
 * Paraguay-specific bugs: http://trac.paraguayeduca.org/

If you're unsure where a bug belongs to, use the Paragauy Educa bug
tracker. Please, always cc me so I can keep the status summary updated.

We're unlikely to dedicate much attention to bugs affecting Gnome and
obscure activities with no active maintainer, but it's good to stay
informed on what's broken anyway. For everything else, we'll do our
best, with the help of OLPC, Fedora, and Sugar Labs.


== How to join development ==

Build system source:
  http://git.paraguayeduca.org/gitweb/users/bernie/olpc-os-builder.git

Yum Repository of our custom RPMs:
  http://repo.paraguayeduca.org/f11-xo1-py/i386/os/

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/

[IAEP] ANNOUNCE: New F11 XO-1build 115 Paraguay

[Martin Langhoff]

On Fri, Mar 26, 2010 at 6:47 PM, Bernie Innocenti <bernie(a)codewiz.org&gt; wrote:
>  Our short-term goal is to meet a release criteria of "no
>  regressions against build 801". Once this is done, we'll re-sync with
>  the latest improvements from our upstreams, F11-XO1.5 and F11-XO1. 
Bravo. To Stephen, to all the ParaguayEduca folks pushing for this. To you.

cheers,



m
-- 
 martin.langhoff(a)gmail.com
 martin(a)laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

[Mikus Grinbergs]

In my opinion, the name selected for this Paraguay build can create
quite a bit of confusion.

It used to be possible to distinguish within current development of
F11-based builds by their naming -- 11 (or thereabouts) from Parrish for
the XO-1, 67 (or thereabouts) from Innocenti for the XO-1, 116 (or
thereabouts) from Ball for the XO-1.5.  [64 and 200 were signed - so
somewhat "outsiders".]

Now every mention of "115" will have to be qualified "-- I mean the one
focused for Paraguay"" versus "-- I mean the one for general XO-1.5
testing".

Bah,  mikus

[Yioryos Asprobounitis]

I'll go with Mikus on that.
With at least 3 development streams some qualifier is needed in the naming. eg
os115x1/os115x15/os115py

--- On Fri, 3/26/10, Mikus Grinbergs <mikus(a)bga.com&gt; wrote:

>  From: Mikus Grinbergs <mikus(a)bga.com&gt;
>  Subject: Re: ANNOUNCE: New F11 XO-1build 115 Paraguay
>  To: "Bernie Innocenti" <bernie(a)codewiz.org&gt;
>  Cc: "OLPC Devel" <devel(a)lists.laptop.org&gt;, "Fedora OLPC List"
> <fedora-olpc-list(a)redhat.com&gt;
>  Date: Friday, March 26, 2010, 7:38 PM
>  In my opinion, the name selected for
>  this Paraguay build can create
>  quite a bit of confusion.
>  
>  It used to be possible to distinguish within current
>  development of
>  F11-based builds by their naming -- 11 (or thereabouts)
>  from Parrish for
>  the XO-1, 67 (or thereabouts) from Innocenti for the XO-1,
>  116 (or
>  thereabouts) from Ball for the XO-1.5.  [64 and 200
>  were signed - so
>  somewhat "outsiders".]
>  
>  Now every mention of "115" will have to be qualified "-- I
>  mean the one
>  focused for Paraguay"" versus "-- I mean the one for
>  general XO-1.5
>  testing".
>  
>  Bah,  mikus
>  
>  _______________________________________________
>  olpc mailing list
>  olpc(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/olpc
>

[Martin Langhoff]

On Sat, Mar 27, 2010 at 7:58 AM, Yioryos Asprobounitis
<mavrothal(a)yahoo.com&gt; wrote:
>  I'll go with Mikus on that.
>  With at least 3 development streams some qualifier is needed in the naming. eg
> os115x1/os115x15/os115py 
+1 -- and remember to keep it all 8.3 :-)

cheers,


m
-- 
 martin.langhoff(a)gmail.com
 martin(a)laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

[Bernie Innocenti]

On Sat, 2010-03-27 at 13:44 +0100, Martin Langhoff wrote:
>  On Sat, Mar 27, 2010 at 7:58 AM, Yioryos Asprobounitis
>  <mavrothal(a)yahoo.com&gt; wrote:
>  > I'll go with Mikus on that.
>  > With at least 3 development streams some qualifier is needed in the naming. eg
> os115x1/os115x15/os115py
>  
>  +1 -- and remember to keep it all 8.3 :-) 
Done: the next image will be called something like "os117py.img"


I've always wondered why the XO builds don't have a real name. Everyone
seems to generically refer to them as "OS". For some time, I've been
calling it "xoos", then I realized I was the only one and gave up.

Analogously, f11-xo1 is hardly pronounceable and f11-xo1-py is even
worse. Where's Steve Jobs when we need him?

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/