test-announce December 2013

test-announce@lists.fedoraproject.org

6 participants
21 discussions

Proposal to CANCEL: 2013-12-30 Fedora QA Meeting
by Adam Williamson 30 Dec '13

30 Dec '13

Apologies for the late notice - somehow kept never getting around to this... We have a meeting slot today (2013-12-30) at 1600 UTC as usual, but I'm proposing we cancel the meeting. I don't think we have anything significant to discuss at present - Fedora's been quiet over the holidays as usual. If anyone thinks there's a strong reason to have a meeting, please reply! Otherwise I guess we'll go ahead and skip this week. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

2013-12-23 @ 16:00 UTC - Fedora QA Meeting
by Adam Williamson 19 Dec '13

19 Dec '13

# Fedora Quality Assurance Meeting # Date: 2013-12-23 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We have a meeting slot on 12-23 - it's two days before Christmas, but lots of keen cookies expressed an interest in having the meeting, so let's do it. We can't do broad Fedora 21 planning at present, but we can look at the Fedora 20 FedUp issue, and perhaps talk about storage validation a bit. Please suggest any other topics for discussion! This is a reminder of the upcoming QA meeting. Please add any topic suggestions to the meeting wiki page: https://fedoraproject.org/wiki/QA/Meetings/20131223 The current proposed agenda is included below. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. FedUp post-mortem 3. Storage validation 4. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Reminder: Fedora 18 end of life on 2014-01-14
by Dennis Gilmore 18 Dec '13

18 Dec '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings. This is a reminder email about the end of life process for Fedora 18. Fedora 18 will reach end of life on 2014-01-14, and no further updates will be pushed out after that time. Additionally, with the recent release of Fedora 20, no new packages will be added to the Fedora 18 collection. Please see http://fedoraproject.org/wiki/DistributionUpgrades for more information on upgrading from Fedora 18 to a newer release. Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJSsiEoAAoJEH7ltONmPFDRwrEQAI59+ExbyhZrgr+K/iTDIvWV LaDHsBsaDeQhV1IxgKN/H0fA84r+LiFTK6/+A5dBt28w9PpxFGGeDUmAF8Gvn3bx Jlz+6MeuHt+Z3xJ6wRjIwjt7jGGG936tGk4Se/sbHYf33qyRid5gyGEYWHPFK2fV HSt2/mh9+PTBcQzVbQBOimJsdvGO71FTBCqZBHhapctVsNnCQAGrnetb/yoPqAHY Sa8K87H7gAWkPswp+w1yHVA7y8gOOjFErNU456N4ZK2h/4zor+dsflchbP9CCKZg izolBKUOi1VVtaxS7wYV+l+PqV9vaa96/coi3TquLuEElwAG/HS1OzKj9gKH/xQq PfV0vCyS+CnM3KnEKcz5jr06WNlY6lDp3h6B+JiPHwlGUD1Wdu6UwSWd2NGxt9c7 bkVpjiGcBpwJMM3G9EpoMCKln/JXRkOz9mxsT/4lha+yvPvIUlpWkl7qtMM3KExH KecUA/JWc74S5a7aWLHRDc8frs1hqk7entkYtf59swFFO39DtDC20fVAm72ZHkig 8kNktOnr3Q19Mw15Dv4Q5UmLRuU36sCrFiF/23zOy7SHK26cnwWWZuCks9vZ81kR eWP/HvP7Wnu8ahMQLzgXEVyDgCraRD8vcPsYg0oAK+HTcvk/+BTdpT/b/g94JUUU h764UoIcaMf0NhSei5Yo =booW -----END PGP SIGNATURE-----

1 0

PSA: Use fedup 0.8 for upgrades to Fedora 20! (was Re: Should a working fedup in Fedora N's stable repository be a release criterion for N+1?)
by Adam Williamson 18 Dec '13

18 Dec '13

On Tue, 2013-12-17 at 21:47 -0800, Adam Williamson wrote: > On Tue, 2013-12-17 at 15:16 -0800, Andrew Lutomirski wrote: > > I have a tendency to upgrade to a new Fedora release as soon as it's > > final, and I sometimes upgrade even sooner. ISTM that the official > > upgrade process is almost always broken, often for known reasons. > > Should one of the criteria for releasing Fedora N+1 be that a > > fully-updated Fedora N must be able to successfully complete 'fedup' > > or whatever the current preferred upgrade program is? > > > > (FWIW, the current bug is particularly nasty -- fedup 0.7.0 apparently > > can't actually update anything, and the sequence: > > > > - Install fedup 0.7.0 > > - Try it and watch it fail or hang > > - Update to fedup 0.8.0 from updates-testing > > - Run fedup > > > > ends up downloading all rpms *twice* a sucking up a correspondingly > > immense amount of disk space. > > Um, I'm fairly sure it doesn't. It only re-downloads stuff that's > different from the previous run. > > We did test upgrades to F20 with 0.7, and they did work in testing, and > quite a lot of people reported success with fedup in the last two weeks > when at least some of them likely used 0.7. > > You have to bear in mind it's release day today, and there's always > weirdness on release day, and people who have success generally don't > report it while those who hit failure almost always do. I've been > advising people to upgrade to 0.8 and retry just as a kind of generic > piece of advice; for many of them, it'd probably work if they just > retried with 0.7. 0.8 does fix several bugs compared to 0.7, but 0.7 > wasn't entirely broken. Eh, that'll teach me to talk before thoroughly testing: these words are delicious! Om nom nom. I just poked it a bit and it sure seems like upgrades with fedup 0.7 to F20 are busted. They definitely worked when we tested shortly before release, though. I can only think that using fedup 0.7 against upgrade kernel/image built with fedup-dracut 0.8 doesn't work. FranciscoD also points out that the location of files downloaded by fedup changed between 0.7 and 0.8, so if you do a run with 0.7 then try with 0.8, it'll re-download all the updates, which is a waste of space and bandwidth. So, here's the news: do your upgrades to F20 with fedup 0.8, yo. It's in updates-testing for F18 and F19 at present, but will go to stable for F19 tomorrow. If you're upgrading from F18, you'll need to pass '--nogpgcheck' to fedup, because of https://bugzilla.redhat.com/show_bug.cgi?id=1040689 . If you did an unsuccessful run with fedup 0.7, then you can do: mv /var/tmp/fedora-upgrade /var/tmp/system-upgrade mv /var/lib/fedora-upgrade /var/lib/system-upgrade before running fedup 0.8, to save it downloading all the packages again, and make sure it cleans up nicely when it's done. I've just tested this, and it works. If you've already done an unsuccessful run with fedup 0.7 and then a successful run with 0.8, you may have files from the 0.7 run hanging around in /var/lib/fedora-upgrade and /var/tmp/fedora-upgrade. It is entirely safe and, indeed, advised to rm -rf these directories. Sorry for the mess, folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Announcing the release of Fedora 20.
by Robyn Bergeron 17 Dec '13

17 Dec '13

Greetings! We can say with great certainty the Fedora Project is pleased to announce the release of Fedora 20 ("Heisenbug"), which coincides with the 10th anniversary of the creation of the Fedora Project. Download this leading-edge, free and open source operating system now: http://fedoraproject.org/get-fedora Detailed information about this release can be seen in the release notes: http://docs.fedoraproject.org/en-US/Fedora/20/html/Release_Notes/index.html *** Dedicated to Seth Vidal *** On July 8, the Fedora Project lost Seth Vidal, a dedicated, tireless, and brilliant contributor. Seth was a lead developer of Yum and the Fedora update repository system. He worked to ensure that the technical and community infrastructure of Fedora worked well and consistently for users and contributors around the world. Seth touched the lives of hundreds of Fedora contributors directly and millions of others indirectly by improving the experience of using and updating Fedora. The Fedora Project dedicates the Fedora 20 release to Seth and asks that you join us in remembering his generous spirit and incredible work that helped make Fedora what it is today. We miss you, Seth. *** 10 Years of Fedora *** The Fedora 20 release coincides with Fedora's tenth anniversary. The first Fedora release (then called Fedora Core 1) came out on November 6, 2003. The Fedora Project community has grown into an active and vibrant one that produces a new version of this leading-edge, free and open source operating system around every six months. *** Desktop Environments and Spins *** The Fedora Project strives to provide the best desktop experiences possible for users, from desktop environment to application selection. We also produce nearly a dozen spins tailor-made for desktop users, hardware design, gaming, musicians, artists, and early classroom environments. Spins are available for download here: https://fedoraproject.org/wiki/Releases/20/Spins == GNOME 3.10 == Fedora 20 comes with GNOME 3.10, which has several new applications and features that will please GNOME-lovers. This release includes a new music application (gnome-music), a new maps application (gnome-maps), a revamp for the system status menu, and Zimbra support in Evolution. == KDE Plasma Workspaces 4.11 == The Fedora KDE SIG has rebased to KDE 4.11 for Fedora 20. This release includes faster Nepomuk indexing, improvements to Kontact, KScreen integration in KWin, Metalink/HTTP support for KGet, and much more. == Spins == Spins are alternate versions of Fedora. In addition to various desktop environments for Fedora, spins are also available as tailored environments for various types of users via hand-picked application sets or customizations. See all of the Fedora 20 Release Spins here: https://fedoraproject.org/wiki/Releases/20/Spins *** ARM as a Primary Architecture *** While Fedora has supported a number of hardware architectures over the years, x86/x86_64 has been the default for the majority of Fedora users and for the Linux community in general. ARM, however, has been making massive strides. It already dominates the mobile market, is becoming a go-to platform for hobbyists and makers, and is showing enormous promise for the server market as well. In keeping with Fedora's commitment to innovation, the Fedora community has been pushing to make ARM a primary architecture to satisfy the needs of users and developers targeting the ARM platform. *** Cloud and Virtualization Improvements *** The Fedora 20 release continues the Fedora tradition of adopting and integrating leading edge technologies used in cloud computing. This release includes features that will make working with virtualization and cloud computing much easier. == First-Class Cloud Images == The Fedora Cloud SIG has been working hard to provide images that are well-suited for running as guests in public and private clouds like Amazon Web Services (AWS) and OpenStack. If you're using public or private cloud, you should grab one of the downloadable Cloud Images or find a supported EC2 image, here: http://fedoraproject.org/en/get-fedora-options#clouds == VM Snapshot UI with virt-manager == Taking VM snapshots is now much easier. Though qemu and libvirt have all the major pieces in place for performing safe VM snapshots/checkpoints, there isn't any simple, discoverable UI. This feature will track adding that UI to virt-manager and any other virt stack bits that need to be fixed/improved, including adding functionality to libvirt to support deleting and rebasing to external snapshots. == ARM on x86 with libvirt/virt-manager == You can now run ARM VMs on x86 hosts using standard libvirt tools: libvirt virsh, virt-manager and virt-install. *** Big Data *** The Fedora 20 release includes all the packages you need to run Apache Hadoop 2.2.0. Hadoop is a widely used, increasingly complete big data platform with a strong, growing community and ecosystem. The Hadoop packages included with Fedora 20 will provide a foundation for immediate use of Hadoop and a base for the rest of the Apache Hadoop ecosystem. *** Developer Goodness *** As always, Fedora 20 includes new features and updated packages that will be of interest to all manner of developers. == WildFly 8 == WildFly 8 is the next version of the application server previously known as JBoss Application Server. With WildFly 8, it's possible to run your Java EE 7 applications with unparalleled speed. WildFly 8 boasts a optimized boot process that starts services concurrently to eliminate unnecessary waits and taps into the power of multi-core processors. At the same time, WildFly takes an aggressive approach to memory management and keeps its memory footprint exceptionally small compared to other JVMs. == Ruby on Rails 4.0 == This update supports Ruby on Rails developers by providing system-packaged Ruby on Rails of the latest version. Apart from that, Rails 4.0 also brings improved functionality, speed, security, and better modularization. *** Maturity and Advanced Features *** Sometimes it's not the big, new features that make a user's experience better; it's the little enhancements or long-awaited tricky features that really help make a new release the bee's knees. == NetworkManager Improvements == NetworkManager is getting several improvements in Fedora 20 that will be welcome additions for power users and system administrators. Users will now be able to add, edit, delete, activate, and de-activate network connections via the nmcli command line tool, which will make life much easier for non-desktop uses of Fedora. NetworkManager is also getting support for bonding interfaces and bridging interfaces. Bonding and bridging are used in many enterprise setups and are necessary for virtualization and fail-over scenarios. == No Default Sendmail, Syslog == In the interests of paring down services that are generally not used on desktop systems, Fedora 20 removes and replaces some services that many users find unnecessary from the Live Desktop DVD. They will remain available as installable packages for users who might need them. The systemd journal now takes the place as the default logging solution for minimal and other selected installation methods, such as the Live Desktop DVD, having been tested and able to manage persistent logging in place of syslog. Also, Sendmail will no longer be installed by default, as most Fedora installs have no need of a Mail Transfer Agent (MTA). *** Even More Changes *** Fedora prides itself on bringing cutting-edge technologies to users of open source software around the world, and this release continues that tradition. No matter what you do, Fedora 20 has the tools you need to help you get things done. A complete list with details of each new change is available here: https://fedoraproject.org/wiki/Releases/20/ChangeSet *** Documentation *** Read the full release notes for Fedora 20, guides for several languages, and learn about known bugs and how to report new ones: http://docs.fedoraproject.org/ Fedora 20 common bugs are documented here: http://fedoraproject.org/wiki/Common_F20_bugs This page includes information on several known non-blocker bugs in Fedora 20; please be sure to read it before installing! *** Contributing *** We hope that you're excited to have Fedora 20 in your hands and are looking forward to using it and exploring its new features and many improvements over Fedora 19. But that's not all! Fedora never stands still, we're always working towards a new and better release and sharing our work with the world. Want to be part of the fun? It's easy to get involved! There are many ways to contribute to Fedora, even if it's just bug reporting. You can also help translate software and content, test and give feedback on software updates, write and edit documentation, design and do artwork, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit http://join.fedoraproject.org today! Cheers, -robyn

1 0

2013-12-16 @ 16:00 UTC - Fedora QA Meeting
by Adam Williamson 15 Dec '13

15 Dec '13

# Fedora Quality Assurance Meeting # Date: 2013-12-16 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! Many thanks to everyone for your hard work on Fedora 20 validation testing! Today / tomorrow, 2013-12-16, will be the first post-F20 QA team meeting - time for us to look back on F20, and forward to F21. I've listed a few suggested areas of discussion for both in the Wiki agenda, so do have a look at that link. We probably need to start thinking about the possible consequences of the 'three product proposal' as soon as possible, and coming up with a game plan: I will see if I can get some folks from FESCo and the WGs to come along, if at all possible. This is a reminder of the upcoming QA meeting. Please add any topic suggestions to the meeting wiki page: https://fedoraproject.org/wiki/QA/Meetings/20131216 The current proposed agenda is included below. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 20 recap 3. Fedora 21 planning 4. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Important note regarding /root permissions for those who installed Fedora 20 pre-releases
by Adam Williamson 13 Dec '13

13 Dec '13

Hi, folks. I wanted to draw the attention of anyone who used Fedora 20 pre-release (Alpha, Beta, or TC/RC for Alpha, Beta or Final) to this issue: https://fedoraproject.org/wiki/Common_F20_bugs#.2Froot_permissions_incorrec… Briefly, if you did use F20 pre-release - this includes yum or otherwise upgrading to F20 at any time the older 'rootfiles' package was in the F20 repos, that is any time prior to about 12-05 (testing) /12-11 (stable) - permissions on the /root directory are likely to be 0755, which is probably not what most sysadmins would expect. You may wish to change them to 0550 or something similarly locked-down. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Fedora 20 Final status is Go; GA release on Dec-17!
by Jaroslav Reznik 12 Dec '13

12 Dec '13

At the Fedora 20 Final Go/No-Go Meeting that just occurred, it was agreed to Go with the Fedora 20 by Fedora QA and Fedora Development. Fedora Release Engineering to be notified. "#agreed Fedora QA and Fedora Development are both Go; Fedora Release Engineering to be notified (with possibility to revisit Go decision in case of unexpected issues from releng side)" Fedora 20 will be publicly available on Tuesday, December 17, 2013. I'd like to use this opportunity to say big "thank you" to everyone involved in the release of the Heisenbug and for catching all heisenbugs we hit during Fedora 20 cycle! Meeting details can be seen here: Minutes: http://bit.ly/1aZVhAm Log: http://bit.ly/19kCBzj Jaroslav

1 0

Fedora 20 Final Release Candidate 1 (RC1) Available Now!
by Andre Robatino 12 Dec '13

12 Dec '13

NOTE: The 32-bit Install DVD is over its size limit. As per the Fedora 20 schedule [1], Fedora 20 Final Release Candidate 1 (RC1) is now available for testing. Content information, including changes, can be found at https://fedorahosted.org/rel-eng/ticket/5808#comment:15 . Please see the following pages for download links (including delta ISOs) and testing instructions. Normally dl.fedoraproject.org should provide the fastest download, but download-ib01.fedoraproject.org is available as a mirror (with an approximately 1 hour lag) in case of trouble. To use it, just replace "dl" with "download-ib01" in the download URL. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Base: https://fedoraproject.org/wiki/Test_Results:Current_Base_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha, Beta, and Final priority test cases for Installation [2], Base [3], and Desktop [4] should pass in order to meet the Final Release Criteria [5]. Help is available on #fedora-qa on irc.freenode.net [6], or on the test list [7]. Create Fedora 20 Final test compose (TC) and release candidate (RC) https://fedorahosted.org/rel-eng/ticket/5808 Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-20/f-20-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Base_validation_testing [4] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [5] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria [6] irc://irc.freenode.net/fedora-qa [7] https://admin.fedoraproject.org/mailman/listinfo/test

1 0

2013-12-11 @ 17:00 UTC - F20 Final Blocker Bug Review #5
by Adam Williamson 11 Dec '13

11 Dec '13

# F20 Final Blocker Review meeting #5 # Date: 2013-12-11 # Time: 17:00 UTC (12:00 EST, 09:00 PST) # Location: #fedora-blocker-review on irc.freenode.net Sadly we didn't build an RC yet and we still have proposed blockers to consider, so please folks, come out and help us review the new crop. Input from outside the usual suspects is always welcome... We'll be reviewing the five proposed blocker and one proposed freeze exception bugs and checking that accepted blocker bugs are getting the attention they need. 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 - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you soon! [1] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce December 2013