It seems a release goes through a number of stages where the release team
focuses on progressively more of the intended capabilities of the packaged
content.
Those not directly involved often wonder about the state of the progress and
the whether or not those involved know about what a tester is observing.
During these rapidly changing stages of release building, the Trac
ticketing system seems to be too finely grained to provide a general picture
of the state of the progress.
I suspect that there are other methods to learn what is wanted. Please
point to examples of success. Not knowing any better, I've posted these
pages on the Sugar Labs wiki for the Sugar on a Stick project ,
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/GettingInvolved (see the
subpages).
Perhaps similar pages are needed for the Rawhide XO release. Those
involved, please advise.
--Fred
On Sun, Mar 29, 2009 at 9:27 PM, Mikus Grinbergs <mikus(a)bga.com> wrote:
The ~cjb images for rawhide-xo are good enough that I've been
able to run
quite a few applications on my XO. But while logged in to Sugar (e.g., with
20090326.img on the XO), I get neither sound out nor a "moving picture" out
from applications meant to produce those.
I do not have any particular test case -- *none* of the applications I've
tried (they all run properly on 8.2.1) produce sound/video for me. [And
some of those applications have taken me hours to install, and would require
even more hours to detail a "how to install".]
Nevertheless, I feel audio/video lack in rawhide XO is serious. The
existing OLPC tickets I've found on bugzilla.redhat are mostly about
__build__ problems. What I'm seeing are __usability__ problems. Where (and
how) should I report lack of audio/video output on an XO?
mikus
_______________________________________________
Fedora-olpc-list mailing list
Fedora-olpc-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-olpc-list