varg1امروز کلاس چه ساعتی شروع می‌شه؟08:53
smartboyhwGuys, our QA Classroom sessions starts 1 hour later. Make sure you join us through #ubuntu-classroom and #ubuntu-classroom-chat!13:00
smartboyhw17 minutes till the first classroom session begins!14:13
jlking3Hi Phill14:22
* smartboyhw does anticipate for his own session a week later.14:23
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Introduction to QA / Testing: Overview of testing tools and areas - Instructors: balloons
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html following the conclusion of the session.14:30
balloonsHello and welcome to the ubuntu quality team session. My name is Nicholas Skaggs and I'm the QA Community Coordinator. Thanks for attending (or reading this log later!)!14:31
balloonsThis is the first of many being held over the next few weeks serving as a introduction to the ubuntu quality community team14:32
balloonsin this sessions I'll be giving a brief overview of what we do as a team and some of the ways to be involved.14:32
balloonsThis will be a high-level introduction with plenty of time for questions. So let's get started14:33
balloonsYou may ask questions at any point.. Just be sure to utilize the #ubuntu-classroom-chat channel. Prefix your question with QUESTION: to ensure I see it.14:33
balloonsSo first I'm going to give a brief overview of what QA is and how the team works, then I'll dive into the activities we do during the cycle. Along the way, we'll talk about the tools we use as well. Finally, we'll talk about how you can get involved and then do a Q & A.14:34
balloonsSo to start off, let’s take a look at the wiki page for the team14:34
balloonshttp://wiki.ubuntu.com/QATeam. On the page you can see some of the teams goals and purpose. Simply put, we help ensure everyone's work in ubuntu is presented in the best possible way14:34
balloonsFrom designing good process, to testing, to making sure things 'just work', we want the culmination of work that results in the ubuntu image to be the best it can be14:35
balloonsThe ubuntu community site also has a page worth checking out on quality; re-iterating these goals and some team background14:35
balloonsSo who are we and where do we hang out?14:36
balloonsWe're people from all over the physical world, and from many different aspects of ubuntu14:36
balloonsI held a blog series recently snapshotting of few of the people who are on the team: http://www.theorangenotebook.com/search/label/peoplebehindquality14:37
balloonsSo where do we hang out? As you can imagine many different places. A quick list of where to find us:14:37
balloonsright here on IRC, #ubuntu-quality14:37
balloonson our mailing list:     https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality14:37
balloonsin the forums;     http://ubuntuforums.org/forumdisplay.php?f=42714:37
balloonson askubuntu;     http://askubuntu.com/questions/tagged/quality14:37
balloonsand even on social sites like facebook; https://www.facebook.com/groups/UbuntuQA/14:38
balloonstwitter; https://twitter.com/ubuntutesting14:38
balloonsand google+; https://plus.google.com/b/108452779163647535106/108452779163647535106/14:38
ClassBotchristoffer asked: So this is not about how I can utilize launchpad (and other tools) for my own app development, is it more general about Ubuntu development?14:39
balloonschristoffer, this is intended to server as an introduction to the quality team. you can see the full schedule we have planned here: https://wiki.ubuntu.com/Testing/Activities/Classroom14:39
balloonsI'm not sure if there is a specific session that meets your needs or not. Most of the sessions come from a quality perspective not development.14:40
balloonsSorry that link should be: https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy14:40
balloonsOk, So, what do we do exactly as a team?14:40
balloonsDuring the course of the cycle, we as a team participate by providing test results for the packages as they are undergoing development. If we find a bug, we'll also report and file it.14:41
balloonsIn addition, we develop testcases, best practices and even tools to help us test more effectively14:41
balloonsWe test different types of things and utilize some terms to describe them14:42
balloonsThe frst is cadence testing, https://wiki.ubuntu.com/Testing/Cadence.14:42
balloonsCadence testing is simply the term we use to describe that we test at regular intervals.14:42
balloonsIn practice, this amounts to us testing every ~2 weeks during the cycle -- we test images, packages and and hardware.14:43
balloonsThe second is smoke testing, or dogfooding as some would call it, the development version of ubuntu. This means simply installing or upgrading to the development release and using it as a regular machine. By attempting to work and perform tasks under the development version you may encounter a bug. Your unique usage of the development version of ubuntu represents a testcase in of itself and helps us achieve broad general coverage across a14:44
balloonsvariety of hardware and workflows14:44
balloonsThe third is a call for testing. This is a call to test a specific piece of software, with an accompanying set of tests and instructions for testing.14:44
balloonsThis call could happen at anytime throughout the cycle, and is utilized by developers to help ensure the software they are landing in the development version is ready for general consumption.14:44
balloonsThis type of testing is generally for a new package landig in the development version of ubuntu14:44
balloonsSo collecting the results and running these different types of tests requires us to have a tool to help14:45
balloonsThe tool we use is called the QATracker14:45
balloonsThe tracker is where we submit the test results and get information needed to complete the test, such as the testcase and installation instructions.14:45
balloonsThere are actually several qatracker instances each geared towards testing different things14:46
balloonshttp://iso.qa.ubuntu.com is used to report results for image testing14:46
balloonshttp://packages.qa.ubuntu.com is used to report results for package testing14:46
balloonshttp://laptop.qa.ubuntu.com is used for laptop/hardware testing14:46
balloonsEach one has a specific focus and keeps track of results and testcases in the specific domain we're testing14:46
balloonsThe wiki page I linked above gives more specific details on how the qatracker works and it's usage14:47
ClassBotsmartboyhw asked: Why should people join Quality when there are other aspects of contributing to consider? (I know the answer, but not all people here do:))14:47
balloonsJoining the quality is a great way to get started with contributing to ubuntu.14:48
balloonsyou get to work with many different teams inside ubuntu and therefore get a taste of all the different areas. Quality is never the same from cycle to cycle; there's always new things to test and new ways to do it14:49
ClassBotThere are 10 minutes remaining in the current session.14:50
balloonsIn addition, it covers a wide variety of skills. From very technical to writing to creativity14:50
balloonsWe'll talk more about the opportunities in a moment14:50
hmdshrهیشکی اینجا فارسی حرف نمیزنه ؟14:50
balloonsAre a technical person? Do you like to code?14:51
balloonsor perhaps your just wanting to learn a little python?14:51
balloonsYou could consider writing some automated testcases using autopilot and contributing them to the ubuntu-autopilot-tests project14:51
balloonsyou could also work on some of the tools we use, such as testdrive; https://launchpad.net/testdrive14:51
balloonsPerhaps you enjoy writing, or are skilled with explaining things step by step14:51
balloonswe need your skills in our ubuntu-manual-tests project writing manual testcases!14:51
balloonsMaybe you just like breaking things, or running bleeding edge software -- contributing test results is right up your alley!14:51
balloonsEven if your not running ubuntu, but a flavor instead, we still need and welcome contributions in all of the above areas. We share many things like testcases and tools across the ubuntu family14:51
balloonssmartboyhw, I hope that helps to answer your question :-)14:52
ClassBotsmartboyhw asked: I accidentally stumbled upon http://desktop.qa.ubuntu.com/ . What's that for?14:52
balloonsWell as you can see at one time that was used for testing the desktop -- specifically new unity features. Nowadays we simply utilize packages.qa.ubuntu.com for those sorts of tests14:53
balloonsAsk any questions if you have them :-) Let me share with you the next steps for joining the team and being more involved14:54
balloonsThe steps for joining the team are quite simple. It's an open membership. You simply need a ubuntu SSO account14:54
balloonshttps://login.launchpad.net/+new_account, if you don't have one14:54
balloonsThat will allow you to contribute results to the tracker. In addition you should join our launchpad team and mailing list.. And then leave us a message and say hello! We're happy to help you get started and guide you through an area you'd like to help in14:54
ClassBotThere are 5 minutes remaining in the current session.14:55
balloonsYou can consider contributing testcases, test results, or even some new artwork for our pages (we always need those with an eye for creativity ;-) )14:55
balloonsHere's the links to our launchpad team and mailing list14:56
balloonsLP team: https://launchpad.net/~ubuntu-testing14:56
balloonsmailing list:  https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality14:56
ClassBotjlking3_ asked: The process, when I look at it, seems overwhelming and intimidating. I'm afraid that I'll report something wrong or in the wrong place or in the wrong way. I don't want to make things worse for the developers.14:56
balloonsjlking3, yikes! we're here to help you feel more comfortable about the process. You don't have to jump into the technical deep end of kernel debugging or some other exotic testing right away (or ever :-) ). Our tests are intended to be run by folks like yourself. We work together to share knowledge and help each other test and file bugs. You don't have to be an expert to participate14:59
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Introduction to QA / Testing: Using md5 checksum and Zsync - Instructors: phillw
balloonsI don't know everything (surprise!). However collectively as a team we are able to help each other out and solve most problems15:00
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html following the conclusion of the session.15:00
phillwHi everyone, my name is Phill. Whiteside and I'm the QA Team leader for lubuntu15:01
phillwThis short session is to introduce zsync and md5sum15:01
phillwFirstly, why use zsync?15:02
phillweach iso image is quite large and as they usually get updated each 24 hours, that's a lot of data!15:02
phillwzsync only downloads the parts of the ISO that have changed, it is faster AND uses less bandwidth15:03
phillwWhy use md5sum?15:03
phillwit is quite possible for a corruption to occur when downloading the ISO, if this happens your ISO will either not install, or exhibit very odd behaviour15:04
phillwthe other nice thing about zsync is that when it has downloaded the update, it automatically checks the MD5 checksum for you (one less step to carry out).15:05
phillwYou will see the zsync links if you go to the iso tracker and select the 'cd' icon to the  left of the ISO you want to download at http://iso.qa.ubuntu.com/qatracker/milestones/270/builds15:07
phillwin my example, the alternate install for lubuntu in 1386 architecture would be zsync http://cdimage.ubuntu.com/lubuntu/daily/20130623/saucy-alternate-i386.iso.zsync15:08
phillwzsync can also be scripted up to do various tasks automatically. Further details on that can be found at https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy/Zsync15:09
ClassBotjlking3_ asked: so you always add .zsync to the end of the URL to get the zsync'd version of the iso?15:09
phillwjlking3: the tracker has several ways to down load an ISO (direct, rsync etc.) the filename ends .zsync to make it obvious that it is the zsync version15:11
phillwif you wish to manually check an  ISO, move to the directory with the ISO in it and issue the command15:12
phillwmd5sum *iso15:12
phillwthis will give you the md5sum of the ISO's in the directory, which you can then check against what is on the iso-tracker, in my example, that would be http://cdimage.ubuntu.com/lubuntu/daily/20130623/MD5SUMS15:13
phillwUsing zsync elliminates this step, as it does it for you.15:14
phillwThat's the end of this introduction, if you have any questions, please feel free to ask (Preface them QUESTION: )15:15
ClassBotVasudevan asked: Which is a faster way to update daily isos over a slow home dsl connection - apt-get dist-upgrade or download zsync version? Thanks.15:17
phillwVasudevan: if you are UPDATING a running install,. use apt-get update && apt-get upgrade. The dist-upgrade is to go from, say, 12.10 to 13.04. Zysnc will refresh (or create) and ISO already on your system. They have different uses depending on the circumstances.15:19
ClassBotjlking3_ asked: So you manually compare the MD5 checksums?15:19
ClassBotThere are 10 minutes remaining in the current session.15:20
phillwVasudevan: if you use zsync to update an ISO, it will automatically do the md5sum check for you.15:21
phillwsorry that was for jlking3 :)15:22
phillwQUESTION : Thnaks, in terms of download which is faster - apt-get upgrade or zsync - over dsl conn?15:24
phillwVasudevan: I've never compared them, so cannot answer that, sorry.15:24
ClassBotThere are 5 minutes remaining in the current session.15:25
phillwapt-get update & upgrade for use on an already installed system, zsync is to get the ISO to install a system.15:25
phillwThanks everyone for attending and for the questions. Happy testing :D15:28
phillwThe next session start at 21:00 UTC / GMT, and it's me up 1st :)15:29
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html15:30
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || No Sessions Currently in Progress
=== H is now known as Guest46344
varg1کسی اینجا هست که فارسی بلد باشه و جواب من رو بده؟20:49
=== sebbu2 is now known as sebbu
=== ajmitch_ is now known as ajmitch
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: An introduction to bug reporting - Instructors: phillw
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html following the conclusion of the session.21:00
phillwHi everyone, my name is Phill. Whiteside and I'm the QA Team leader for lubuntu21:00
phillwThis session is to briefly outline two systems of bug reporting with the development releases21:01
phillwFirstly, why report a bug?21:01
phillwFor the testers, Often we are using the latest, unmodified alpha code for various projects during the development release21:02
phillwdo NOT assume someone else will report a bug!21:02
phillwAnother important thing to remember is that Discussing a bug on IRC, email, forum or facebook areas etc. does not raise a bug. The devs do not monitor those areas21:03
phillwBy all means use them to discuss a problem. Once your discussion about the bug is at a stage where you can report it, then for it to be actioned by the devs you must raise a bug.21:03
phillwWhen 12.04 came along, it had added in an extra system for automated reporting of crashes.21:03
phillwIt is still being enhanced.21:04
phillwBut, there were blog reports of 'Canonical spying on your system', this is untrue.21:04
phillwThe system that runs is called whoopsie and reports to launchpad and if you 'say yes' also to errors.ubuntu.com21:06
phillwit keeps an eye on your /var/crash area and if it sees something arrive, it springs into action21:06
phillwApport actually writes the crash file to /var/crash and if the release being run is the development release of Ubuntu, the .crash files is submitted to Launchpad21:07
phillwit also looks out for .crash files as well. (i.e. not generated by apport).21:08
phillwWhoopise is an ongoing and active project. Fuller details all about it can be found at https://wiki.ubuntu.com/ErrorTracker21:08
phillwFor most of running test cases, we will still use apport (ubuntu-bug)21:09
phillwgoing onto launchpad and manually creating a bug often results in a bug report that can not be actioned owing to a lack of information.21:09
phillwthe best way to prevent this is to use the ubuntu-bug command.21:09
phillwFor bugs that happen at install time, it can be a bit difficult to work out what to raise the bug against.21:10
phillwTo this end, for testing of ISO's a quick list can be found at https://wiki.ubuntu.com/QATeam/Overview/Install_Bugs21:10
phillwSo, if the error occurred whilst trying to install an iso, you would issue the command ubuntu-bug ubiquity21:10
phillwif you are testing an application, e.g. GClac and it failed, you would issue the command ubuntu-bug gcalc21:11
phillwusing ubuntu-bug ensures that as much information relevant to the bug is obtained and put onto the bug report.21:11
phillwAgain, there is a full explanation at https://wiki.ubuntu.com/Bugs/FindRightPackage21:11
phillwIf you are unsure on what package to allocate a bug against, please feel free to ask on #ubuntu-bugs and one of the people there will be more than happy to assist.21:11
phillwincomplete bugs do take time up which could be better spent actually dealing with bugs.21:12
phillwBrian will be  holding  a session immediately after this introduction to explain this further.21:12
phillwby the way, please do feel to ask Questions, but I will get as much covered as I can, which should leave ~ 10 mins at the end for a Q & A session21:13
phillwWithin the quality team, we have a brief section on the basics of bug reporting as it affects quality. This can be found at https://wiki.ubuntu.com/QATeam/Overview#Bugs21:13
phillwThat's the basics covered, last time I ran this, there were a couple of questions - which I will now cover.21:14
phillwMy bug goes to Private, what does it mean?21:15
phillwUsually, when a bug is marked "Private" there's some good reason for it.  With a lot of segfault (crash) bugs I see, a lot of them get marked as private, either because they contain information that *could* be private or could identify your system, or similar reasons21:15
phillwTypically, I see this with bugs which have core dumps or tracebacks which could contain information to identify someone: passwords, account numbers, etc. fall in the category of information that needs to be "removed" from the bug before it goes to a public view.21:15
phillwThose private bugs are therefore exactly what they are: hidden from the public eye until someone's gotten to it and actually looked through to see if there's anything that needs removal on those bugs, and then we usually make the bug visible after such things.21:15
phillwAlso, The bot that goes looking for duplicated bugs does not worry if the bug it is using as master is private. If this happens please go to #ubuntu-bugs and raise it with them21:16
phillwWhat about reporting kernel bugs, could it be a duplicate?21:16
phillwFor kernel bugs, *always* report a new one. It is difficult to say, a priori, if your affected system is *identical* with another in an already reported bug21:17
phillwThere is a 3rd type of bug, in the test cases... This is to report an error in the test case (Typo, things out of order in the sequence etc).21:18
phillwon each test case, for example, http://iso.qa.ubuntu.com/qatracker/testcases/1301/info21:18
phillwit is not for reporting bugs found by using the test case, but only in the test case itself (these are written by humans, and we do make mistakes, even with over sight and proof reading :) )21:19
ClassBotThere are 10 minutes remaining in the current session.21:20
phillwThat sums up all I have to say, Brian will be following. Please feel free to ask questions21:20
ClassBotThere are 5 minutes remaining in the current session.21:25
phillwWell, thanks for attending. I hope it was of use to you.... I'm never sure if no questions means I've covered it all - or scared everyone away :)21:28
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Filing and following up a good bug report - Instructors: bdmurray
bdmurrayHi, I'm Brian Murray an ubuntu developer and leader of the Ubuntu Bug Squad.21:30
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html following the conclusion of the session.21:30
bdmurrayI'd like to elaborate a bit more on what philw waid regarding reporting bugs.21:31
bdmurrayubuntu-bug is useful for reporting bugs about specific packages via the command 'ubuntu-bug' and the name of the package21:31
bdmurrayHowever, sometimes you don't always know the name of the package.  Like what is the name of the package for the "Software Updater".21:32
bdmurrayIn that case you can use "ubuntu-bug -w" and then a dialog will appear indicating that you should click on the window for the problem application21:33
bdmurrayapport will then gather information about your system and the application to add to a new bug report21:33
bdmurrayIts also possible to use apport with symptoms for example if you are having an issue with an USB disk drive.  You can use 'ubuntu-bug storage'.21:34
bdmurrayThis will run through a series of tests to determine which package is the problem and then open a bug report about that package.21:34
bdmurrayAdditional symptoms live in /usr/share/apport/symptoms/ and include issues as vague as audio and display.21:35
bdmurrayAs you can see ubuntu-bug is a great help when reporting bugs, but is also a great help for us developers as detailed information about your system and specific information for the package is gathered.21:36
bdmurrayHowever, having said that there is still one critical bit of information missing!  Detailed steps to recreate the bug report.21:37
bdmurrayWhen I say detailed steps I really mean a list like21:37
bdmurray1) click on the file menu21:37
bdmurray2) choose print21:37
bdmurray3) click on this other thing21:38
bdmurray4) watch it explode!21:38
bdmurrayThis makes it easy for us to follow the same steps with little confusion21:38
bdmurrayAdditionally, an important part of the bug life cycle is having a bug confirmed21:38
bdmurraythis also allows another Ubuntu user to come along and see your bug and follow the same steps you did and if they get the same result, confirm the bug report21:39
bdmurrayIt also helps for us to know how often the problem occurs.  Was it one in every ten attempts to scan something?21:42
bdmurrayOr did it happen every single time?21:42
bdmurrayI believe philw already mentioned this but is ususally best to open new bug reports rather than possibly adding additional issues to an existing bug report.21:44
bdmurrayHaving said that if you do find a bug that you think is about the same issue please mention it in the bug you are filing, either in the description or as an additional comment.21:44
bdmurrayIt is also important to know that every issue you may experience should be a separate bug report.  We don't want to hear about your printer and your DVD drvie in the same issue as they are unlikely to be related or be fixed with the same change.21:46
ClassBotballoons asked: does that mean I can use ubuntu-bug and say something like ubuntu-bug display or ubuntu-bug graphics if I'm having graphical issues, and ubuntu-bug audio for audio issues, etc?21:47
bdmurrayballoons: yes, you can use 'ubuntu-bug display' to help you file a bug about graphic issues and the same is true for audio issues.21:48
bdmurrayIt's pretty neat, feel free to give a try, just don't send the bug to Launchpad!21:48
bdmurray(There will be a final confirmation dialog where you can review the details of the bug report.)21:49
bdmurrayLet's say we've filed bug 1192332 and want to see what other bugs there are reported about update-manager21:49
bdmurrayYou can find them by clicking on update-manager (Ubuntu) in the "Affects" table21:50
ClassBotThere are 10 minutes remaining in the current session.21:50
bdmurrayOr by click on the word Bugs next to Code and Blueprints21:50
bdmurrayThen you could review those new bug reports about the package and see if you can confirm them.21:51
bdmurrayA bug can be confirmed when you can recreate the same issue.21:51
bdmurrayYou can confirm a bug by clicking the pencil next to "This bug affects you"21:52
bdmurrayor by clicking the pencil next to the bugs status in the "Affects" table21:52
bdmurrayYou can learn more about confirming a bug here21:53
bdmurrayAlso keep in mind that bug reports can frequently be dialogs between developers and testers.21:53
bdmurrayAs such watch for additional requests for information or testing and reply promptly.21:54
ClassBotThere are 5 minutes remaining in the current session.21:55
bdmurrayAnother part in the bug life cycle process is verifying that fixes actually work and as someone experiencing the issue you are in a good position to do that.  As I understand it that will be covered in the next section.21:56
ClassBotballoons asked: is there a recommended way to filter bugs against a package that one might be interested in? for example, I see 1700 bugs for update-manager at the moment.21:56
bdmurrayI'd generally use the search box.  For example I was looking for configuration file prompts so I typed in 'conf file' in the dialog and clicked search and found some good results.21:57
bdmurrayOne can also filter on bug tags by clicking on advanced search21:57
bdmurraygenerally bugs are tagged with the release code name (e.g. saucy) so you could search for bugs affecting saucy21:58
bdmurraywell really reported from saucy21:58
bdmurrayany other questions?21:58
bdmurrayI'm available in #ubuntu-bugs most of the time21:58
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Verifying SRU updates - Instructors: chilicuil
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html following the conclusion of the session.22:00
chilicuilmy name is Javier Lopez http://wiki.ubuntu.com/~chilicuil22:00
chilicuilthis session will be practical so prepare your lp id and terminal =)22:01
chilicuilI made some slides, you can fetch them from: http://people.ubuntu.com/~chilicuil/pdf/sru-updates.pdf22:01
chilicuilif you have any question at any point feel free to ask in the #ubuntu-classroom-chat channel and I'll be glad to answer them22:02
chilicuilso, to begin22:02
chilicuila SRU is a proposed update which has already been accepted in the ubuntu dev version and now is trying to make its way to a stable release (precise, quantal or raring)22:03
chilicuilnot every update is candidate for SRU, to become a SRU an update needs to:22:04
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Current Session: Verifying SRU updates - Instructors: chilicuil - Slides: http://is.gd/GFWXJ1
chilicuil  * fix a severe regression22:04
ClassBotSlides for Verifying SRU updates: http://people.ubuntu.com/~chilicuil/pdf/sru-updates.pdf22:04
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html following the conclusion of the session.22:04
chilicuil  * fix a program which loss user data22:04
chilicuil  * be simple and safe22:05
chilicuilthis page summarize all the details: https://wiki.ubuntu.com/StableReleaseUpdates22:05
chilicuilso why stable ubuntu versions have a different policy?22:05
chilicuil *stability*22:06
chilicuilin the past even one liner fixes have brought important issues, bugs #81125, #309674 and #559822 are some examples22:06
chilicuilso we're trying to ensure updates archived in -updates don't break everything =)22:07
chilicuilunfortunately, this policy has an issue22:07
chilicuilif no one actually test that a proposed update is good enough to get copied to stable releases, it could stay at -proposed starving for ever =(22:08
chilicuila complete list of current -proposed updates can be found here: http://people.canonical.com/~ubuntu-archive/pending-sru.html22:08
chilicuilif you open the link, you'll see that there are updates for all stable releases, lucid, precise, quantal and raring22:09
chilicuiland once saucy get released, proposed updates will be visible there before any other place22:10
chilicuilblue and green updates are optimal to test22:10
chilicuilI'd like that we test a couple of them right now22:11
chilicuilyou won't need many things, and it's relative easy to do22:13
chilicuilyou'll require:22:13
chilicuil* any stable ubuntu release, I'll asume raring for this example22:13
chilicuil * a lp account22:14
chilicuil * optionally, pbuilder, virtualbox or a spare machine22:14
chilicuilthere are chances that a proposed update could be really wrong and burn your machine, but tipically that's not the case22:15
chilicuilpersonally, I use pbuilder for testing cli applications and virtualbox for apps with a graphical interface22:15
chilicuilhowever, right now, I'll test directly on my main machine, since I've picked a safe update to test =P, and because I don't want to overcomplicate the example, learning pbuilder and virtualbox require a session for themselves22:17
chilicuilif you don't have a lp account you can create one in a couple of minutes: https://launchpad.net/+login22:17
chilicuilI'll wait here for those who don't have one =)22:18
chilicuilok, I'll assume you've created a lp account, let's review some of the pending updates: http://people.canonical.com/~ubuntu-archive/pending-sru.html22:22
chilicuilas you can see, there are plenty of opportunities to help22:22
chilicuilfor now I'd like that we could focus on software-properties, specifically bug #104742422:23
chilicuilthis report was opened to fix a problem with the additional drivers dialog22:24
chilicuilreports related to a sru are exceptional good, so it's generally easy to follow instructions22:24
chilicuilif they're not clear enough you can put a comment in the report and add the tag: 'verification-failed'22:25
chilicuilthe 'test case' section is specially helpful so try to not overlook it22:25
chilicuilwhen a sru is requested, and it's accepted, members of the sru team, add the 'verification-needed' tag, our work as part of the QA team is to change those tags for 'verification-done' | 'verification-failed' depending of the result of our tests22:26
chilicuilbefore going further, I recommend to upgrade the system22:26
chilicuil$ sudo apt-get update && sudo apt-get upgrade22:26
chilicuileven if you use pbuilder or virtualbox, is generally a good idea to make sure we have the latest updates before testing any SRU22:27
chilicuilI'll give a couple of minutes for those who want to follow the live SRU testing session and need to update their machines22:28
chilicuilin the meantime, I'll talk more about the SRU reports22:29
chilicuilwhen you open a SRU report, you'll usually see these sections: [Impact], [Test case], [Regression potential], [Original description]22:30
chilicuilthe Impact section refers to the main problem, why this SRU should be introduced to stable releases22:31
chilicuilthe [Test case] sections usually have instructions step by step to reproduce the bug, it's a mandatory section, so you can be feel safe to find clear instructions22:33
chilicuilthe [Regresssion potential] section list some issues who could appear after adding this update, the less the better22:34
chilicuilfinally the [original section], well, it has the original post for reference22:35
chilicuilnow, I'll asume we had enought time to update our systems, so we can look at the report #1047424 and see how if we can reproduce the bug22:36
chilicuilso the bug refers to a incorrect dialog after installing any driver using the software properties application22:37
chilicuilwe'll launch the application by typing 'drivers' at the dash and selecting 'Software & Updates'22:38
chilicuilafter opening it, we can click the latest tab 'Additional Drivers' and install or remove a driver, let's do it22:39
chilicuilyou don't need to worry, we won't reboot our systems, so if you don't have a driver to install, remove one, we'll reinstall it before leaving the session22:40
chilicuilafter selecting one driver we can press 'Apply changes', this will triage the installation|uninstalling process22:41
chilicuilafter doing it, you'll see a 'Restart ...' button22:41
chilicuila dialog asking for confirmation will appear, and it'll only have 'cancel' and 'shutdown' as options, that's the bug!22:42
chilicuilinstead of asking for shutting down the system, it should ask for rebooting22:42
chilicuilso, we've confirmed the issue22:42
chilicuilso, once we've seen the bug, we'll apply the -proposed update22:43
chilicuildetailed instructions are here: https://wiki.ubuntu.com/Testing/EnableProposed22:43
chilicuilthe fastest to do it IMO is to modify /etc/apt/sources.list22:44
chilicuilso, if you don't feel like reading the wiki right now, you can trust me and run:22:44
chilicuil$ echo 'deb http://mx.archive.ubuntu.com/ubuntu/ raring-proposed main restricted multiverse universe' | sudo tee /etc/apt/sources.list.d/proposed.list22:44
chilicuilthat command will create a file in /etc/apt/sources.list.d/proposed.list with the following 'deb http://mx.archive.ubuntu.com/ubuntu/ raring-proposed main restricted multiverse universe'22:45
chilicuilapt uses those files to know from where to pull software22:46
chilicuilafter adding the proposed repository the system needs to update the index and apply the updates22:46
chilicuil$ sudo apt-get update && sudo apt-get install software-properties-gtk22:46
chilicuilthose commands will download the new index and after that will update the software-properties-gtk program, sudo apt-get install can install or update (if the package is already installed)22:47
chilicuilafter completing the last step, it's time to retry the dialog22:48
chilicuilclose the 'Software & Updates'22:49
chilicuiland then open it again, go the driver tab and renable the uninstalled driver22:49
ClassBotThere are 10 minutes remaining in the current session.22:50
chilicuilone hint to know that you applied correctly the update is that after executing sudo apt-get install software-properties-gtk you should see your computer downloading a package from -proposed22:50
chilicuilif you don't see it, something went wrong, and you should review your /etc/apt/sources.list.d/proposed.list file22:51
chilicuilso, once you've applied the proposed update, you need to follow the test case steps and ensure the issue has gone22:52
chilicuilif you are following this example, you should see that after applying the driver installation and selecting the 'Restart...' button you'll see this time a dialog with two buttons, 'cancel' and 'reboot'22:53
chilicuilthe -proposed update works!22:53
chilicuilthat's it, that's exactly what SRU testing is about22:54
chilicuilso, once we've tested and confirm that the proposed update fixes the reported issue, we can add comments, those who completed the sru testing, please do so22:54
ClassBotThere are 5 minutes remaining in the current session.22:55
chilicuilsomething like, 'the proposed update work in Ubuntu raring amd64' should be enough22:55
chilicuiland don't forget to add the appropiate tag, in this case, 'verification-done'22:55
chilicuilafter completing all these steps a member of the SRU team will review the report and probably will copy the -proposed update to -update, after that, a lot of people will improve its Ubuntu experience22:57
chilicuilif have any problem while doing SRU testing feel free to ping me, or to join #ubuntu-quality22:58
chilicuilif you*22:58
chilicuilI think that's all, any question?22:58
chilicuilthanks Skini151, you rock!22:59
ClassBotLogs for this session will be available at http://irclogs.ubuntu.com/2013/06/24/%23ubuntu-classroom.html23:00
=== ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || No Sessions Currently in Progress

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!