W dniu 17.05.2011 10:54, Alexandros Frantzis pisze:
Hi all,
I completely missed the Linaro release process session during LDS, but here are my thoughts on the Linaro development cycle.
Currently, the Linaro cycle lags behind the Ubuntu cycle by one month. This is done so that the Linaro releases are based on a stable system.
Unfortunately, this scheme causes some disruption for me (and I suspect for other engineers, too). The problem is that while the current Linaro cycle is still ongoing, we need to start planning for next-cycle/LDS, attend LDS and after that investigate some more and create the specifications. This is hard and time consuming work and I am sure not many people (including me) can continue to work effectively on their remaining work items while drafting specifications or attending LDS. The problem is exacerbated further because the end of cycle is usually a very strenuous period for engineers.
So my questions/suggestions are:
- Do other engineers feel this way?
Yes. I think that linaro has 5-month cycle with one month squandered on LDS, blueprints and catch-up with the previous release where we are still (supposedly) going to make improvements.
I would rather have the very same cycle or even one cycle _before_ Ubuntu ships so that by the time we're at UDS we can have a UDS/sprint hybrid where we already discussed some things earlier, already have some blueprints and code rolling.
- From people's experience, has the one-month-after-ubuntu schedule provided concrete advantages? Could we get away with less (e.g. one week)?
From my point of view it's hard to judge as Validation is strictly outside the main archive, kernel and toolchain where we mostly interact with our Ubuntu brethren. It is however interesting to consider how our cycle would impact Ubuntu if _all_ of Linaro were really releasing once a month.
Thoughts?
Thanks for bringing this up Alf :-)
Best regards ZK