Those are only the session blueprints for the scheduler. Once we've captured all the info we need (broken each up into individual feature blueprints that would satisfy the requirements), those will go away (be marked "implemented"). I don't see how we get around it (well, I suppose we could keep our planning manual and ad hoc, but I wanted to make sure folks could use the scheduler to make sure they were able to attend other important sessions).
cheers, Jesse On Wed, Oct 5, 2011 at 9:14 AM, Christian Robottom Reis <k...@linaro.org> wrote: > On Tue, Oct 04, 2011 at 12:17:11PM +0300, Ilias Biris wrote: >> * Benchmarking: >> https://linaro-public.papyrs.com/public/4143/GWG2011-BENCHMARK-DASHBOARD, >> also >> in Launchpad >> https://blueprints.launchpad.net/linaro-graphics-misc/+spec/linaro-gfxmm-benchmark-dashboard >> >> * Webkit port using CAIRO-GLES: >> https://linaro-public.papyrs.com/public/4146/GWG2011-WEBKIT-CAIRO-GLES/# >> also in Launchpad >> https://blueprints.launchpad.net/linaro-graphics-misc/+spec/linaro-gfxmm-webkit-cairo-gles > > Once we have the show on the road (i.e. the roadmap items estimatded, > approved and scheduled for Q4) would it make sense to kill the > blueprints above? I don't like the idea of having duplication (or a > 1-to-1 mapping) there, and ISTM that you really want to have blueprints > that are smaller sized than what these are. > -- > Christian Robottom Reis, Engineering VP > Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 > Linaro.org: Open Source Software for ARM SoCs > > _______________________________________________ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev > _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
