On Wed, Jun 16, 2010 at 23:47, seattlechaz <seattlec...@hotmail.com> wrote: > Greetings: > > I downloaded and hash checked the Maverick Meerkat alpha then installed > it in Virtual Box. Then, as is my custom, I installed all the updates. > Upon rebooting, GDM failed and no amount of command line juju would > bring it back. > > Question: should I have just tested the alpha iso as it stands without > the available updates? This is a new venture for me so please clarify. > Thank you.
When did you download it? And where did you download from? http://cdimages.ubuntu.com/daily-live/ is the best place to get the current daily build of the latest development release (in this case, Maverick Alpha 1) To answer your actual question (I just wanted to see if you were having this issue on the latest daily ISO, or if you were using the older Alpha 1 ISO): No, you are doing right. There are different kinds of testing that go on. Daily and Milestone ISO testing are just that. You pull down the most recent ISO image and test a variety of things, such as the standard and debian installers, various install options (free-only, etc), and ensure that the ISO will completely install a bootable system on a computer (or in a VM). You can also test the development OS itself, which is what you seem to have started. That helps test various parts of the OS as they are being developed. There are also other types of testing that are focused on specific goals or subsystems or whatever, but ad hoc testing is also a benefit as that can cover test cases that we may not have thought of that exist out in the "real world". In any case, you've done fine! That is EXACTLY what you should do. Test the ISO by installing, then test the OS by installing the latest updates and reporting on what broke in each scenario. Just make sure that for ISO testing, you are pulling down the latest daily-live build to ensure you have the most recent ISO. rsync is good for that. Once you have a given iso, rsync will only pull the diff between what you have and what's available, so updating to the latest ISO is a lot faster. You can also use a script to sync the ISOs manually or automatically. Here's one that is provide by the Ubuntu testing community: https://wiki.ubuntu.com/Testing/Isoscript Also, if you don't have one, you need a Launchpad account: http://launchpad.net So you can file bugs as you find them. And since you seem to be new to the testing thing, be sure to read up on the process: https://wiki.ubuntu.com/Testing/ That will get you started, and point you to information on the various testing activities that exist. Hope that helps! Jeff -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
