Greetings,
On 10/06/2012 01:07 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
- The current llct is *llct-20121006.0*
- October 9: ll rebuild based on llct-20121006.0
ll-20121010.0 has been pushed to linux-linaro-tracking.git. The pinned manifest is: http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git%3Ba=blob%3Bf...
ll-20121010.0 is based on llct-20121009.0, which is llct-20121006.0 plus few fixes. Here is the pinned manifest: http://git.linaro.org/gitweb?p=kernel/linux-linaro-manifest.git%3Ba=blob%3Bf...
- October 16: ll rebuild based on llct-20121012.<N>, ll code freeze (no massive ll topics updates after that; bugfixes only)
If you have a new topic to add to 12.10, please make sure that it is submitted by October 12 (common topics to add to llct tree), or October 16 (ll topics). The topics for llct should be based on v3.6 or (if there is a need for that) on another llct topic. The ll topics should be based on llct, or (if there is a need for that) on v3.6 or another ll topic. If an ll topic is based on an older llct version, it can be rebased to the current one automatically, but the commit ids would be mangled (of course).
For the 12.10 the plan is to switch to config fragments for all the supported boards. Please make sure that the config fragment for your board is up-to-date here: git://git.linaro.org/kernel/configs.git , config-boards-3.6 branch
Otherwise these instructions apply: https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess
Thanks, Andrey
On 10/05/2012 05:25 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2012-10-05 at 17:03 +0400, Andrey Konovalov wrote:
On 10/05/2012 12:12 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2012-10-04 at 23:02 +0400, Andrey Konovalov wrote:
don't we need some kind of notification system where you announce a plan to rebuild linux-linaro and give us a version of llct to base our LT branches off?
Yes, this makes sense. Would the following plan be OK: (<N> should normally be 0, but may be a small positive number)
- till the end of this week please use llct-20121004.0 as the base for
the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>
- October 23: ll rebuild based on llct-20121019.<N>, ll code freeze
(no massive ll topics updates after that; bugfixes only)
Is this month following the normal release cycle? If so, isn't the release day Oct 24th, and release candidates are built from the previous Thurday's code, i.e. Oct 18th. I.e. the freeze for the release should be Oct 16th not 23rd?
Oops.. Your are right. Why don't we have the Thursday, October 32 this year?
So the correct plan is the following:
- till the end of this week please use llct-20121004.0 as the base
for the linux-linaro (ll) topics
- October 9: ll rebuild based on llct-20121005.<N>
- October 16: ll rebuild based on llct-20121012.<N>, ll code
freeze (no massive ll topics updates after that; bugfixes only)
Also, I assume we're not going to try to move to Linux 3.7 this month?
That's correct. We didn't have the kernel.org release based (vs -rc based) ll release for quite a while. And the plan is to stick to v3.6 for 12.10 release unless someone needs to move to v3.7-rc* by all means this cycle. After October 19 the llct tree will move to v3.7-rc*, but the ll tree will be frozen till the 12.10 is out.
That all sounds reasonable to me.