On Sun, Jul 10, 2016 at 9:48 PM, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
Yes , it does. Now let me put forward the actual idea of having an QA sprints succeeding an onboarding call. As Adam mentioned we have many new contributors coming in and hence there was a need to ensure that the packages are being tested correctly . Over a span of 2+ weeks the new contributors have been testing packages and collectively we tested about 1000 packages for Fedora 24. To ensure that everything is fine, I have asked a few of them to not give karma and wait until I check and ensure the testing was proper. In the QA sprint, I ensured that the packages were tested properly by all the people who were taking part. Except for a few packages , everything went pretty fine! .
Sayan's Package was working fine for F24 ( I didn't still test for F23, although I do see one on Bodhi) , I verified it already.Although we might need to work out on the https://fedoraproject.org/wiki/QA:Update_feedback_guidelines to ensure new contributors become well aware when they post feedbacks.
On Sun, 2016-07-10 at 21:30 +0530, Sayan Chowdhury wrote:
> Hi,
>
> I recently packaged and pushed an update for fedmsg-meta-fedora-infrastructure
> to bodhi and exactly 40 secs[1] later I got a +1 to the update. I am sure that
> testing a package surely takes more than 40 secs. This makes me really curious
> that are the packages really being tested before giving out the karma.
>> After going through messages in datagrepper[2][3], I found that few people are
> giving out karma in one go (4-5 packages under a minute). If these packages
> really are not-tested and the karma are given out randomly then I am sure that
> this sure going to affect the release, infrastructure and our users.
>
> Does anybody know what is going on?
There was a testing sprint run by Sumantro recently, and generally he's
been signing up a lot of new testers. Sumantro, can you please check
and make sure folks are properly testing these updates? This update for
instance is involved in producing human-readable forms of fedmsgs; it
would actually be quite complex to test properly, I believe, as you
would need to have a whole test fedmsg hub set up.
"Install the package and see if the system breaks" is an appropriate
form of testing for some packages, but not all, many are not at all
related to typical desktop system functionality. Folks do need to make
sure they understand what a package is for and have actually tested its
functionality before posting feedback.
I do note that the 'Positive feedback' section of
https://fedoraproject.org/wiki/QA:Update_feedback_guidelines is a
little simplistic here, and I'll try to update that.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
Yes , it does. Now let me put forward the actual idea of having an QA sprints succeeding an onboarding call. As Adam mentioned we have many new contributors coming in and hence there was a need to ensure that the packages are being tested correctly . Over a span of 2+ weeks the new contributors have been testing packages and collectively we tested about 1000 packages for Fedora 24. To ensure that everything is fine, I have asked a few of them to not give karma and wait until I check and ensure the testing was proper. In the QA sprint, I ensured that the packages were tested properly by all the people who were taking part. Except for a few packages , everything went pretty fine! .
Sayan's Package was working fine for F24 ( I didn't still test for F23, although I do see one on Bodhi) , I verified it already.Although we might need to work out on the https://fedoraproject.org/wiki/QA:Update_feedback_guidelines to ensure new contributors become well aware when they post feedbacks.
Thanks
Sumantro
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
