devel-announce January 2013

devel-announce@lists.fedoraproject.org

9 participants
100 discussions

Start a nNew thread

Proposed F19 Feature: DualstackNetworking - proper dual stack IPv4 and IPv6 networking
by Jaroslav Reznik 16 Jan '13

16 Jan '13

1 1

Proposed F19 Feature: JRuby 1.7 - JRuby is an alternative Ruby implementation
by Jaroslav Reznik 16 Jan '13

16 Jan '13

As decided by FESCo on 2012-12-05 meeting, all proposed Features are required to pass through the community review by announcing them on devel-announce list. FESCo votes on new features no sooner than a week from the announcement. = Features/JRuby 1.7 = https://fedoraproject.org/wiki/Features/JRuby_1.7 * Detailed description: Transition to JRuby 1.7 will consist of 3 basic steps: - Updating packages Most of the packages that JRuby depends on are in Fedora just because of JRuby, so they can be safely updated. Some dependencies are shared with other packages, so they will have to be discussed with their owners (see #Scope). - Integration with Fedora Normally, each Ruby implementations ships with its own copy of RubyGems library. This is wrong because a) it's bundling, b) there is no reason why multiple Ruby implementations wouldn't be able to share one RubyGems library. There used to be some differencies in JRuby's copy of RubyGems, but the JRuby upstream has been very cooperative and managed to get them all merged into upstream RubyGems. The integration will require changing Fedora's operating_system.rb (place for distro-specific defaults for RubyGems). This change will result into all Gems with binary extensions having to be recompiled, as the binary extension placement will change. See [1] for current operating_system.rb look and its changes from F18. What should "/usr/bin/ruby" point to? During standard Gem packaging process, the executable files in Gems get shebangs according to the binary that they are packaged with (Ruby => "/usr/bin/ruby"; JRuby => "/usr/bin/jruby"). Therefore executing a Ruby "binary" runs the interpreter that was used for building (or the hardcoded one, which is usually Ruby). Using alternatives for "/usr/bin/ruby" doesn't seem to be a very good option, because Ruby and JRuby are not in fact full alternatives, as they for example cannot use same extension Gems (but it still makes sense to allow executing same binaries with them). Also, alternatives are only switchable on admin level (we want every developer with non-root privileges to be able to choose the interpreter). Therefore Ruby-SIG has come up with solution of having "/usr/bin/ruby" as a bash script (currently called rubypick) [2], that allows user to choose the interpreter as first argument on invocation (_mri_ or _jruby_), if such a parameter is present. Otherwise it falls back to a default. For example invoking "ruby_binary _jruby_ --foo=bar" in fact invokes "/usr/bin/jruby ruby_binary --foo=bar". This bash script will be in a separate package and both Ruby and JRuby will depend on it. Ruby-SIG knows that this feature might be controversial and we wouldn't want it to stop us from bringing JRuby's power to Fedora (if met with a heavy resistance). So if anyone will suggest a more suitable solution, we'll go with it instead of this one. - Changes in packaging None yet. JRuby will be able to use pure Ruby Gems packaged into RPM out of the box, but packaging of Gems with JRuby extensions is turning out to be very complicated, so the guidelines for it will be postponed to next release (as well as the actual packaging). Users will be still able to install Gems with JRuby extensions, both system-wide (into /usr/local/) and into their home directories. [1] https://github.com/bkabrda/jruby.spec/blob/master/rubygems/operating_system… [2] https://github.com/bkabrda/rubypick

1 0

Proposed F19 Feature: Ruby 2.0.0 - the latest stable version of Ruby, with major increases in speed and reliability
by Jaroslav Reznik 16 Jan '13

16 Jan '13

1 0

Proposed F19 Feature: Erlyvideo - add Erlyvideo video streaming server to the Fedora repositories
by Jaroslav Reznik 16 Jan '13

16 Jan '13

1 0

Proposed F19 Feature: Enlightenment - Integrate Enlightenment in Fedora
by Jaroslav Reznik 16 Jan '13

16 Jan '13

1 0

Reminder: Fedora 16 end of life on 2013-02-12
by Dennis Gilmore 15 Jan '13

15 Jan '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings. This is a reminder email about the end of life process for Fedora 16. Fedora 16 will reach end of life on 2013-02-12, and no further updates will be pushed out after that time. Additionally, with the recent release of Fedora 18, no new packages will be added to the Fedora 16 collection. Please see http://fedoraproject.org/wiki/DistributionUpgrades for more information on upgrading from Fedora 16 to a newer release. Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlD1ijoACgkQkSxm47BaWffE1gCgwpIOp4jT/vuwMLuG9VWpXHYH p8MAn2f0RY3InfKcquvgmyCEHF7pXqPF =UOtn -----END PGP SIGNATURE-----

1 0

Announcing the release of Fedora 18.
by Robyn Bergeron 15 Jan '13

15 Jan '13

The Fedora Project is incredibly delighted to announce the release of Fedora 18 ("Spherical Cow"). Heck, we'd even say that getting this release to you has been a mooving experience. Fedora is a leading-edge, free and open source operating system that continues to deliver innovative features to many users, with a new release about every six months...or so. :-D But no bull: Spherical Cow, is of course, Fedora's best release yet. You'll go through the hoof when you hear about the Grade A Prime F18 features. You can always cownt on us to bring you the best features first. Can't wait for a taste? You can get started downloading 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/18/html/Release_Notes/ == What's New in Fedora 18? == The Fedora Project takes great pride in being able to show off features for all types of use cases, including traditional desktop users, systems administration, development, the cloud, and many more. But a few new features are guaranteed to be seen by nearly anyone installing Fedora and are improvements that deserve to be called out on their own. The user interface for Fedora's installation software, Anaconda, has been completely re-written from the ground up. Making its debut in Fedora 18, the new UI introduces major improvements to the installation experience. It uses a hub-and-spoke model that makes installation easier for new users, offering them concise explanations about their choices. Advanced users and system administrators are of course still able to take advantage of more complex options. The general look and feel of the installation experience has been vastly upgraded, providing modern, clean, and comprehensible visuals during the process. While the new installer should work well for most users in most configurations, there are inevitably a few teething problems in the first release of such a major revision. Known design limitations of the new installer in F18 are listed here: http://fedoraproject.org/wiki/Anaconda/NewInstaller Known significant bugs can be seen here: http://fedoraproject.org/wiki/Common_F18_bugs#Installation_issues We welcome your constructive and specific feedback as we continue to work on refining the installer for future releases. The upgrade process for Fedora now uses a new tool called FedUp (Fedora Upgrader). FedUp replaces pre-upgrade as well as the DVD methods for upgrading that have been used in previous Fedora releases. FedUp integrates with systemd to enable the upgrade functionality, doing the work in a pristine boot environment. Of course, it wouldn't be a release announcement without a spotted -- er, dotted -- list of all the other fantastic features you'll see in Fedora 18: === For desktop users === Moooove over, stale desktops. We've got a small herd of choices udderly suited to your preferences. * GNOME 3.6: The newest version of the GNOME desktop provides an enhanced Messaging Tray, support for Microsoft Exchange and Skydrive, and many more new features. * Cinnamon: Fedora users now have the option of using Cinnamon, an advanced desktop environment based on GNOME 3. Cinnamon takes advantage of advanced features provided by the GNOME backend while providing users with a more traditional desktop experience. * MATE Desktop: The MATE desktop provides users with a classic GNOME 2.x style user interface. This desktop is perfect for users who have been running GNOME Classic or other window managers like XFCE as an alternative to GNOME 3. * KDE Plasma Workspaces 4.9: KDE Plasma Workspaces has been updated with many new features and improved stability and performance, including updates to the Dolphin File Manager, Konsole, and KWin Window manager. * Xfce 4.10: The lightweight and easy-to-use Xfce desktop has been updated to the 4.10 version with many bug fixes and enhancements, including a new MIME type editor, a reworked xfce4-run dialog, improved mouse settings, tabs in the Thunar file manager, and options to tile windows in xfwm4. Through all of these and more, Xfce continues to improve without getting in your way. Regardless of your desktop choice, Fedora 18 offers... * Improved storage management: SSM (System Storage Manager) is an easy-to-use command-line interface tool that presents a unified view of storage management tools. Devices, storage pools, volumes, and snapshots can now be managed with one tool, with the same syntax for managing all of your storage. (It's great for systems administrators, too!) === For developers === For developers there are all sorts of moo-tivating goodies: * Fresh versions of programming languages: Using Perl, Rails, or Python? All three of these languages are updated in Fedora 18. We've got Rails 3.2, Python 3.3, and Perl 5.16 fresh off the farm. * Clojure gets more love with the addition of tooling packages, including the Leinengen build tool, as well as Clojure libraries and frameworks, including Korma and Noir. * DragonEgg connects GCC and LLVM: DragonEgg is a plugin for the GCC compilers to allow use of the LLVM optimization and code-generation framework. DragonEgg provides software developers with more optimization and code-generation options for use with the GCC compilers. DragonEgg also allows GCC to be used for cross-compilation to target architectures supported by LLVM without requiring any special cross-compilation compiler packages. Fedora continues to develop and use GCC as the standard default compiler. === For systems administrators === Keep track of your infrastructure herds with these new features: * Offline system updates: Systems can now be updated offline, allowing for a more stable update of critical system components. This functionality is only integrated with GNOME Desktop Environment in this release but uses the distribution neutral PackageKit and systemd API's and hence can be made available for other desktop environments as well based on the interest from upstream developers. * Storage enhancements: StorageManagement is a collection of tools and libraries for managing storage area networks (SAN) and network attached storage (NAS). * Samba 4: This popular suite of tools has long provided file- and print-sharing services in heterogeneous operating system environments. The long-awaited Samba 4 introduces the first free and open source implementation of Active Directory protocols and includes a new scripting interface, allowing Python programs to interface to Samba's internals. * Riak: A fault-tolerant key-value store, Riak provides easy operations and predictable scaling as a NoSQL database. === For clouds and virtualization === Do you spend your days <strike>grazing</strike> gazing into the clouds? Here's just a taste of some of the cloud and virt features you'll see in Fedora 18: * Eucalyptus makes its first appearance in Fedora, with their 3.2 release included in F18. This platform for on-premise (private) Infrastructure-as-a-Service clouds uses existing infrastructure to create scalable and secure AWS-compatible cloud resources for compute, network, and storage. * OpenStack: With the Folsom release in Fedora 18, OpenStack continues to have the newest releases in Fedora. This open source cloud computing platform enables users to deploy their own cloud infrastructures for private or public cloud deployments. Heat, an incubated OpenStack project, is also available in F18, providing an API that enables the orchestration of cloud applications using file or web based templates. * oVirt Engine: The management application for the oVirt virtualization platform, oVirt Engine, is updated to the newest version, 3.1. This release includes extensive new features, including support for live snapshots, cloning virtual machines from snapshots, quotas, and more. * Suspend and resume support for virt guests: Virtual machines get love with this feature, enabling the ability to suspend and resume guests, with the close of a laptop lid or menu option or via the command line. And that's only the beginning. For a more complete list with details of all the new features in Fedora 18, steer over to: http://fedoraproject.org/wiki/Releases/18/FeatureList == Downloads, upgrades, documentation, and common bugs == The steaks are high--don't miss out on installing the best version of Fedora yet! Get it now: http://get.fedoraproject.org/ If you are upgrading from a previous release of Fedora, refer to: http://fedoraproject.org/wiki/Upgrading Fedora has replaced pre-upgrade with FedUp (excuse the pun.. or don't), a more robust solution, and pushed several bug fixes to older releases of Fedora to enable an easy upgrade to Fedora 18. Graze...er, gaze...upon the full release notes for Fedora 18, guides for several languages, and learn about known bugs and how to report new ones, here: http://docs.fedoraproject.org/ With all the changes to the installer, we particularly recommend reading the Installation Guide: http://docs.fedoraproject.org/en-US/Fedora/18/html/Installation_Guide/index… Everyone makes missteaks. Fedora 18 common bugs are documented at: http://fedoraproject.org/wiki/Common_F18_bugs This page includes information on several known bugs in the installer, so we recommend reading it before installing Fedora 18. == Fedora Spins == Fedora spins are alternate versions of Fedora tailored for various types of users via hand-picked application set or customizations, from desktop options to spins for those interested in gaming, robotics, or design software. More information on our various spins is available at: http://spins.fedoraproject.org == Contributing == There are many ways to contribute beyond bug reporting. You can 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! == Fedora 19 == Even as we continue to provide updates with enhancements and bug fixes to improve the Fedora number experience, our next release, Fedora 19, is already being developed in parallel and has been open for active development for several months already. We have an early plan for release at the end of May 2013, and the final schedule for F19 is going to be based on the results of the planning process: https://fedoraproject.org/wiki/Releases/19/Schedule == Feature Deprecation == Fedora has always been full of great features, but sometimes we need to cull the herd. Saying good-bye is always hard, but here are the ones we had to put out to pasture this time around. * /etc/sysconfig Deprecations: Several system configurations have moved out of /etc/sysconfig. The goal of these changes is to reduce - as described in http://0pointer.de/blog/projects/the-new-configuration-files.html - the unnecessary differences between Linux distributions and share a standard location for common settings. For a full list of changes read the release notes. http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/index.html == Contact information == If you are a journalist or reporter, you can find additional information here: https://fedoraproject.org/wiki/Press Enjoy! -Robyn Bergeron

1 0

The final Fedora 18 is RC4!
by Jaroslav Reznik 10 Jan '13

10 Jan '13

Hi, at today's supplementary Go/No-Go meeting it was decided to ship RC4 (release candidate) as the final release [1]. #agreed to ship RC4 as final release (with no votes against) The release date is Tuesday, January 15, 2013! Big thanks goes to everyone who helped with this RC3/RC4 testing effort and again to everyone who participated on the whole release. Time for Fedora 18 release parties! Jaroslav [1] http://meetbot.fedoraproject.org/fedora-meeting-2/2013-01-10/f18-go-no-go-s…

1 0

Fedora 18 status is Go, release planned for January 15, 2013
by Jaroslav Reznik 09 Jan '13

09 Jan '13

At the Fedora 18 Go/No-Go Meeting that just occurred, it was agreed to Go for the Fedora 18. The release is planned for Tuesday, January 15, 2013 [1]. See meeting minutes [2]. It was agreed that RC3 is GOLD for now, with possibility to raise the status of RC4 to be the final release based on outcome of supplemental testing due to the late acceptance of bug #810040 [3]. The final call will happen tomorrow, Thursday, January 10 at 16:00 UTC (11 AM EST, 8 AM PST, 17:00 CET), #fedora-meeting-2. Please help Fedora QA with supplemental testing - the RC2/RC3 test results will be pulled into the RC4 test matrices except the test cases required for RC4 re-verification. An email with more details will follow on Test list. Our lovely Spherical Cow would like to thank you everyone for that hard and sometimes dirty work that lead to it's release. Moooooooo! Jaroslav [1] http://fedoraproject.org/wiki/Releases/18/Schedule [2] http://meetbot.fedoraproject.org/fedora-meeting-2/2013-01-09/f18_final_gono… [3] https://bugzilla.redhat.com/show_bug.cgi?id=810040

1 0

[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway 09 Jan '13

09 Jan '13

Some changes to the Fedora Packaging Guidelines have been made: --- If a package is exempt from multilib, it may use %{_prefix}/lib instead of %{_libdir}. Packages that contain architecture specific files that would ordinarily be installed into %{_libexecdir} are always considered ineligible for multilib. However, you should be sure that the (sub)package that they are in does not have other content that would be considered eligible for multilib. If this is not the case for the files you wish to do this in for your package or you are just unsure, ask FESCo for an explicit multilib exemption. https://fedoraproject.org/wiki/Packaging:Guidelines#Multilib_Exempt_Locatio… Please note that FESCo granted an explicit exemption for systemd (and any packages with systemd unit files) to use %{_prefix}/lib/systemd. The core systemd packages were also given permission to be excluded from multilib. --- The section of the Guidelines covering how to handle Troublesome URLs in SourceURL fields has been amended: https://fedoraproject.org/wiki/Packaging:SourceURL#Troublesome_URLs Additionally, a new section has been added to cover how to handle GitHub source files: https://fedoraproject.org/wiki/Packaging:SourceURL#Github --- The Java packaging guidelines were updated for the following changes: * No longer require 2+ jars to be in subdirectory (there was no technical need) * Add standardization for compatibility packages * Remove no longer needed parts about Maven 2 * Improve add_maven_depmap documentation * Add suggestions for pom_ macros instead of patching * installation/use of J2EE APIs standardization (initial version) * JNI guidelines simplification & examples https://fedoraproject.org/wiki/Packaging:Java --- These guideline changes were approved by the Fedora Packaging Committee (FPC). Many thanks to leamas, Stanislav Ochotnicky (and the Java SIG), Kamil Páral, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines. As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure Thanks, ~tom

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce January 2013