On 22/05/13 02:48, the mail apparently from Andrey Konovalov included:
The next steps are:
May 22: ll rebuild based on llct-20130521.0
May 23: ll rebuild based on llct-20130521.0, linux-linaro release
candidate, code freeze
The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).
This happened, which is good, but llct has not updated for 3.10-rc3 or
3.10-rc4 yet, which is not good; llct is two weeks old. Something
similar happened last month.
I realize this isn't the case for everyone but actually the literal
"schedule for 13.05" holds zero interest for me.
Timely updates on llct for each mainline -rc are very interesting
though, in fact we depend on them.
Is it possible things have gotten a little unbalanced with all the
excitement of "code freezes", "releases", "schedules" that make the
choo-choo noises for the monthly release train set, we're not giving the
llct tracking activity enough love?
-Andy
--
Andy Green | Fujitsu Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
