test-announce May 2018

test-announce@lists.fedoraproject.org

4 participants
15 discussions

Fedora 29 Rawhide 20180506.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 06 May '18

06 May '18

Announcing the creation of a new nightly release validation test event for Fedora 29 Rawhide 20180506.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: pungi - 20180503.n.0: pungi-4.1.24-1.fc29.src, 20180506.n.0: pungi-4.1.24-2.fc29.src lorax - 20180503.n.0: lorax-29.1-1.fc29.src, 20180506.n.0: lorax-29.2-1.fc29.src python-blivet - 20180503.n.0: python-blivet-3.0.0-0.6.b1.fc29.src, 20180506.n.0: python-blivet-3.1.0-0.1.b1.fc29.src anaconda - 20180503.n.0: anaconda-29.13-1.fc29.src, 20180506.n.0: anaconda-29.14-1.fc29.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/29 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_29_Rawhide_20180506.n.0_… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_29_Rawhide_20180506.n.0_… https://fedoraproject.org/wiki/Test_Results:Fedora_29_Rawhide_20180506.n.0_… https://fedoraproject.org/wiki/Test_Results:Fedora_29_Rawhide_20180506.n.0_… https://fedoraproject.org/wiki/Test_Results:Fedora_29_Rawhide_20180506.n.0_… https://fedoraproject.org/wiki/Test_Results:Fedora_29_Rawhide_20180506.n.0_… https://fedoraproject.org/wiki/Test_Results:Fedora_29_Rawhide_20180506.n.0_… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

Proposal to CANCEL: 2018-05-07 Fedora QA Meeting
by Adam Williamson 05 May '18

05 May '18

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't see anything particularly urgent to discuss, so let's take the time off. If you're aware of anything important we have to discuss this week, please do reply to this mail and we can go ahead and run the meeting. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

Fedora 29 Rawhide 20180503.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 03 May '18

03 May '18

1 0

[Fedora 28] Test Day Retrospection
by Sumantro Mukherjee 02 May '18

02 May '18

Hey All, First of all, thanks for spending some time and contributing to Fedora 28 Test Days. This was by far the *most-engaging* testday season with 11 Test Days and 201 Testers executing 925 Test cases. Last Flock, we approched the Kernel folks to run a test day with for every new kernel rebase and we are happy to say, we get it tested throughly! Most particpated Fedora 28 Test Days: Test Day:2017-11-30 Kernel 4.14 Test Day Testers: 49, Tests: 57 Test Day:2018-02-22 Kernel 4.15 Test Day Testers: 42, Tests: 64 Test Day:2018-04-13 Kernel 4.16 Test Day Testers: 32, Tests: 41 Test Day:2018-04-19 Upgrade Test Day Testers: 60, Tests: 103 For every release we have: 1. Gnome Test Day 2. I18n Test Day 3. Cloud Test Day 4. Kernel Test Day 5. Upgrade Test Day We want to increase this list with coming releases by adding more of release-blocking and mostly-used features/apps/changes apart from changeset of the current release. Thoughts that echoed throughout the F28 test day cycle: 1.Test days to run as async event (not bound to any release) 2.All Test days to kick off as soon as change sets are final(for changesets) 3.Test Day images needs to be squeezed to as minimal as possible 4.Try to set the test-cases and posts well in advance. There are many who post it for regional communities and an annoucement well in advance helps them.

1 0

[Fedora 29] Call for Test Days
by Sumantro Mukherjee 02 May '18

02 May '18

Hey All, Another testing cycle is finally upon us, and it's about time we got some Test Days scheduled/planned for the F29 cycle. This cycle has major changes and could use some testing love - a full list can be found here: http://fedoraproject.org/wiki/Releases/29/ChangeSet F29 also has several self-contained changes that could use some testing. So my thought was if there were things people would like to get tested, but didn't think it warranted an entire day - then we could group these together and run a test day to poke at several different things at the same time. For those of you not familiar with test days, a test day is an online event aimed at testing a specific a feature of an upcoming Fedora Release.By utilizing IRC for organization/coordination and a Wiki page for instructions and results, test days are easy to organize. Anyone can request to host a test day or request that the QA team help you out with the organization of the test day. A test day can run for any feature or area of a distribution that focused testing would be useful for. More information on test days can be found here: https://fedoraproject.org/wiki/QA/Test_Days To propose a test day, file an issue on Pagure[https://pagure.io/fedora-qa/issues] with F29 as Milestone. A full explanation can be found here: https://fedoraproject.org/wiki/QA/Test_Days/Create The SOP for hosting a test day is here: https://fedoraproject.org/wiki/QA/SOP_Test_Day_management If you have any questions about test days or the process, please don't hesitate to contact me or any other QA Team member in #fedora-qa on Freenode or respond on the test list. Thanks and happy testing! Thanks //sumantro freenode : sumantro

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce May 2018