lubuntu-qa team mailing list archive

[Ron Mitchell <rm2892@xxxxxxxxx>]

Nicholas:

Re your request for feedback:

It's taking me longer that I'd expected to come up to speed. My lack of experience with software development is proving to be a problem.

Have spent the past week reading everything I can get my hands on about how you guys do business. Have yet to register for the test cases, but at least I know now that sooner or later I need to do that. I have been installing each Friday's build and checking out the things I usually check out when updating/installing any Linux distro. I'm quite aware however, that there's much more involved to your efforts than that. Still very much on a learning curve, so I'm not really in a position yet to provide you with any kind of intelligent feedback.

I'm still trying to clear part of my MacBook for Lubuntu testing. After much whining and gnashing of teeth, I did get rid of Windows 8 pre-release. That appears to have solved my major difficulty with booting Lubuntu from an external USB drive in that I've made space for it on my internal drive next to OS X Lion. Still want to try an external USB drive but for the moment, at least I should be able to do some of the test cases for AMD64+Mac - once I get fully set up. (still working on it). 

Anyway, bear with me. Hopefully I'll be able to contribute something useful before too long.

Ron Mitchell



On Mon, 13 Aug 2012 18:40:46 -0400
Nicholas Skaggs <nicholas.skaggs@xxxxxxxxxxxxx> wrote:

> Greetings everyone! After each milestone I generally review everything 
> that happened during the milestone, trying to understand how we did, and 
> how it went for you as a community. The release team does the same, 
> comparing how their team did on respins, communicaton, etc. However, 
> especially given the recent confusion of cadence testing, and it itself 
> being an experiment, I'd like to take a moment to specifically invite 
> everyone to provide feedback on how iso testing has been this cycle, and 
> in particular this last week. This is entirely open-ended, but I'll 
> leave some questions for you to think about.
> 
> Did you find the testing itself easy to complete?
> Was it easy for you to follow along with how the testing was going?
> Did you have fun!?
> Specific to the idea of "cadence testing" (that is, to test outside of 
> milestone at regular intervals), did you find the testing useful or 
> otherwise productive expenditure of our collective "time and effort" as 
> a community?
> 
> I don't want to share too much of my thoughts so as to not influence the 
> discussion at first. However, I will say it can be difficult to keep 
> abreast of what's happening during the testing weeks as it is and that 
> without the ability to use the isotracker effectively during a cadence 
> week makes it even harder. During the cadence week, using the 
> isotracker, people were lost as to what to do or the status of what was 
> trying to be achieved. If we continue to aim for this type of testing, 
> we'll need to expand the workarounds and ultimately enhance the 
> isotracker to support the testing effort.
> 
> Nicholas
> 
> P.S. Just a quick note; I am always available for feedback or discussion 
> in any manner you wish. Email, IRC, voice or google hangout, skype, 
> whatever you wish. Any idea or topic is fair game. I'd love to hear from 
> you!



-- 
Ron Mitchell <rm2892@xxxxxxxxx>










On Mon, 13 Aug 2012 18:40:46 -0400
Nicholas Skaggs <nicholas.skaggs@xxxxxxxxxxxxx> wrote:

> Greetings everyone! After each milestone I generally review everything 
> that happened during the milestone, trying to understand how we did, and 
> how it went for you as a community. The release team does the same, 
> comparing how their team did on respins, communicaton, etc. However, 
> especially given the recent confusion of cadence testing, and it itself 
> being an experiment, I'd like to take a moment to specifically invite 
> everyone to provide feedback on how iso testing has been this cycle, and 
> in particular this last week. This is entirely open-ended, but I'll 
> leave some questions for you to think about.
> 
> Did you find the testing itself easy to complete?
> Was it easy for you to follow along with how the testing was going?
> Did you have fun!?
> Specific to the idea of "cadence testing" (that is, to test outside of 
> milestone at regular intervals), did you find the testing useful or 
> otherwise productive expenditure of our collective "time and effort" as 
> a community?
> 
> I don't want to share too much of my thoughts so as to not influence the 
> discussion at first. However, I will say it can be difficult to keep 
> abreast of what's happening during the testing weeks as it is and that 
> without the ability to use the isotracker effectively during a cadence 
> week makes it even harder. During the cadence week, using the 
> isotracker, people were lost as to what to do or the status of what was 
> trying to be achieved. If we continue to aim for this type of testing, 
> we'll need to expand the workarounds and ultimately enhance the 
> isotracker to support the testing effort.
> 
> Nicholas
> 
> P.S. Just a quick note; I am always available for feedback or discussion 
> in any manner you wish. Email, IRC, voice or google hangout, skype, 
> whatever you wish. Any idea or topic is fair game. I'd love to hear from 
> you!


-- 
Ron Mitchell <rm2892@xxxxxxxxx>