devel-announce December 2013

devel-announce@lists.fedoraproject.org

7 participants
9 discussions

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

Split of bind-chroot package in Fedora rawhide branch
by Tomas Hozza 18 Dec '13

18 Dec '13

Hi. I would like to prevent unpleasant surprises and announce, that bind-chroot sub-package of bind has been split into two sub-packages in the Fedora rawhide branch. Previously the bind-chroot sub-package contained named-chroot.service enabling users to run named in a chroot environment and also named-sdb-chroot.service enabling users to run named-sdb in a chroot environment. >From now on, there are two subpackages: - 'bind-chroot' - for running named in a chroot (nothing changes) - 'bind-sdb-chroot' - for running named-sdb in a chroot User that want to run named-sdb in a chroot must install the 'bind-sdb-chroot' package explicitly. This change is a part of fixing Bug #997030. The package will be also NOT installed if updating to Fedora rawhide, because it cannot be currently done (AFAIK) without creating unwanted dependencies. As an addition named-sdb now uses its own chroot path '/var/named/chroot_sdb'. Regards, Tomas Hozza

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

2 1

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 Go/No-Go Meeting #2, Thursday, December 12 @ 17:00 UTC
by Jaroslav Reznik 10 Dec '13

10 Dec '13

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 20. Thursday, December 12, 2013 17:00 UTC (12 PM EST, 9 AM PST, 18:00 CET) "Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 20 Final Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/20/final/buglist This is the second attempt to release final Fedora 20 and we're really very close to holidays. Please, help us with the release by working on the bugs assigned to you - the very, very deadline to create and validate RC on time is Wednesday... Thanks everyone! Jaroslav

1 0

docker-io rpm and docs
by Lokesh Mandvekar 06 Dec '13

06 Dec '13

Hi lists, docker-io 0.7.0 has made its way into yum stable repos for 19, 20 and epel and 0.7.1 is being pushed out to testing by Vincent Batts currently. Please test and add karma here: https://admin.fedoraproject.org/updates/docker-io The fedora docs have been merged in the master branch and can be found here: http://docs.docker.io/en/master/installation/fedora/ This will probably be pushed to the 'latest' branch when 0.7.2 is released, so until then, if you click on the fedora icon here: http://www.docker.io/gettingstarted/#h_installation, all you'll see is http://docs.docker.io/en/latest/installation/fedora/ Comments, suggestions welcome :) -- Lokesh

1 0

Fedora 20 Final to slip by one week
by Jaroslav Reznik 05 Dec '13

05 Dec '13

Today at Go/No-Go meeting it was decided to slip Fedora 20 Final release by one week due to unresolved blocker bugs [1] not being fixed and no RC available by the time of the meeting . The new GA date is now Dec 17. You can find more details in meeting minutes [2]. The next Go/No-Go meeting is on Thursday, Dec 12, the same time in #fedora-meeting-2 channel. [1] http://qa.fedoraproject.org/blockerbugs/milestone/20/final/buglist [2] http://meetbot.fedoraproject.org/fedora-meeting-2/2013-12-05/f20_final_gono… [3] https://fedoraproject.org/wiki/Releases/20/Schedule

1 0

Fedora 20 Final Go/No-Go Meeting, Thursday, December 05 @ 17:00 UTC
by Jaroslav Reznik 02 Dec '13

02 Dec '13

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 20. Thursday, December 05, 2013 17:00 UTC (12 PM EST, 9 AM PST, 18:00 CET) "Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 20 Final Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/20/final/buglist For more details, see Adam's wrap up from the last Thursday [1]. Please, help us to deliver the release on time! The Readiness meeting follows the Go/No-Go meeting two hours later. Jaroslav [1] https://lists.fedoraproject.org/pipermail/devel/2013-November/192527.html

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce December 2013