Thanks a lot for getting back to me. Alright now to answer you questions :) I have been working with my mentor, av` (Andrea Veri) who has been teaching me mergers, basic packaging and such so that involves using fakeroot and installing the required packages is thus taken care of. For reproducing bugs, I have done a lot of that, for example I confirmed a bug regarding evolution mail and then send it upstream which is going to get fixed in the next GNOME release. I have also filed a lot of different bugs [1], now is the part where I need your help: like you said in the messae, SRU team get a lot of bugs in the email. This helps me focus on something rather than wandering in launchpad. I am going to start working with SRUVerification from the queue and see how that goes. One of the biggest reasons I want to join SRU verification is to get more involved in the bug work and get better at it :)
[1] https://bugs.edge.launchpad.net/~dhillon-v10 -- Regards, Vikram Dhillon On Tue, 2009-12-08 at 00:29 -0800, Steve Beattie wrote: > Hi Vikram! > > On Fri, Dec 04, 2009 at 11:20:24PM -0500, Vikram Dhillon wrote: > > How is everyone doing? I have been a member of Ubuntu testing > > team, but I just learned how to test ISO's and such for releases. > > That's great. Lucid Alpha 1 is coming this week, so any help you can > give on that front will be appreciated. > > > I understand packaging software in Ubuntu, so I wanted to join SRU > > Verification team to take on more responsibility and learn more. Please > > give me more guidance on what steps do I need to take further. > > Sure, thanks for your interest. For the record, SRUs are > Stable Release Updates, and SRU Verifications are the process > we go through to verify a proposed SRU so that it can be > released as an update. The SRU process is documented at > <https://wiki.ubuntu.com/StableReleaseUpdates>. > > SRU verification is a great way to participate in the Ubuntu project > as well as learn more about the software itself. Basically, what we'd > like to see for membership in sru-verification is a demonstration of > understanding of how to perform an SRU verification, typically in > the form of some example bugs where feedback was given (similar to > the bugcontrol team application process). > > Basically, an applicant needs to demonstrate that they're able to: > > 1) install the relevant software packages, > 2) attempt to reproduce the bug (hopefully successfully) > 3) install the versions from the -proposed pocket > 4) again, attempt to reproduce the bug (hopefully failing), > 5) look for regressions introduced by the update > > In your case, I'm unable to find any any such feedback in any of the > bug reports that the sru-verification is subscribed to; if you could > point me to some examples, I'd be happy to approve your membership. > (Fair warning, the sru-verification team is subscribed to a large > number of bug reports, and thus gets a non-trivial amount of > bugmail. Filtering incoming email is recommended.) > > There are other ways to contribute to the sru-verification team; > currently, there are a couple different web pages we use to track > which packages are in the proposed queue: > > http://people.canonical.com/~ubuntu-archive/pending-sru.html (archive admin > view) > http://people.canonical.com/~sbeattie/sru_todo.html (mostly covering main) > > Unifying and improving those would appreciated, > as well as helping to improve the documentation at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification > would be greatly appreciated. > > Thanks again for your interest! >
signature.asc
Description: This is a digitally signed message part
-- Ubuntu-qa mailing list Ubuntu-qa@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa
