Status Update

[Richard Purdie <richard.purdie@linuxfoundation.org>]

In summary its been a fairly quiet week, there are number of different
holidays in different geos.

Pending Patches
===============

There has been a steady stream of 1.5 patches starting to appear. With
Saul's help these have been tested on the autobuilder and then many have
been merged into master. There were some race issues with one of the
sstate performance improvements but that is now resolved as far as I
know. We're making slow/steady progress on gcc 4.8.

1.5 planning is well underway now and some people are starting to work
on the implementation of features.

1.4.1
=====

Paul is going to maintain the 1.4 series. He's already queued up several
of the fixes that didn't make 1.4 and these are now undergoing testing
on the autobuilder. If anyone has any changes to propose for 1.4.1, now
is the time. We're not looking at features or upgrades but will consider
bug fixes.

1.3.2
=====

I've merged a lot of queued changes that Ross prepared for 1.3.2 and
this is now undergoing testing.

Python 3
========

I've been asked when bitbake will work under python3 several times now.
The first question is which python 3 as there are big differences
between them. I'm still not sure which python 3.X we'd end up wanting to
target.

I've done a bit of research and the changes we need to make are mostly
of the annoying kind. I have had bitbake build a few things (e.g.
pseudo-native) with a hacked up bitbake and metadata. The current
roadblock is the oe.types functionality and I think I'll need Chris'
help to fix this since some functionality it relies on was removed in
3.x.

I've a series I'll send out which deals with the simple issues. 

There are several cases we'll have to put in "hacky" code to make things
work for both py2 and py3, the most annoying being octal file
permissions. There is no syntax which works in both so we're facing
having to write them in hexidecimal if we want both to work. When I have
spare time I'll continue to work on it and try and get a more complete
build working.

Cheers,

Richard