On Tue, May 31, 2011 at 5:27 AM, Ilias Biris ilias.biris@linaro.org wrote:
Picking up this subject again, here is a wiki page with the ideas mentioned in the thread and (currently) my comments on those ideas:
https://wiki.linaro.org/ProjectManagement/ParkingLot/DevelopmentCycleProposa...
You can check out the proposals, correct if there is anything wrong/missing, and add more. I am thinking to get some basic voting going on there so that you can show your preference, although some ideas are really interconnected.
I would like to keep this topic moving, in order to attempt solving it early and adjust as we go on.
I have added my comments to the page. I like the second idea: use an internal deadline. "End the cycle for your working group prior to the LDS - go to the LDS having closed all items, and postponed anything that was still opened. " The team is supposed to start drafting the the next cycle blueprints in preparation of LDS. Effectively, this is what we have been attempting to do.
Regards, Mounir
Best,
Ilias
On 17/05/11 11:54, Alexandros Frantzis wrote:
Hi all,
So my questions/suggestions are:
Do other engineers feel this way?
From people's experience, has the one-month-after-ubuntu schedule
provided
concrete advantages? Could we get away with less (e.g. one week)?
- If we don't change anything we should at least make this situation
very clear
to engineers/managers, so that they can plan accordingly: ~5 months of normal work, starting two weeks after LDS and ending one
week
before the next LDS. Keep the rest for planning/LDS and spec-ing, plus
some
light work.
Thoughts?
-- Ilias Biris, Aallonkohina 2D 19, 02320 Espoo, Finland Tel: +358 50 4839608 (mobile) Email: ilias dot biris at linaro dot org Skype: ilias_biris
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev