May 2017 - test-announce - Fedora Mailing-Lists

by Mohan Boddu

Hi all, Today is an important day on the Fedora 26 schedule[1], with two significant cut-offs. Today is the Beta freeze[2]. This means that only packages which fix accepted blocker or freeze exception bugs[3][4] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Finally, Today is the '100% code complete deadline' Change Checkpoint[5], meaning that Fedora 26 Changes must now be code complete, meaning all the code required to enable to the new change is finished. The level of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested by this deadline'. Regards Mohan Boddu [1] https://fedoraproject.org/wiki/Releases/26/Schedule [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://fedoraproject.org/wiki/Changes/Policy

6 years, 11 months

1
0
0 / 0

2017-05-15 ** Blocker Review Proposal to CANCEL

by Mike Ruckman

Greetings testers! We don't have any proposed blockers for Beta or Final right now, so I propose that we cancel tomorrows meeting. If you find a blocker or want to discuss something, please reply to this thread and we'll have the meeting! Thanks! // Mike -- Fedora QA

6 years, 11 months

1
0
0 / 0

Fedora 26 Branched 20170513.n.0 nightly compose nominated for testing

by rawhide＠fedoraproject.org

Announcing the creation of a new nightly release validation test event for Fedora 26 Branched 20170513.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: anaconda - 20170504.n.1: anaconda-26.21.4-1.fc26.src, 20170513.n.0: anaconda-26.21.6-1.fc26.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/26 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_26_Branched_20170513.n... The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513.n... Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

6 years, 11 months

1
0
0 / 0

2017-05-15 @ 15:00 UTC - Fedora QA Meeting

by Adam Williamson

# Fedora Quality Assurance Meeting # Date: 2017-05-15 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We haven't met for a bit, and we're coming up on the Beta freeze, so let's have a quick check-in! We've had several new folks come along lately, so perhaps running another onboarding session would be a good idea; we can talk about that, and if you're new, please do come along and say hi if the time is convenient! If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 26 status 3. Test Day status 4. New member welcome / onboarding 5. Open floor -- adamw

6 years, 11 months

1
0
0 / 0

REMINDER: Fedora 26 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze in 1 week

by Jan Kurik

The next Tuesday, on 2017-May-16, we will reach two important milestones of the Fedora 26 release [1]: == Change Checkpoint: 100% Code Complete Deadline [2] == * New accepted changes must be code complete, meaning all the code required to enable to the new change is finished. * The level of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested by this deadline. == Beta Freeze [3] == Only packages which fix accepted blocker or freeze exception bugs [4] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. [1] https://fedoraproject.org/wiki/Releases/26/Schedule [2] https://fedoraproject.org/wiki/Changes/Policy [3] https://fedoraproject.org/wiki/Milestone_freezes [4] https://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

6 years, 11 months

1
0
0 / 0

Proposal to CANCEL: 2017-05-08 Fedora QA Meeting

by Adam Williamson

Hi folks! I'm proposing we cancel the QA meeting tomorrow, unless someone else wants to run it. I'm on my way back home from Linuxfest Northwest and will be getting in pretty late, and I'm not sure I'm going to make it up to run a meeting. If anyone would like to volunteer to run the meeting, please just go ahead and send out an agenda. Remember, we do have the blocker review meeting at 1600 UTC! Some dates for your diary: Beta freeze is 2017-05-16, and Beta Go/No-Go is scheduled for 2017-05-25. So we need to be checking the Beta matrix coverage is good and finding any yet-unfound Beta blockers now. I'll send out a blocker status mail soon, and check for missing test coverage too. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

6 years, 11 months

1
0
0 / 0

2017-05-08 @ 16:00 UTC ** Blocker Review Meeting

by Mike Ruckman

# F26 Blocker Review meeting # Date: 2017-05-08 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net It's that time of the week again! We've got 4 proposed blockers for Beta that we need to look through. If you have time between now and Monday to go through the list of blockers, please do so. You can find the full list here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F26 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria // Mike -- Fedora QA

6 years, 11 months

1
0
0 / 0

[Test Day] DNF 2.0 2017-05-09

by Sumantro Mukherjee

Hey Testers, Tuesday 2017-05-20 will be DNF 2.0[1] Test Day! As part of this planned Change[2] for Fedora 26, So this is an important Test Day! Test Day will focus on testing DNF. DNF-2.0 is the next upcoming major version of DNF package manager. DNF-2 is the upstream DNF version, the only version actively developed. Currently the upstream contains many user requested features, increased compatibility with yum and over 30 bug fixes. To DNF-1 back porting of patches from upstream is difficult and only critical security and usability fixes will be cherry-picked to Fedora. With DNF 2.0 in places,users can notice usability improvements of DNF like better messages during resolution errors, showing whether package was installed as weak dependency, better handling of obsolete packages, less tracebacks, etc. We hope to see whether it’s working well enough and catch any remaining issues. As always, the event will be in #fedora-test-day on Freenode IRC. [1]: https://fedoraproject.org/w/index.php?title=Test_Day:2017-05-09_DNF_2.0 [2]: https://fedoraproject.org/wiki/Changes/DNF-2.0 Thanks //sumantrom

6 years, 11 months

1
0
0 / 0

Fedora 26 Branched 20170504.n.1 nightly compose nominated for testing

by rawhide＠fedoraproject.org

Announcing the creation of a new nightly release validation test event for Fedora 26 Branched 20170504.n.1. 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: anaconda - 20170420.n.0: anaconda-26.21.3-1.fc26.src, 20170504.n.1: anaconda-26.21.4-1.fc26.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/26 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_26_Branched_20170504.n... The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170504.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170504.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170504.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170504.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170504.n... https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170504.n... Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

6 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce May 2017