devel-announce May 2015

devel-announce@lists.fedoraproject.org

8 participants
14 discussions

Reminder: Fedora 20 end of life on 2015-06-23
by Dennis Gilmore 27 May '15

27 May '15

Greetings. This is a reminder email about the end of life process for Fedora 20. Fedora 20 will reach end of life on 2015-06-23, and no further updates will be pushed out after that time. Additionally, with the recent release of Fedora 22, no new packages will be added to the Fedora 20 collection. Please see https://fedoraproject.org/wiki/FedUp for more information on upgrading from Fedora 20 to a newer release. Dennis

1 0

Fedora 22 for aarch64 is here!
by Peter Robinson 26 May '15

26 May '15

We are proud to announce the official release of Fedora 22 for aarch64, the community-driven and community-built operating system now available in Cloud, Server, and Workstation editions. If that's all you need to hear, jump over to Get Fedora to download -- or for current users, run the FedUp upgrade tool. * https://fedoraproject.org/wiki/Architectures/AArch64/F22/Installation * https://fedoraproject.org/wiki/FedUp In addition to the latest versions of all your favorite free and open source software, Fedora 22 marks our second release with distinctly-targeted offerings for cloud computing, the server room, and the desktops and laptops of software developers and creators everywhere. Thanks to the hard work of developers, designers, packagers, translators, testers, documentation writers, and everyone else, we're incredibly confident in saying that this is our best and most polished release yet. Also with this release, we return to our traditional six-month cadence -- we'll see you back here sometime around Halloween! Highlights in the Fedora 22 release =================================== Every Fedora release has its own character. If this release had a human analogue, it'd be Fedora 21 after it'd been to college, landed a good job, and kept its New Year's Resolution to go to the gym on a regular basis. What we're saying is that Fedora 22 has built on the foundation we laid with Fedora 21 and the work to create distinct editions of Fedora focused on the desktop, server, and cloud (respectively). It's not radically different, but there are a fair amount of new features coupled with features we've already introduced but have improved for Fedora 22. Fedora Server ------------- * Database Server Role -- The Fedora Server edition focuses on easy of different server roles. Fedora 21 debuted with an Domain Controller Role featuring FreeIPA. For this release, we've added a Database Server role, built around PostgreSQL. * Default to XFS filesystem -- The default file system type for Fedora Server installs will be XFS running atop LVM for all partitions except /boot. The /boot partition will remain a non-LVM, ext4 partition due to technological limitations of the bootloader. * Cockpit will be compatible between OS releases -- Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser. - Easy to use. Cockpit is perfect for new sysadmins, allowing them to easily perform simple tasks such as storage administration, inspecting journals and starting and stopping services. - No interference. Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface. - Multi-server. You can monitor and administer several servers at the same time. Other changes of note ===================== Faster and better dependency management with DNF ------------------------------------------------ With Fedora 22, we're introducing a major change under the hood. Specifically, we're now using DNF and hawkey to manage packages. DNF is much like the Yum software package manager (it's largely command-line compatible), but re-written and re-engineered to provide optimal performance and (along with Hawkey) provide a strict API definition for plugins and extending projects. DNF also makes use of the libsolv library initially pioneered by the openSUSE Project to provide faster and better dependency management. It also boasts a better performance and memory footprint vs. Yum, and is designed to have a cleaner codebase and be easier to maintain. If you're using the Fedora 22 Workstation edition, and managing packages with the Software Application, odds are you won't notice a difference. Server and Cloud users who fall back on Yum commands will receive a reminder (courtesy of dnf-yum) that Yum is deprecated and DNF is now the default package manager. DNF has been in development for quite some time, so we're confident it's ready for prime time. The classic Yum command line tool has been renamed to yum-deprecated as a transitional step for tools still using it. See Read The Docs for compatibility changes from Yum to DNF in detail. GNU Compiler Collection 5 ------------------------- Fedora 22 comes with GCC 5.1 as the primary compiler suite. Downloads, upgrades, documentation, and common bugs ================================================== You can start by downloading Fedora 22: * https://fedoraproject.org/wiki/Architectures/AArch64/F22/Installation If you are upgrading from a previous release of Fedora, refer to: * http://fedoraproject.org/wiki/Upgrading Fedora's FedUp utility enables an easy upgrade to Fedora 22 from previous releases. See the FedUp page on the Fedora wiki for more information: * https://fedoraproject.org/wiki/FedUp Documentation ------------- Read the full release notes for Fedora 22, guides for several languages, and learn about known bugs and how to report new ones: * http://docs.fedoraproject.org/ Fedora 22 common bugs are documented at: * http://fedoraproject.org/wiki/Common_F22_bugs This page includes information on several known non-blocker bugs in Fedora 22. Please be sure to read it before installing! Read this announcement in glorious full color on Fedora Magazine, at * http://fedoramagazine.org/fedora-22-released and follow the Magazine for regular user-focused articles covering all things Fedora.

1 0

poppler soname bump in rawhide
by Marek Kasik 26 May '15

26 May '15

Hi, I plan to rebase poppler in rawhide to poppler-0.33.0 during the next week. There are several API changes and soname bump of the base library libpoppler.so.*. I've prepared a scratch build of poppler-0.33.0 against which you can test your packages. You can find the build here: http://koji.fedoraproject.org/koji/taskinfo?taskID=9851480 or here: http://mkasik.fedorapeople.org/poppler/ Poppler developers changed the model they use for releasing. All releases should be considered stable from now so even the odd ones. Also, if your package use the unstable API (headers from poppler-devel), could you consider to change it to use a stable API (glib, qt, C++)? This would allow us to not ship the headers and rebase to the newest poppler versions whenever we want not just in Rawhide. Regards Marek

1 0

Fedora 22 Final status is Go, release on May 26, 2015
by Jaroslav Reznik 22 May '15

22 May '15

At the Fedora 22 Final Go/No-Go Meeting #2 that just occurred, it was agreed to Go with the Fedora 22 Final by Fedora QA, Release Engineering and Development. Fedora 22 Final will be publicly available on Tuesday, May 26, 2015. Meeting details can be seen here: Minutes: http://bit.ly/1Bh2pH1 Log: http://bit.ly/1HzMI5g Thank you everyone for a great job, sleepless nights validating TCs, RCs, fixing bugs, composing stuf and everything else needed for smooth releases. Amazing last three years wrangling releases for me! Jaroslav

1 0

[Guidelines change] Changes to the packaging guidelines
by Jason L Tibbitts III 21 May '15

21 May '15

Here are the recent changes to the packaging guidelines: The policy for systemd presets has been modified to merge the individual treatments of service, socket and timer units into one policy. The policy page was also moved into the packaging guidelines proper. * https://fedoraproject.org/wiki/Packaging:DefaultServices * https://fedoraproject.org/w/index.php?title=Packaging%3ADefaultServices&dif… * https://fedorahosted.org/fpc/ticket/532 ----- Slightly modified the per-product configuration guidelines to account for changes in the os-release file. * https://fedoraproject.org/wiki/Packaging:Per-Product_Configuration * https://fedoraproject.org/w/index.php?title=Packaging%3APer-Product_Configu… * https://fedorahosted.org/fpc/ticket/520#comment:7 ----- New guidelines for the consistent usage of SSL certificates by applications have been added. * https://fedoraproject.org/wiki/Packaging:SSLCertificateHandling * https://fedorahosted.org/fpc/ticket/480 ----- It is now mandatory that modules which support python3 be packaged for python3. Python modules which support both python2 and python3 may be packages for both, or just python3. Packaging of modules which support only python2 are unaffected. * https://fedoraproject.org/wiki/Packaging:Python * https://fedoraproject.org/w/index.php?title=Packaging%3APython&diff=413621&… * https://fedorahosted.org/fpc/ticket/526 ----- The AppData packaging guidelines have been updated to include information about addon packages, and to use appstream-util instead of appdata-validate. * https://fedoraproject.org/wiki/Packaging:AppData * https://fedoraproject.org/w/index.php?title=Packaging%3AAppData&diff=413661… * https://fedorahosted.org/fpc/ticket/527 ----- The R Packaging guidelines have been revised to indicate that the DESCRIPTION file should not be marked %doc, as it is actually required for operation of the R package and needs to be present even when installed with --excludedocs. * https://fedoraproject.org/wiki/Packaging:R * https://fedoraproject.org/w/index.php?title=Packaging%3AR&diff=413668&oldid… * https://fedorahosted.org/fpc/ticket/535 ----- The BuildRequires section of the guidelines has been revised; the exceptions list is gone. The release engineering folks are free to define the buildroot and rpm is free to change its dependency list. * https://fedoraproject.org/wiki/Packaging:Guidelines#BuildRequires_2 * https://fedoraproject.org/w/index.php?title=Packaging%3AGuidelines&diff=413… * https://fedorahosted.org/fpc/ticket/497

1 0

Fedora 22 Final is No-Go but second sign-off try is tomorrow
by Jaroslav Reznik 21 May '15

21 May '15

Hi! Today at Fedora 22 Final Go/No-Go meeting it was decided that Fedora 22 Final is No-Go. More details in meeting minutes [1]. As both bugs we accepted as blocker bugs today are already fixed and RC3 compose is requested, we will try to sign-off the final release tomorrow. If you are willing to help with release validation, follow standard channels for RC3 announcement. The next Go/No-Go meeting is on Friday, May 22 17:00 UTC #fedora-meeting-2 channel. [1] http://bit.ly/1FFcJ2G

1 0

Fedora 22 Final Go/No-Go Meeting, Thursday, May 21 @ 17:00 UTC
by Jaroslav Reznik 19 May '15

19 May '15

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 22. Thursday, May 21, 2015 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST) "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 22 Final Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/22/final/buglist We don't have RC yet but seem like we're very close to it - testing heroes will be needed to cover all required tests by this meeting. Jaroslav

1 0

Fedora 22 Final Release Readiness Meeting :: Thursday, May 21, 19:00 UTC
by Jaroslav Reznik 19 May '15

19 May '15

Fedora 22 Final Release Readiness Meeting. date: 2015-05-21 place: irc.freenode.net in #fedora-meeting-2 time: 19:00 UTC (3 PM EDT, 12 noon PDT, 21:00 CEST) This Thursday, May 21, we will meet to make sure we are coordinated and ready for the Final release of Fedora 22 on Tuesday, May 26, 2015. Please note that this meeting will occur on May 21 even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may received this message several times, but I was asked to open this meeting to the teams and I'll also hope this will raise awareness and more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. We also have a badge! Jaroslav

1 0

F23 System Wide Change: Netizen Spin
by Jan Kurik 18 May '15

18 May '15

= Proposed Self Contained Change: Netizen Spin = https://fedoraproject.org/wiki/Changes/Netizen_Spin Change owner(s): Corey Leong <cleong at fedoraproject dot org> A Fedora Spin for promoting and supporting internet citizenship and citizen engagement. == Detailed Description == Fedora Netizen is an open source operating system for enabling internet citizens to engage with online services and communities. The goal for Netizen is to pattern the operating system's features after Maslow's Hierarchy of Needs which was published in his 1943 paper, "A Theory of Human Motivation". As a professor of pyschology, Abraham Maslow theorized that individuals attempt to experience five stages of needs starting with physiological, safety, social, esteem, and then ending with self-actualization. Beginning with the first level of physiological needs, individuals' motivational needs ascend upwards to higher levels of needs in order, however, only after establishing lower levels of needs first before ascending to the next level. The philosophy for Netizen closely relates to Maslow's Hierarchy of Needs by establishing three primary software package levels in a hierarchical model. The first and lowest software package level addresses the need for Netizen Privacy in the areas of personal privacy, informational privacy, and communication privacy. After Netizen Privacy, the second software package level addresses the need for Netizen Security in the areas of data security, local security, and network security. After Netizen Security, the third software package level addresses the need for Netizen Engagement in the areas of publishing, education, and social engagement. Future Netizen software package levels will address analytics, awareness, design, develop, and others. == Scope == A Netizen theme is the final requirement to be developed per marketing department support of a look and feel in order to replace the current default theme. This is an isolated change. * Other developers: N/A (not a System Wide Change) * Release engineering: Add spin to spin-kickstarts, ensure spin has been tested, and release with rest of spins * Policies and guidelines: N/A (not a System Wide Change) -- Jan Kuřík

1 1

F23 Self Contained Change: Cinnamon Spin
by Jan Kurik 15 May '15

15 May '15

= Proposed Self Contained Change: Cinnamon Spin = https://fedoraproject.org/wiki/Changes/Cinnamon_Spin Change owner(s): Dan Book <grinnz(a)gmail.com> A Fedora Spin using the Cinnamon desktop environment. == Detailed Description == Cinnamon is a Linux desktop which provides advanced innovative features and a traditional user experience. The desktop layout is similar to Gnome 2. The underlying technology is forked from Gnome Shell. The emphasis is put on making users feel at home and providing them with an easy to use and comfortable desktop experience. == Scope == * Proposal owners: Track existing Cinnamon desktop environment group, and test the Spin: * * Boot and auto-login to Cinnamon * * Functionality of desktop, panel, menu, windows * * Themes of panel/menu, windows, controls, icons * * Default panel launchers and menu favorites * * Install and verify functionality after install * Other developers: N/A (not a System Wide Change) * Release engineering: Add spin to spin-kickstarts, ensure spin has been tested, and release with rest of spins * Policies and guidelines: N/A (not a System Wide Change) -- Jan Kurik

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce May 2015