Re: Linaro Release 12.09 Postmortem Summary
On Fri, Oct 5, 2012 at 4:36 PM, David Zinman wrote: > Postmortem and lessons learned for Linaro's release 2012.09 > > https://wiki.linaro.org/Cycles/1209/Release/Review Is there any specific reason why we're missing the postmortem for so many teams? Cheers, -- Ricardo Salveti de Araujo ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Planning topcs for inclusion in linux-linaro
On Fri, Oct 5, 2012 at 2:03 PM, 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? Andrey, let's make sure this is properly communicated over time for the maintainers and linaro-dev, so everyone can understand and see the progress done (to prepare any kind of rebase/pull). >>> Yes, this makes sense. >>> Would the following plan be OK: >>> ( 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. >>> * October 16: ll rebuild based on llct-20121012. >>> * October 23: ll rebuild based on llct-20121019., 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. > * October 16: ll rebuild based on llct-20121012., 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. There are some advantages already about using v3.7 (like aarch64 support), but as it's a quite short cycle, and the we'll probably not have enough RCs to produce a useful tree for the release, v3.6 would be the best option. Let's also make sure we have a session at Connect to discuss the tree maintenance as usual, then we can better announce/propose any changes you're doing for the following cycles. Cheers, -- Ricardo Salveti de Araujo ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Planning topcs for inclusion in linux-linaro
Greetings, Minor change to the plan: * The current llct is *llct-20121006.0* * October 9: ll rebuild based on llct-20121006.0 * October 16: ll rebuild based on llct-20121012., ll code freeze (no massive ll topics updates after that; bugfixes only) 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: ( 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. * October 16: ll rebuild based on llct-20121012. * October 23: ll rebuild based on llct-20121019., 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. * October 16: ll rebuild based on llct-20121012., 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. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro Release 12.09 Postmortem Summary
Postmortem and lessons learned for Linaro's release 2012.09 https://wiki.linaro.org/Cycles/1209/Release/Review Highlights and Key Successes The 12.09 release cycle saw some early work on minimal ARMv8 bootstrap, with a very minimal rootfs to help other developers that want to get involved with porting. This work is critical for the future of Linux on ARMv8, as the major GNU/Linux distributions can use it as base to bootstrap and support this new architechture. Registration (http://connect.linaro.org/wp-login.php?redirect_to=/register-connect/) is open for Linaro Connect (LCE 12 Copenhagen) which will be held from 29 Oct to 2 Nov at the Bella Center in Copenhagen, Demark. In addition to the regular track sessions, LCE 12 will host three mini summits: an ARMv8 (64-bit) mini-summit on the Tuesday, an Android mini-summit on the Wednesday and a big.LITTLE mini-summit on the Thursday. Postmortem and Lessons Learned == Development and delivery planning continues to be a high priority as Linaro continues to grow. The platform team has instituted a release week standup meeting to coordinate development and release planning for the upcoming cycle and consolidate QA status for the cycle. As Linaro expands we will be reviewing our processes to determine the best and most effiecient way to move forward. Blueprints = The number of high or essential priority blueprints that missed the cycle: Android3 out of 12 Developer Platform4 out of 6 Infrastructure 1 out of 5 Lava 0 out of 2 QA 1 out of 3 Total 9 out of 28 32% of high or essential priority blueprints scheduled for this cycle were not delivered. Total blueprints: 22 out of 53 missed the cycle. High priority missed blueprints recap: 12.05: 19 out of 48, 39% 12.06: 13 out of 31, 42% 12.07: 14 out of 31, 45% 12.08: 6 out of 26, 23% 12.09: 9 out of 28, 32% * Not included is data from working groups and landing teams Source: https://docs.google.com/spreadsheet/ccc?key=0AjEaTwrvj1bidGVXTlFYQUJJcnMxa1NDSVZDYVdRLXc -- David Zinman Linaro Release Manager | Project Manager 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
Re: Planning topcs for inclusion in linux-linaro
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: > >> ( 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. > >> * October 16: ll rebuild based on llct-20121012. > >> * October 23: ll rebuild based on llct-20121019., 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. > * October 16: ll rebuild based on llct-20121012., 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. -- Tixy ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Planning topcs for inclusion in linux-linaro
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: ( 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. * October 16: ll rebuild based on llct-20121012. * October 23: ll rebuild based on llct-20121019., 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. * October 16: ll rebuild based on llct-20121012., 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. Thanks, Andrey ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
sched: modify timer and workqueue framework to allow migration
Hi Guys, I have been working on this activity since some time and V2 of patches is up for review over kernel mailing list. If any of us is interested in using these patches, can pick them from: http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=shortlog;h=refs/heads/sched-timer-wq-migration-v2 Patches are applied over a merge of v3.6 and workqueue-for-3.7 branch from tejun. Blueprint of this activity: https://blueprints.launchpad.net/linaro-power-kernel/+spec/timer-workqueue-cpu-quiescent NOTE: This branch isn't merged into big LITTLE MP merge branch till now. Waiting for feedback from mainline. -- viresh ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Query: Vexpress quick boot
Glad you got what you wanted :) Looks like something odd is going on with the red button, though. I'll let the platforms folk know. Regards, Bernie On 5 Oct 2012, at 04:43, "Viresh Kumar" wrote: > On 4 October 2012 21:26, Ryan Harkin wrote: >> I'm not understanding this email thread at all... perhaps because I've >> read it from the top ;-) >> >> I thought from the first email that Viresh was trying to get the board >> to boot up completely from when he applies power to the board in >> that case, editing /media/VEMSD/config.txt and changing "AUTORUN" to >> "TRUE" means that when you power on the board, it will automatically >> power on the core tile (ie. it's the equivalent of pressing the red >> button after the motherboard boots). > > Bingo!! Exactly what i wanted. Updated here: > > https://wiki.linaro.org/PawelMoll/BootingVEMadeEasy > -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Planning topcs for inclusion in linux-linaro
On 10/05/2012 01:42 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: >> ( 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. >> * October 16: ll rebuild based on llct-20121012. >> * October 23: ll rebuild based on llct-20121019., 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? > > Also, I assume we're not going to try to move to Linux 3.7 this month? > Samsung LT release would be based on Linux-v3.6 final release, no plans to move to 3.7 during 12.10. -- Tushar Behera ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Planning topcs for inclusion in linux-linaro
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: > ( 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. > * October 16: ll rebuild based on llct-20121012. > * October 23: ll rebuild based on llct-20121019., 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? Also, I assume we're not going to try to move to Linux 3.7 this month? -- Tixy ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
LAVA down time
Hi All, Finally, after months of delays, our leased line is stable and usable. I have the router configured and ready to switch over, which I plan to do on Monday. As a consequence, I will be putting all the boards in LAVA offline on Sunday morning (UK time). Currently running jobs will be allowed to complete, but any new jobs will get queued, and not run until the switchover is complete. While the lab is down, I will also be upgrading control to precise and attaching the WiFi AP so that it has access to the outside world. Obviously, with the switch over, the IP address of v.l.o will change, and this will take some time to permeate through to DNS. I will make sure that this has happened before bringing all the boards back online, but it will probably mean that LAVA will not be running jobs until Tuesday morning, and that v.l.o will actually disappear for a couple of hours on Monday. Once the transition has happened, we should see a significant improvement in the response time when accessing v.l.o and utilising LAVA. Of course, if anyone sees anything wrong or odd, please alert me immediately. Thanks Dave Dave Pigott Validation Engineer T: +44 1223 40 00 63 | M +44 7940 45 93 44 Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
