devel-announce March 2016

devel-announce@lists.fedoraproject.org

8 participants
12 discussions

Fedora 24 Alpha for POWER
by Peter Robinson 31 Mar '16

31 Mar '16

The Fedora 24 Alpha for POWER is here, right on schedule for our planned June final release. Download the prerelease from our Get Fedora site: - Get Fedora 24 Alpha Workstation https://getfedora.org/en/workstation/ prerelease/ - Get Fedora 24 Alpha Server https://getfedora.org/en/server/prerelease/ - Get Fedora 24 Alpha Cloud https://getfedora.org/en/cloud/prerelease/ - Get Fedora 24 Alpha Spins https://spins.fedoraproject.org/prerelease - Get Fedora 24 Alpha Labs https://labs.fedoraproject.org/prerelease - Get Fedora 24 Alpha ARM https://arm.fedoraproject.org/prerelease What is the Alpha release? -------------------------- The Alpha release contains all the features of Fedora 24's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 24 is expected in June. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/24/Schedule * https://fedoraproject.org/wiki/How_to_file_a_bug_report Fedora-Wide Changes ------------------- Under the hood, glibc has moved to 2.23. The update includes better performance, many bugfixes and improvements to POSIX compliance, and additional locales. The new library is backwards compatible with the version of glibc that was shipped in Fedora 23, and includes a number of security and bug fixes. We've also updated the system compiler to GCC 6 and rebuilt all packages with that, providing greater code optimization and catching programming errors which had slipped past previous compilers. In ppc64/ppc64le golang 1.6 brings all the same golang functionality that other architectures have enjoyed enabling all the features and apps that are avaialble there such as docker. Server ------ - FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This version helps streamline installation of replicas by adding a replica promotion method for new installs. A new topology plugin has also been added that automatically manages new replication segment creation. An effective replica topology visualization tool is also available in the webUI. - NodeJS 4 in now available for aarch64. Earlier versions of nodejs have been available on primary architectures for some time. With nodejs4 we now bring all the functionality to aarch64 too. - More packages have been removed from the default Server edition to make the footprint of the default installation smaller. Cloud ----- - For Fedora 24, we're working hard to make Fedora the best platform for developing containers, from the base Fedora container images to a full-featured PaaS to run and manage them. - For both ppc64 and ppc64le we have qemu cloud images and add to it docker base images to the release as well. Issues and Details ------------------ This is an Alpha release. As such, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F24 Bugs page. * https://fedoraproject.org/wiki/Common_F24_bugs For tips on reporting a bug effectively, read "how to file a bug report." * https://fedoraproject.org/wiki/How_to_file_a_bug_report Release Schedule ---------------- The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/24/Schedule The current schedule calls for a beta release towards the beginning of May, and the final release in early June. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly-integrated and updated upstream software while also retaining high quality.

1 0

Fedora 24 Alpha for aarch64
by Peter Robinson 31 Mar '16

31 Mar '16

The Fedora 24 Alpha for aarch64 is here, right on schedule for our planned June final release. Download the prerelease from our Get Fedora site: - Get Fedora 24 Alpha Server https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Alpha/Se… https://fedoraproject.org/wiki/Architectures/AArch64/F24/Installation What is the Alpha release? -------------------------- The Alpha release contains all the features of Fedora 24's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 24 is expected in June. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/24/Schedule * https://fedoraproject.org/wiki/How_to_file_a_bug_report Fedora-Wide Changes ------------------- Under the hood, glibc has moved to 2.23. The update includes better performance, many bugfixes and improvements to POSIX compliance, and additional locales. The new library is backwards compatible with the version of glibc that was shipped in Fedora 23, and includes a number of security and bug fixes. We've also updated the system compiler to GCC 6 and rebuilt all packages with that, providing greater code optimization and catching programming errors which had slipped past previous compilers. In aarch64 golang 1.6 brings all the same golang functionality that other architectures have enjoyed enabling all the features and apps that are avaialble there such as docker. Server ------ - FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This version helps streamline installation of replicas by adding a replica promotion method for new installs. A new topology plugin has also been added that automatically manages new replication segment creation. An effective replica topology visualization tool is also available in the webUI. - NodeJS 4 in now available for aarch64. Earlier versions of nodejs have been available on primary architectures for some time. With nodejs4 we now bring all the functionality to aarch64 too. - More packages have been removed from the default Server edition to make the footprint of the default installation smaller. Cloud and Docker ---------------- Not quite ready for Alpha both qemu cloud images and docker images will be appearing for nightly Fedora 24 aarch64 composes starting next week. All the docker pieces are already in place in Fedora 24 Alpha. The last pieces of the infrastructure to build the nightly docker images are almost live into production. There will be appropriate announcements when they go live. Issues and Details ------------------ This is an Alpha release. As such, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F24 Bugs page. * https://fedoraproject.org/wiki/Common_F24_bugs For tips on reporting a bug effectively, read "how to file a bug report." * https://fedoraproject.org/wiki/How_to_file_a_bug_report Release Schedule ---------------- The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/24/Schedule The current schedule calls for a beta release towards the beginning of May, and the final release in early June. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly-integrated and updated upstream software while also retaining high quality.

1 0

Announcing the release of Fedora 24 Alpha!
by Dennis Gilmore 29 Mar '16

29 Mar '16

The Fedora 24 Alpha is here, right on schedule for our planned June final release. Download the prerelease from our Get Fedora site: - Get Fedora 24 Alpha Workstation https://getfedora.org/en/workstation/ prerelease/ - Get Fedora 24 Alpha Server https://getfedora.org/en/server/prerelease/ - Get Fedora 24 Alpha Cloud https://getfedora.org/en/cloud/prerelease/ - Get Fedora 24 Alpha Spins https://spins.fedoraproject.org/prerelease - Get Fedora 24 Alpha Labs https://labs.fedoraproject.org/prerelease - Get Fedora 24 Alpha ARM https://arm.fedoraproject.org/prerelease What is the Alpha release? -------------------------- The Alpha release contains all the features of Fedora 24's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 24 is expected in June. If you take the time to download and try out the Alpha, you can check and make sure the things that are important to YOU are working. Every bug you find and report doesn't just help you, it improves the experience of millions of Fedora users worldwide! Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as we can, and your feedback improves not only Fedora, but Linux and Free software as a whole. * https://fedoraproject.org/wiki/Releases/24/Schedule * https://fedoraproject.org/wiki/How_to_file_a_bug_report Fedora-Wide Changes ------------------- Under the hood, glibc has moved to 2.23. The update includes better performance, many bugfixes and improvements to POSIX compliance, and additional locales. The new library is backwards compatible with the version of glibc that was shipped in Fedora 23, and includes a number of security and bug fixes. We've also updated the system compiler to GCC 6 and rebuilt all packages with that, providing greater code optimization and catching programming errors which had slipped past previous compilers. Workstation ----------- - Workstation features a preview of GNOME 3.20, which was released just after the Alpha was cut. The GNOME 3.20 release is already available in the Fedora 24 update stream. Once you install Fedora 24 Alpha, you can use Software or dnf to update. GNOME 3.20 will of course be part of Fedora 24 Beta and the Final release. - We have decided not to make Wayland, the next generation graphic stack, the default in Fedora 24 Workstation. However, Wayland remains available as an option, and the Workstation team would greatly appreciate your help in testing. Our goal is one full release where the non-default Wayland option works seamlessly, or reasonably close thereto. At that point we will make Wayland the default with X11 as the fallback option. - There have been many changes to theming in GTK+ 3, where a stable API has not been declared. As a result, applications that use custom CSS theming, for example, may show issues with their appearance. This may include default applications that come with Fedora 24 Alpha Workstation. Users are asked to try out their favorite GTK+ 3 based applications and report bugs upstream so they might be addressed in time for the final release. Server ------ - FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This version helps streamline installation of replicas by adding a replica promotion method for new installs. A new topology plugin has also been added that automatically manages new replication segment creation. An effective replica topology visualization tool is also available in the webUI. - More packages have been removed from the default Server edition to make the footprint of the default installation smaller. Cloud ----- - For Fedora 24, we're working hard to make Fedora the best platform for developing containers, from the base Fedora container images to a full-featured PaaS to run and manage them. - We're packaging OpenShift Origin for Fedora to make it easy to run on Fedora. OpenShift Origin is a distribution of Kubernetes optimized for enterprise application development and deployment. Origin embeds Kubernetes and adds powerful additional functionality to deliver an easy to approach developer and operator experience for building applications in containers. Spins and Labs -------------- Fedora Spins are alternative desktops for Fedora that provide a different desktop experience than the standard Fedora Workstation edition. Fedora Workstation is built on the GNOME desktop environment and aims to provide a compelling, easy-to-use operating system for software developers, while also being well-suited to other users. Our spins showcase KDE Plasma, Xfce, LXDE, Mate-Compiz, Cinnamon, and Sugar on a Stick (Soas) on the same Fedora Base. Fedora Labs are collections of software for specific purposes — Games, Design, Robotics, and so on. They are pre-selected sets of Fedora software and are ideal for events or audiences with the corresponding specific interest. Fedora 24 comes with a new lab, the Astronomy Spin, a set of tools for astronomers and astrophysicists. Note that the SoaS spin and Security, Games, and Design Suite labs are missing from the Fedora 24 Alpha release. We plan to fix this for the Beta release. ARM --- ARM images are available as usual for several usecases. Fedora 24 ships Desktop images, such as Spins and Workstation, but also provides a Server image. A minimal Fedora image completes the wide set of install options for you ARM board. Atomic Host ----------- Fedora Atomic Host releases on a two-week schedule, and each release is built on the latest overall Fedora OS. This schedule means the Atomic Host is currently built on Fedora 23, but will switch to Fedora 24 when we're out of Beta. There currently is no Fedora Atomic Host built on Fedora 24 Alpha, but we plan to have that for the Beta. However, you can try one of the newer features with recent Fedora Atomic Host builds today. Since Fedora 23 was released, Atomic Host has added a "developer mode" that gives a better developer experience overall. When running in DEVELOPER MODE, the host will download and start Cockpit and fire up a TMUX session to make it easier to work at the console and obtain necessary information (like the root password, IP address, etc.). Issues and Details ------------------ This is an Alpha release. As such, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. As testing progresses, common issues are tracked on the Common F24 Bugs page. * https://fedoraproject.org/wiki/Common_F24_bugs For tips on reporting a bug effectively, read "how to file a bug report." * https://fedoraproject.org/wiki/How_to_file_a_bug_report Release Schedule ---------------- The full release schedule is available on the Fedora wiki: * https://fedoraproject.org/wiki/Releases/24/Schedule The current schedule calls for a beta release towards the beginning of May, and the final release in early June. Be aware that these dates are development targets. Some projects release on a set date regardless of feature completeness or bugs; others wait until certain thresholds for functionality or testing are met. Fedora uses a hybrid model, with milestones subject to adjustment. This allows us to make releases with new features and newly-integrated and updated upstream software while also retaining high quality. Flock 2016: Krakow, Poland -------------------------- If you're a contributor to Fedora, or interested in getting more involved, one way to engage with our community is through Fedora premier events. The annual North American/European conference for Fedora contributors is Flock, which takes place August 2-5, 2016 in Krakow, Poland. Registration is now open at https://register.flocktofedora.org. For more information about our Latin American and Asia-Pacific Conferences, stay tuned for announcements on the Fedora Community Blog: * https://communityblog.fedoraproject.org

1 0

[Guidelines change] Changes to the packaging guidelines
by Jason L Tibbitts III 28 Mar '16

28 Mar '16

Here are the recent changes to the packaging guidelines. ----- The use of rich (or Boolean) dependencies is now OK for F23+. * https://fedoraproject.org/wiki/Packaging:Guidelines#Rich.2FBoolean_dependen… * https://fedorahosted.org/fpc/ticket/593 ----- The ban on the use of the %systemd_requires macro has been lifted. * https://fedoraproject.org/wiki/Packaging:Scriptlets#Systemd * https://fedorahosted.org/fpc/ticket/600 ----- The mono guidelines were modified to require that packages limit themselves via ExclusiveArch: to architectures which actually support mono. * https://fedoraproject.org/wiki/Packaging:Mono * https://fedorahosted.org/fpc/ticket/602

1 0

Announce: blivet-2.0.0
by David Lehman 24 Mar '16

24 Mar '16

Hi everyone, I would like to announce the release of blivet-2.0.0[1]. See the release notes[2] for information about all of the changes in this version and the documentation[3] for the public API specification. Some of the larger changes: - full PEP8 compliance - thread-safety - added support for creating LVM RAID volumes - added support for resizing LUKS encrypted block devices - use libbytesize[4] as the backend for blivet's Size class - device tree updates based on uevents (disabled by default) - dropped support for python2 For now there is a blivet-2.0.0 build in my copr[5] for anyone who wants to check it out. I also want to give a heads-up that I plan to build blivet-2.0.1 in rawhide next week, which means switching anaconda to use it at that time. Thanks, David [1] https://github.com/rhinstaller/blivet/releases/tag/blivet-2.0.0 [2] https://github.com/rhinstaller/blivet/blob/2.0-release/release_note s.rst [3] http://rhinstaller.github.io/blivet/docs/api.html [4] https://github.com/rhinstaller/libbytesize [5] https://copr.fedorainfracloud.org/coprs/dlehman/blivet/

1 0

Fedora 24 Alpha status is GO, release on March 29, 2016
by Jan Kurik 23 Mar '16

23 Mar '16

At the second Fedora 24 Alpha Go/No-Go Meeting [1][2] that just ended, has been agreed by QA, Release Engineering and Development to go live with the Fedora 24 Alpha. Fedora 24 Alpha will be publicly available on March 29, 2016. The official release time has been agreed on F24 Alpha Readiness meeting [3] to be 14:00 UTC. Meeting details can be seen here: [1] Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2016-03-23/f24-alpha-go_no… [2] Log: https://meetbot.fedoraproject.org/fedora-meeting/2016-03-23/f24-alpha-go_no… [3] https://meetbot.fedoraproject.org/teams/f24-alpha-readiness-meeting/f24-alp… Thanks everyone! -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Node.js 5.9.0 coming to Rawhide next week
by Stephen Gallagher 23 Mar '16

23 Mar '16

Next week, I plan to upgrade Node.js from the 4.x LTS branch to the 5.x stable branch in Rawhide. This upgrade does break backwards-compatibility and thus will need re-testing of modules. Also, all native NPMs (those that are built with architecture-specific packages rather than noarch) will need to be rebuilt to pick up the new automatic dependency system we have implemented. Previously, native modules had to be rebuilt for every minor-version bump of Node.js, but we have tweaked the virtual Provides and Requires to only require a rebuild at major-version bumps. This will help significantly with the stable branch, which revs the minor release fairly often.

1 0

Modularity Working Group: Call for Self-Nominations
by Matthew Miller 18 Mar '16

18 Mar '16

Two and a half years ago¹ (woah, time goes fast!), we formed the initial Fedora.next Working Groups — three for the Cloud, Workstation, and Server editions, and two more for exploring the "Fedora Rings" concept, Base and Environments & Stacks. On Monday, the Fedora Council unanimously approved an update to this structure as part of the next phase of the Modularity Objective². We’re putting Environments & Stacks on hold for now (activity had effectively come to a halt anyway), and creating a new Modularity Working Group which will include the Base Working Group functions among its responsibilities. Details including the mission statement are at https://fedoraproject.org/wiki/Modularity_Working_Group. To nominate yourself, add your name to the list at https://fedoraproject.org/wiki/Modularity_Working_Group/Initial_Nominations, along with a brief description of your current involvement with Fedora and plans for participation in this group. Note that this will be a highly technical working group. We're looking particularly (but not exclusively) for representation from the previous Environments & Stacks and Base WGs, Release Engineering, Infrastructure, Quality Assurance, and the Security Team. Self-nominations will close at April 18, 2016 00:00 UTC. Langdon White, as Objective Lead, will select initial membership, with the approval of the Council. As with previous WGs, this will be an independent subcommittee of FESCo, and the group will select a liaison who will attend FESCo meetings and facilitate communication. 1. https://lists.fedoraproject.org/pipermail/devel-announce/2013-September/001… 2. http://fedoraproject.org/wiki/Objectives/Fedora_Modularization,_Prototype_P… -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

Fedora 24 Alpha Release Readiness Meeting, Thursday, March 17 @ 19:00 UTC
by Jan Kurik 14 Mar '16

14 Mar '16

Join us on irc.freenode.net in #fedora-meeting for the Fedora 24 Alpha Release Readiness Meeting meeting. The meeting is going to be held on Thursday, March 17, 2016 19:00 UTC. Please check the [FedoCal] link for your time zone. We will meet to make sure we are coordinated and ready for the Alpha release of Fedora 24 on Tuesday, March 22nd, 2016. Please note that this meeting is going to be held 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. [FedoCal] https://apps.fedoraproject.org/calendar/meeting/3336/ Thank you for your support and Regards, Jan More information available at: https://fedoraproject.org/wiki/Release_Readiness_Meetings -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Modularity Objective Status Update (March 11, 2016)
by White, Langdon 11 Mar '16

11 Mar '16

Recently, I have been able to dedicate substantially more of my time to the modularity objective. Red Hat is also dedicating other people to moving the objective forward. Both I and the others expect to be able to continue to dedicate time for the foreseeable future. As a result, I wanted to send out this update about what we have done over the past couple weeks and seek feedback. I also plan to send out these updates regularly, probably monthly, or more often, if we have something specific we would like feedback on. First off, we have updated the Modularization wiki page[1] on the Fedora wiki with things we know and things we think about modularity. The biggest example being "what is a module." Next, we are due to review the modularity objective with the Fedora Council on March 14th. As a result, we have put together a new phase proposal[2]. One of the major components is a proposal about restructuring a couple of the working groups. I’d appreciate your comments and feedback on this proposal before we submit it to the Council. I also started a blog post series on community blog[3]. The first post[4] went out this past Tuesday. Lastly, we did a Q&A for the Server WG earlier this week. Mizmo did a great writeup[5] and you can also read the "real" logs[6]. Engineering work is starting but we are still getting organized. The next update will include more details about how you can get involved. However, if you have ideas now, please feel free to add user stories[7][8]. Langdon Fedora Modularity Objective Lead [1]: https://fedoraproject.org/wiki/Modularization [2]: https://fedoraproject.org/wiki/Objectives/Fedora_Modularization,_Prototype_… [3]: https://communityblog.fedoraproject.org/ [4]: https://communityblog.fedoraproject.org/modularity-use-case-application-ind… [5]: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… [6]: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… [7]: http://guide.agilealliance.org/guide/user-stories.html [8]: https://fedoraproject.org/wiki/Modularization/Planning

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce March 2016