@Walter: Gave that wiki a quick read . . . which seems to exceed my skillset . . . . I can do basic stuff, run basic commands . . . but I know nothing about "html markup language" . . . never had any education in command line . . . . I could go through some of the stuff, but the "writing test cases" part I don't see having time to lean how to do that, and then do it. My speed is "bug reports" . . . which even that doesn't seem to stay within the lines requested . . . .
In the past I tried to do some of the QA testing of installs . . . but, even that process is "cumbersome" to time schedules . . . in that, in the QA we can't just "report" any issues we might have found, we also have to file bug reports . . . before we can then report them in the QA . . . and seemingly the bug report thing has its own "issues" . . . like with "Lubuntu" I recently only found two options to report against "LXfind" and "LXschedule" . . . and then when I tried to "apport-collect" data to the bug report . . . from the terminal Launchpad opened and logged me in via the browser . . . but running the "collect + bug number" . . . data was not transmitted . . . ??? Tried several times . . . on both bug reports--to wit, one is now "invalid" but the other one seems not to have been "received." Point is that there are over-lapping layers of complexity in the QA that just take "too much" time . . . . As of Lu 19.04 and my seat of the pants testing goes, there really doesn't seem to be major problems with it . . . the install went well, running it every few days I could find things in the GUI that I might like to see improved as far as the visuals of it goes . . . and some practical stuff like being able to "suspend" from the log in window . . . (there are now two icon-applets for power stuff that are new, but I don't think "suspend" works from there) . . . but, otherwise can't complain. F On Mon, Feb 4, 2019 at 11:15 AM Walter Lapchynski <w...@ubuntu.com> wrote: > On 2019-02-04 18:02, Fritz Hudnut wrote: > > I can make no > > promises to complete any projects within any time frame due date . . . > > but, if you wanted to "walk me through it" . . . there might be a > > moment or two where I could make some "edits" with the caveat that > > "nothing is promised" . . . . > > Totally understood, Fritz. I have no expectations of anyone, really. I > mean, we're all volunteers. Simon and I have disappeared for lengths of > time because life got in the way (apparently when you had your bubble of > time), though I guess when it comes time to crunch time, we are on the > line to get something out the door. But for everyone else, no > expectations. *ANY* help is helpful. And if I can help you to know how > to fix a problem on your own in the future, all the better— for all of > us! > > That said, there is [documentation][1] on this process that is pretty > good. I urge you to read through it and give it a go. Put me as one of > the reviewers. If you need any help along the way, please let me know. > And if you'd like to schedule a time to go over it together in real time > on IRC or whatever, I'm game for that, too. > > [1]: https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual/Writing > > -- > @wxl | polka.bike > C563 CAC5 8BE1 2F22 A49D > 68F6 8B57 A48B C4F2 051A >
-- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users