OpenZaurus 3.5.4.1 status update

OpenZaurus 3.5.4.1 is near to be released. Images was created and tested 
on all supported platforms (c7x0, akita, spitz/borzoi/terrier) and they 
work. Now the question is how to generate feeds for 3.5.4.1. 

First option is adding all packages from 3.5.4.1 to 3.5.4 feeds but then 
all !3.5.4.1 devices (collie, poodle, tosa) will get upgrades to newer 
glibc etc which I want to avoid as this is not tested. I do not want to 
have posts like 'I upgraded my working Zaurus and now it does not even 
boot' (some of you probably remember problems with r21 kernel on collie 
in OZ 3.5.3 times).

Second way is generating new feeds for 3.5.4.1 - this will take few days 
and some stuff probably will not build.

But I also had plans for !3.5.4.1 devices (all 2.4 powered) to give people 
images with all updates (so we do not get posts like 'I flashed my tosa 
with 3.5.4 and half of keyboard does not work! OZ is shit' when it can be 
easily resolved with 'ipkg update; ipkg upgrade' as we fixed keymaps 
after release. Those images would be released as 3.5.4.2 but have to use 
3.5.4 (arm/arm5) feeds rather then 3.5.4.1 (arm5 only).

Or I can build 3.5.4.1 feeds for arm so all machines will use them - and 
thats looks like best option.

So current situation looks like this:

- images are working on all platforms (thx to Mickeyl, CoreDump, RP and 
few other devels/users for testing)
- feeds need to be built (optimised for arm not armv5)
- images will be rebuilt from feeds and tested
- release of 3.5.4.1

I think that this will take about 1-2 weeks to get feed built.

Any opinions?

-- 
JID: hrw-jabber.org
Palmtop: Sharp Zaurus C760
OpenEmbedded/OpenZaurus developer

              whats mean ubuntu?
              it's african word for "can't configure debian"