On 10 November 2010 21:14, Michael Hope <michael.h...@linaro.org> wrote: > On Thu, Nov 11, 2010 at 6:24 AM, Peter Maydell <peter.mayd...@linaro.org> > wrote: >> I've had a look at these and fleshed them out mostly. >> There are some oddities: >> * why are maintain-beagle-models and qemu-continuous-integration >> under "tr-toolchain-consolidate-qemu" and not "tr-toolchain-integration" ? > > I think consolidation is an on-going process (hence the 'maintain' > blueprint) and that CI will help the process.
Hmm. To me consolidation is all about pushing patches upstream (and we have a different blueprint for pushing omap patches upstream); I intended maintain-beagle-models to cover the stuff we wouldn't be doing if we didn't want to keep the qemu beagle model working as a platform for testing and demoing Linaro images. That's what I thought "integration" was for... >> * should sound-support really be a "Medium" ? I thought we decided at UDS >> that it wasn't all that important > > It's medium compared to the other blueprints in it's group. You're using these as relative and not absolute priority levels? That's kind of confusing... > Think of > it as a scheduling thing - low priority but low effort (for the simple > playback case at least) bumps it up to a medium. > >> and I haven't worried too much about ones which are clearly far enough >> down the list that we're not going to get to them in this six month cycle. > > OK, can you mark them as such then so others know? Update the > whiteboard with a note and add the line 'Tags: community' to the end > of the whiteboard. OK. ...audio was in this group, by the way. -- PMM _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
