Re: Notes from today's Release Meeting(s)
On Tue, Jul 29, 2008 at 09:49:23PM -0700, S Page wrote: Michael Stone wrote: 5. Separately, I wish we were receiving even more volunteer testing. Can you help out? Fame, glory, and the undying gratitude of hundreds of thousands of children await you! Background: I'm just a G1G1. I don't have a Developer key, but on my own initiative I installed candidate-703 and candidate-708 using olpc-update and provided some feedback and bug reports. ... More clarity. Is more clarity needed more in some fora than in others? Is this nominated Wednesday build going to be a candidate build that mere users can install using olpc-update, or do I need the fabled bronze Developer key to become a joyride-like tester of nominated 8.2 builds? It will soon, but not yet. In a few weeks, once we're more confident in the sustainability and security of the build, then we'll publish an official candidate build with cryptographic signatures that mark it as suitable for mass installation. and that cloning/updating the Friends in Testing page would be useful. I'd never heard of http://wiki.laptop.org/go/Friends_in_testing I've never heard of X is a rather consistent refrain. Hrm. I did sign up for http://wiki.laptop.org/go/8.2.0#Put_Your_Name_Here_to_Confirm_You_Will_Try_the_Release_Candidate Thanks! I think once OLPC has a candidate build that people can install using olpc-update and has been smoke-tested, then it can publicize it on planet.laptop.org, olpcnews.com, forum.laptop.org, etc. Another mailing list won't help as much to get the word out. Okay. I'm not so sure. If you want more testing, just publicize as above. I didn't hear about candidate builds until I started following devel and figured out the wiki's green Latest Releases box. Should we make the Latest Releases box more prominent or readable? Me too, especially if there's clarity about olpc-update vs. the fabled developer key. You should probably request a developer key: http://wiki.laptop.org/go/Developer_key It will make your life as a tester much, much easier. Besides - Forth is fun! Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] Notes from today's Release Meeting(s)
On 30 Jul 2008, at 15:59, Michael Stone wrote: On Tue, Jul 29, 2008 at 09:49:23PM -0700, S Page wrote: I'm not so sure. If you want more testing, just publicize as above. I didn't hear about candidate builds until I started following devel and figured out the wiki's green Latest Releases box. Should we make the Latest Releases box more prominent or readable? Right now it's very – hmmm, safe – and so it should be. How about once your confident of a release candidate and a singed image is available, it gets an addition block (in warning red tint perhaps) noting an RC for those willing to live on the bleeding edge is available for testing? I guess this will only have much impact if the RC is about for at least few weeks. --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Notes from today's Release Meeting(s)
1. We're going to begin nominating this week's 'joyride-weekly' tomorrow at 0900 EDT. If you have risky changes you want to contribute, please provide them _after_ we deliver our nomination. If you want to help more peoples' changes make the deadline, then please help smoke-test joyrides built close to the deadline. Please record your results on http://wiki.laptop.org/go/Test_Group_Release_Notes and file bugs liberally. When we deliver the build nomination, we will summarize the currently available testing notes in the announcement mail. 2. This week, we will submit the nomination announcement in the following venues: devel@, testing@, support-gang@, the 1cc whiteboard, OLPCNews, forum.laptop.org, and locations on the wiki TBD - the front page Latest releases box - the test group release notes page In addition to a summary of current testing notes, the announcement will include a pointer to testing instructions. (Feel free to help write testing instructions if you've ever been frustrated with the current ones.) 3. We would be really happy if we felt comfortable entering code freeze (a.k.a. package-level change control) next Wednesday. We will make this decision in our Tuesday release meeting. Our fine colleagues in QA have agreed to assist us in making this decision by smoke-testing one fresh joyride per day. 4. In preparation for the full-blown regression tests that we will run in coming weeks, it would be very helpful if we received more detailed package-level ChangeLog entries and if we did better job of displaying the ChangeLog and related-tickets data that we currently have available. (In addition, anyone who further improves Reinier's, Bert's, and Marco's announcer scripts will earn a drink or treat from me.) 5. Separately, I wish we were receiving even more volunteer testing. Can you help out? Fame, glory, and the undying gratitude of hundreds of thousands of children await you! 6. We need to begin settling on an activity pack to use for testing purposes. Suggestions on peaceful ways to identify the contents of this activity pack would be appreciated. Thanks, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from today's Release Meeting(s)
On Tue, Jul 29, 2008 at 8:45 PM, Michael Stone [EMAIL PROTECTED] wrote: 5. Separately, I wish we were receiving even more volunteer testing. Can you help out? Fame, glory, and the undying gratitude of hundreds of thousands of children await you! I (just an interested G1G1 owner for my grandson with a Solaris/Unix/Linux background) would love to help testing, but you are not making it very easy. You have to follow devel@ to know what is going on and that alone is almost a part-time job. On the wiki there is a Friends in testing page (http://wiki.laptop.org/go/Friends_in_testing) but it does not seem to be used by the core developers/testers/release team. There has only been one request for testing WiFi compatibility for 8.1.1, but nothing for testing 8.2. I believe you really need some dedicated person as liaison between sugarlabs/1cc and outside testing and development volunteers. Anyway I'll try to test whatever build you nominate tomorrow. Ton van Overbeek ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from today's Release Meeting(s)
http://wiki.laptop.org/go/Friends_in_testing I believe you really need some dedicated person as liaison between sugarlabs/1cc and outside testing and development volunteers. We're working on it! Are you interested in joining OLPC's Support Gang where a collegial group discusses just such issues? Buzz me personally if so, thanks-- we have a mailing list of ~100 dedicated volunteers and weekly phone calls with intl guest speakers in deployment development, for exactly such reasons -- improving OLPC/Sugar support and testing: http://lists.laptop.org/listinfo/support-gang Definitely send me your phone number if you can. Anybody can join if you want to contribute to OLPC Support-- Thanks! --Holt :) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from today's Release Meeting(s)
On Tue, Jul 29, 2008 at 09:32:42PM -0400, Ton van Overbeek wrote: I (just an interested G1G1 owner for my grandson with a Solaris/Unix/Linux background) would love to help testing, but you are not making it very easy. What would make it easier for you? I gather that having the nominated Wednesday build helps and that cloning/updating the Friends in Testing page would be useful. Anything else come to mind? You have to follow devel@ to know what is going on and that alone is almost a part-time job. Several folks (rsmith and cscott) suggested making at least a devel-announce list for this sort of traffic. Would that help? (Previous requests for volunteer list summarizers were not fulfilled.) On the wiki there is a Friends in testing page (http://wiki.laptop.org/go/Friends_in_testing) but it does not seem to be used by the core developers/testers/release team. It's simple forgetfulness; most of those people follow [EMAIL PROTECTED] :) There has only been one request for testing WiFi compatibility for 8.1.1, but nothing for testing 8.2. 8.2 has only recently (a few weeks ago) become worth booting. Frankly, I've been too overwhelmed with Sugar bugs to pay close enough attention to wireless issues. I believe you really need some dedicated person as liaison between sugarlabs/1cc and outside testing and development volunteers. We agree -- we just haven't found such a person yet. We even have a job description for such a person, though (argh!) it doesn't seem to be posted at http://laptop.org/en/jobs.shtml. Anyway I'll try to test whatever build you nominate tomorrow. Thanks so much! Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from today's Release Meeting(s)
Michael Stone wrote: 5. Separately, I wish we were receiving even more volunteer testing. Can you help out? Fame, glory, and the undying gratitude of hundreds of thousands of children await you! Background: I'm just a G1G1. I don't have a Developer key, but on my own initiative I installed candidate-703 and candidate-708 using olpc-update and provided some feedback and bug reports. ... What would make it easier for you? More clarity. I gather that having the nominated Wednesday build helps Is this nominated Wednesday build going to be a candidate build that mere users can install using olpc-update, or do I need the fabled bronze Developer key to become a joyride-like tester of nominated 8.2 builds? and that cloning/updating the Friends in Testing page would be useful. I'd never heard of http://wiki.laptop.org/go/Friends_in_testing I did sign up for http://wiki.laptop.org/go/8.2.0#Put_Your_Name_Here_to_Confirm_You_Will_Try_the_Release_Candidate Several folks (rsmith and cscott) suggested making at least a devel-announce list for this sort of traffic. Would that help? I think once OLPC has a candidate build that people can install using olpc-update and has been smoke-tested, then it can publicize it on planet.laptop.org, olpcnews.com, forum.laptop.org, etc. Another mailing list won't help as much to get the word out. I believe you really need some dedicated person as liaison between sugarlabs/1cc and outside testing and development volunteers. I'm not so sure. If you want more testing, just publicize as above. I didn't hear about candidate builds until I started following devel and figured out the wiki's green Latest Releases box. Mozilla does fine with self-selected groups of self-builders, nightly testers, alpha testers, beta testers, etc., I don't think they have any such liaison person. Anyway I'll try to test whatever build you nominate tomorrow. Me too, especially if there's clarity about olpc-update vs. the fabled developer key. Thanks so much! No, thank you! -- =S ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
