[Angstrom-devel] Release planning

[Marcin Juszkiewicz]

Dnia poniedziałek, 7 maja 2007, Koen Kooi napisał:

> The images and feeds are starting to look pretty good, so lets look at
> what needs to get done before releasing:

> * open bugs: http://bugs.openembedded.org/showdependencytree.cgi?id=1573 

#1691 should be easy for someone who has sl-cxx00 Zaurus - all use same 
chip

> * machine mentors: people need to put there names down in the wiki and
> document the issues in bugzilla (like Rolf is doing for Collie)

I can co-mentor Tosa, c7x0, collie. But will not test integrated WiFi in 
tosa as it suxx too much. I can test does it suspend/resume properly with 
those drives loaded.

> * distill a list of 'supported' and 'untested'[1] machines
> * distill a list of 'supported' and 'untested'[1] image targets

I want to put progear into 'untested' list of machines as I am the only 
owner of that device within devteam and I lack time to test images on it. 
Anyway default Ångström X11 images are not usable due to lack of 
touchscreen driver (mutouch) and progear also require xorg.conf properly 
populated to have calibrated touchscreen.

BTW - 'untested' is OK for me.

> * wait for the bluez 3.10 release[2][3] and fix bluetooth in the
> 'supported' image targets. 

> * Write installation docs and put them on the website

Put them in wiki, let people extend them and finally machine mentor will 
move it into website.

> * Work out feed structure and management

> * anything else?

* Policy for feed updates - who can, how to make it, when make it.
* Snapshot of OE database, recipes tarball, branch in OE.
* Archive sources, put on web (if space allow), place offer.
* Write release announcements, send them to websites few days before 
release.
* Finish website. We need informations:
- what is Ångström
- why was created
- who created it (OE, OZ, Familiar, other buzzwords)
- what machines are supported (and which are not tested fully)
- who use it (companies, known developers)
- which environments are supported?

This will be first release so it need good PR job done. We cannot release 
something which will break out-of-box instead of working.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

         Real programmers don't document.
         If it was hard to write, it should be hard to understand.