Re: 10.10 install bug...untested.
Sorry for the real late reply on this... I got back with him and it ends up being a network hard error (when he tries to install the OS its locking on cuz of the network card) but its a old laptop and I dont know the wireless card is but if I find out I will post it here. And I have tested the OS on my desktop late last night and had no problems (maybe only his system with his set-up) On Tue, 2010-10-05 at 13:44 -0400, Jeff Lane wrote: > On Sun, 2010-10-03 at 21:09 -0500, Linden wrote: > > Was talking to a friend on the State TX team and was told that he is > > having some prombles installing 10.10...there maybe a bug in the ISO for > > a fresh install...I will test this once I have some time but if someone > > is able to test this fasterlet me know of the outcome. > > > > Stephan Harz > > Think maybe you could get your friend to provide something useful in the > way of details? > > Saying "My friend has a problem installing. it may be a bug. Can you > test this." really doesn't help much. > > FWIW, I've done at least a hundred or so installs of 10.10 going all the > way back to the first alpha ISO. The RC had no issues for me at all > (though there is at least one issue with booting the installed system). > > In any case, more details would be helpful here. > > Cheers, > Jeff > -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Information about the Ubuntu BugSquad
Hello folks, The Ubuntu project is pretty big and contains a lot of teams, one of those is the Ubuntu Bug Triagers Team which is called the "Ubuntu BugSquad", The BugSquad is the first point of contact for the bugs reports filed about Ubuntu, the team keep track of current bugs and make sure that major bugs do not go unnoticed by the developers, the members of this team assign bugs to packages, ensure that the bug reports are complete, find duplicates, recreate bugs, and forward bugs to their upstream authors (when applicable), all these activities help bugs to get fixed and subsequently to make Ubuntu even better. If you're interesting on joining the Ubuntu BugSquad we have a few points of contacts: == Mailing List == * https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad == IRC Channel == Our channel is #ubuntu-bugs and it's available trough the Freenode IRC Network. If you have any questions please do not hesitate on joining the channel and ask. == Wiki Pages == Some wiki pages that might help you to join the team and learn more about Bug Triage: * https://wiki.ubuntu.com/BugSquad * https://wiki.ubuntu.com/Bugs/HowToTriage/ * https://wiki.ubuntu.com/BugSquad/Mentors Help is always welcome, there's plenty of bugs waiting to be triaged on Ubuntu if you want to help feel free to contact us trough the previous listed methods. Have a nice day!, pedro. -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Improving Communication Feedback Report
Hola Ara, El mié, 06-10-2010 a las 09:15 +0200, Ara Pulido escribió: > Hello all! > > During UDS Maverick we had a session about improving the communication > channels in the Ubuntu QA team. It was more about improving processes, > and using better and more often the channels that we already had. > > Now that the Maverick cycle is finishing is time to look back and see > what work well and what didn't work that well, so we can discuss it > during UDS Natty and keep improving our processes. > > *The IRC channels* > We have three channels QA-related in use: #ubuntu-bugs, #ubuntu-testing, > #ubuntu-quality. These are the results from the survey when I asked the > question "Are you familiar with the following IRC channels?" > > * #ubuntu-testing: 91% > * #ubuntu-quality: 50% > * #ubuntu-bugs: 50% > > The channel #ubuntu-quality seems to be in need of some rethinking. Less > people knows it, very few people actually use it. We should rethink the > way we use this channel and explain better what's its purporse. Any ideas? Well the issue is that the channel is just being used for the QA Meeting but the rest of the week is really quiet, IIRC in the creation of the channel the idea was to have a common place for people on the #ubuntu-testing and #ubuntu-bugs to hang out but i don't see a lot of discussions on it. > > Also, although the #ubuntu-bugs channel is used, only half of the people > subscribed to Ubuntu QA is familiar with it. Pedro, can you prepare an > email to Ubuntu QA explaining #ubuntu-bugs channel and other resources > for triagers? Yes, I'll prepare something and send it to the Ubuntu QA list. Thanks for the survey results Ara!, pedro. -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Re: Meeting 2010-10-06 - 17:00 UTC - #ubuntu-quality
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 good, now i can verufue de keys from ubuntu keyserver using enigmail Thx Sulumar PS check mine to see if everything works like it should On 05/10/10 23:14, Steve Beattie wrote: > On Tue, Oct 05, 2010 at 11:04:45PM +0200, Sulu Mayer wrote: >> Frist of all i cant veryfie that pgp signature and dont know why. probably >> forgot soething. lol > > It verified here just fine, how is it failing for > you? Do note that firegpg, which you appear to be using, > has been discontinued due to the author's inability to > cope with the frequent changes to the gmail interface; see > http://blog.getfiregpg.org/2010/06/07/firegpg-discontinued/ for > more info. > > Sorry you can't make the meeting. > > Thanks. > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAkysKsYACgkQ3J5GZZ/GIAQiNAD/f+kGIXLpQAfPSEoe0kIpKVNM hjZ90Q9fznKyqsTCrzAA/iYKJmLkB8eXTPqk3JO/QeHMvNa782U5v1hidGKTYWdd =RSSx -END PGP SIGNATURE- -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
Improving Communication Feedback Report
Hello all! During UDS Maverick we had a session about improving the communication channels in the Ubuntu QA team. It was more about improving processes, and using better and more often the channels that we already had. Now that the Maverick cycle is finishing is time to look back and see what work well and what didn't work that well, so we can discuss it during UDS Natty and keep improving our processes. *The meetings* One of the main outputs of that session was about the weekly meetings the we have on IRC. People found that the meeting times were too fixed and that the meeting minutes were not always sent and stored. Some of the actions items to improve this situation were: * A rotating chair * A rotating time of the meeting, to accommodate more people * The chair was going to send a summary to the mailing list The feedback collected from the survey I sent a week ago is very positive: * 84.6% of the people that replied the survey thought that the rotation of time is useful * 50% increased their participation thanks to the rotation * 100% of the people read the summary sent to the list! One of the main concerns about the rotation of the meeting is the predictability. People sometimes are surprised about the time, and can't make it to the meeting. One possible solution would be that the chair, instead of sending the reminder the same day or the day before, sends the reminder on Monday, first thing, so people have a couple of days to read the email and organize their week. Another issue related to meetings that I have observed during the Maverick cycle is that, the chair, if it is the first time that he or she chairs the meeting, has a very hard time trying to find documentation on how to chair the meeting, where to get the logs afterwards, where to put the summary and logs and when to send them. To solve all of these issues, I have created a small documentation on the Meetings page to help new people who are chairing to find their way: https://wiki.ubuntu.com/QATeam/Meetings/Chairing *The Launchpad Team* In the Maverick cycle the Ubuntu Testing team got 46 new members and 20 membership expired. That's an increase of 26 members this cycle, which is an 8.4% increase. *The Mailing List* During the Lucid cycle, 404 messages were sent to the mailing list. During the Maverick cycle 274 messages were sent. We have to take into account that I counted from May 1st until 30 September (5 months) That makes an average of 67 messages per month in the Lucid cycle and 68.5 messages per month in the Maverick cycle. Numbers are very similar, but subscribers have increased a lot in the last cycle, from 703 at the end of the Lucid cycle to 970 readers subscribers right now. That's an increase of 37.98%!! *The IRC channels* We have three channels QA-related in use: #ubuntu-bugs, #ubuntu-testing, #ubuntu-quality. These are the results from the survey when I asked the question "Are you familiar with the following IRC channels?" * #ubuntu-testing: 91% * #ubuntu-quality: 50% * #ubuntu-bugs: 50% The channel #ubuntu-quality seems to be in need of some rethinking. Less people knows it, very few people actually use it. We should rethink the way we use this channel and explain better what's its purporse. Any ideas? Also, although the #ubuntu-bugs channel is used, only half of the people subscribed to Ubuntu QA is familiar with it. Pedro, can you prepare an email to Ubuntu QA explaining #ubuntu-bugs channel and other resources for triagers? *The new landing page* We have created a new landing page at http://qa.ubuntu.com but, as the page just went live a couple of weeks ago, we would gather information at UDS and we might as for feedback at the end of the Natty cycle, when we have enough data about it. One of the suggestions that I got in the survey is that, now that we have increased participation, it is time to improve the documentation. I couldn't agree more. I am working with the Community team with their Community Review project [1] to try to understand what issues the new contributors have to face before they feel confident contributing. Improving that new contributor first experience is going to be one of my goals during Natty cycle. To sum up, I think that the balance of these changes has been positive. Let's work together again during Natty UDS and cycle to keep the improvements and build a great Ubuntu QA community!! Thanks all! Ara. [1] https://wiki.ubuntu.com/CommunityReview/Sep2010 -- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
