FWN/Beats/Announcements

From FedoraProject

< FWN | Beats
Revision as of 17:28, 20 April 2012 by Rashadul (Talk | contribs)

Jump to: navigation, search

Contents

Announcements

Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements[1], development announcements[2] and Fedora Events[3].

Contributing Writer: Rashadul Islam

  1. http://lists.fedoraproject.org/pipermail/announce/
  2. http://lists.fedoraproject.org/pipermail/devel-announce/
  3. http://fedoraproject.org/wiki/Events

Breaking News of the Week

[Guidelines Change] Changes to the Packaging Guidelines

Tom Callaway[1] on Thu Apr 12 20:57:29 UTC 2012 announced[2],

"A bundling exception for boost within Passenger was granted, due to the intrusive nature of the forked changes, the efforts of the maintainer to merge as many of them as possible into the upstream boost source tree, and the visible efforts of the upstream to keep the bundled copy of boost in sync with the current boost releases.

The package must also include a Requires: bundled(boost) = $VERSION where $VERSION is the boost version being bundled.

[3]

Packages which have SysV initscripts that contain 'non-standard service commands' (commands besides start, stop, reload, restart, or try-restart) must convert those commands into standalone helper scripts. Systemd does not support non-standard unit commands.

[4]

A section was added to the systemd Packaging Guidelines page with a link to the Tmpfiles.d Packaging Guidelines page, since systemd uses Tmpfiles.d.

[5]

The Ruby Packaging Guidelines were almost completely rewritten. If you maintain ruby packages in Fedora, we advise that you review the new guidelines.

[6]

An informational note about Software Collection macros in Fedora Packages was added:

[7]

The guidelines relating to PIE and Hardened Packages were updated. Now, if your package meets the following critera you MUST enable the PIE compiler flags:

  • Your package is long running. This means it's likely to be started and

keep running until the machine is rebooted, not start on demand and quit on idle.

  • Your package has suid binaries, or binaries with capabilities.
  • Your package runs as root.

[8]

Rules involving appropriate scripting within Fedora Package spec files were added to the Guidelines:

[9]

The section in the systemd guidelines covering EnvironmentFiles and support for /etc/sysconfig files was revised for clarification.

[10]

The Ada Packaging Guidelines were updated for new rules on packaging source files and updated macros.

[11]

The section of the Packaging Guidelines describing the "bootstrapping" binary exception was amended for clarification:

[12]

The section of the Packaging Guidelines describing Duplication of system libraries was amended to clarify the exceptions for Javascript and parallel stacks.

[13]

These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).

Many thanks to Kevin Fenzi, Bohuslav Kabrda, Brett Lentz, Marcela Mašláňová, Bill Nottingham, Vít Ondruch, Mamoru Tasaka, 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: [14]

Thanks"

  1. tcallawa at redhat.com
  2. lists.fedoraproject.org/pipermail/announce/2012-April/003057.html
  3. https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Packages_granted_exceptions
  4. https://fedoraproject.org/wiki/Packaging:Systemd#Unit_Files
  5. https://fedoraproject.org/wiki/Packaging:Systemd#Tmpfiles.d
  6. https://fedoraproject.org/wiki/Packaging:Ruby
  7. https://fedoraproject.org/wiki/Packaging:Guidelines#Software_Collection_Macros
  8. https://fedoraproject.org/wiki/Packaging:Guidelines#PIE
  9. https://fedoraproject.org/wiki/Packaging:Guidelines#Scripting_inside_of_spec_files
  10. https://fedoraproject.org/wiki/Packaging:Systemd#EnvironmentFiles_and_support_for_.2Fetc.2Fsysconfig_files
  11. https://fedoraproject.org/wiki/Packaging:Ada
  12. https://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions
  13. https://fedoraproject.org/wiki/Packaging:Guidelines#Duplication_of_system_libraries
  14. https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure

Announcing the release of Fedora 18 Beta!

Dennis Gilmore[1] on Tue Apr 17 14:17:02 UTC 2012 announced in two thread[2][3],

"Look, up in the sky! It's a bird, it's a plane, it's... the Beta release of Beefy Miracle! Flying 'round the world at the speed of the intertubes, delivering progress, mustard, and freedom to the masses.

We are delighted to announce the availability of the Beta release of Fedora 17. Want to get a taste of the future? Download it now:

[4]

What is the Beta Release?

The Beta release is the last important milestone of Fedora 17. Only critical bug fixes will be pushed as updates leading to the general release of Fedora 17 in May. We invite you to join us in making Fedora 17 a solid release by downloading, testing, and providing your valuable feedback.

Of course, this is a beta release, meaning that some problems may still be lurking. A list of the problems we already know about is found at the Common F17 bugs page, seen here:

[5]

Features

This release of Fedora includes a variety of features both over and under the hood that show off the power and flexibility of the advancing state of free software. Here are just a few of the new features:

On the desktop: GNOME 3.4 introduces many user experience improvements, including new search capabilities in the activities overview, improved themes, and enhancements to the Documents and Contacts applications. A new application, GNOME-boxes, provides easy access to virtual machines. Additionally, GIMP 2.8, the newest version of the GNU Image Manipulation Program, brings new improvements such as single-window mode, layer groups, and on-canvas editing.

For developers: You never sausage a great array of development tools! Fedora 17 includes a pre-release of Juno, the release of the Eclipse SDK expected in June 2012. Java 7 (and OpenJDK 7) is the default Java runtime and Java build toolset, and GCC 4.7.x is now the primary compiler in Fedora. Other language refreshes include shipping Ruby 1.9.3, the latest stable version of the Ruby language, PHP 5.4, the latest PHP stack, and Erlang has also been updated to the R15 release.

Under the hood, and in the cloud: The Cluster stack in Fedora includes numerous and significant updates for both high availability and load-balancing applications. Fedora 17 utilizes Linux kernel 3.3, with improved btrfs and ext4 filesystems, GMA (poulsbo) graphics and Broadcom wireless chipset support, and numerous other bug fixes and enhancements. Firewalld is now the default firewall solution in Fedora, providing dynamic firewall configuration capabilities. Finally, OpenStack, a collection of services that can be used to set up and run cloud compute and storage infrastructure, has been updated to the latest release, 2012.1 (Essex).

And that's only the beginning. A more complete list and details of all the new features in Fedora 17 is available here:

[6]

We have nightly composes of alternate spins available here:

[7]

Contributing to Fedora

For more information on common and known bugs, tips on how to report bugs, and the official release schedule, please refer to the release notes:

[8]

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, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. To get started, visit [9] today!"

  1. dennis at ausil.us
  2. http://lists.fedoraproject.org/pipermail/announce/2012-April/003058.html
  3. http://lists.fedoraproject.org/pipermail/announce/2012-April/003059.html
  4. http://fedoraproject.org/get-prerelease
  5. http://fedoraproject.org/wiki/Common_F17_bugs
  6. http://fedoraproject.org/wiki/Releases/17/FeatureList
  7. http://dl.fedoraproject.org/pub/alt/nightly-composes/
  8. http://docs.fedoraproject.org
  9. http://join.fedoraproject.org

Fedora 18 Release name voting and Poll for whether to continue naming releases

Toshio Kuratomi [1] on Fri Apr 20 00:04:15 UTC 2012 announced[2],

"Voting for the Fedora 18 release names has begun. You can find the potential names in the voting application: [3]

If you are a Fedora contributor (defined as having signed the FPCA and being in one other Fedora group in the account system) then you are eligilbe to vote.

This cycle, the Board is also asking contributors to let us know if we should continue to have release names for future Fedora releases. Even though the interface is the same, this portion is intended to be a poll rather than a straight up vote. The Fedora Board will look at the answers to determine if enough contributors value continuing to create release names to make it worthwhile in the future. If it does seem desirable, the Board will likely look into forming a working group to come up with a new method for creating release names for future releases.

The poll for keeping release names is also found in the voting application: [4]

Eligibility to answer the poll is the same as for being able to vote on the names themselves (having signed the FPCA and being in one other group)."

  1. a.badger at gmail.com
  2. http://lists.fedoraproject.org/pipermail/announce/2012-April/003060.html
  3. https://admin.fedoraproject.org/voting/
  4. https://admin.fedoraproject.org/voting/

Fedora Development News

The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above
  1. https://admin.fedoraproject.org/mailman/listinfo/devel-announce

Fedora 17 for Power Alpha Announcement

David Aquilina[1] on Tue Apr 10 19:51:42 UTC 2012 announced[2],

"Time flies like the wind...

As it's already time again for another Fedora release on Power, this time for Fedora 17 Alpha.

We've hit a couple of bumps along the road to the Alpha, but at long last we're finally at a state where we're ready to release it to the public.

Due to lack of developer time and hardware, Apple hardware support is at this point completely untested. Especially with the switch to grub2 we rely on community feedback and participation to make this work for this release. So if you have the hardware and want it to work, patches welcome! :)

The bits are available from your closest mirror:

[3]

More details about this Alpha release can be found here:

[4]

One of our focuses in the lead up to the beta of Fedora 17 for Power will be addressing architecture-specific packaging issues in as many packages as possible. If you own a package in Fedora which has ExclusiveArch or ExcludeArch set, please take a moment to verify that the architectures you've excluded or are exclusive to are still correct and sane.

I want to thank everyone involved in making this happen once more. Many Fedora packagers and contributors have again stepped up and helped fix issues that only appeared on Power hardware. Moreover the whole Fedora Secondary Arch team has been doing a fantastic job to get us to where we are now, especially considering that we had a complete switch of builders and hub hardware, mass rebuild and a hub failure along the way!

As usual, you can reach the whole team on the #fedora-ppc IRC channel on FreeNode and via our email list:

[5]

And we have our Secondary Arch wiki with (decently) updated information:

[6]

For Phil, Karsten, and the entire Fedora for Power team, Thanks & regards, David"

  1. dwa at redhat.com
  2. http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000913.html
  3. https://mirrors.fedoraproject.org/publiclist/Fedora/17-Alpha/ppc64/
  4. https://fedoraproject.org/wiki/Fedora_17_Alpha_PPC_release_notes
  5. https://admin.fedoraproject.org/mailman/listinfo/ppc
  6. http://fedoraproject.org/wiki/Architectures/PowerPC

Fedora 17 Beta Go/No-Go Meeting, Round 3, Wednesday, April 11, @17:00 Eastern

Fedora New Project Leader, Robyn Bergeron[1] on Wed Apr 11 03:23:31 UTC 2012 announced[2],

"Please join us on irc.freenode.net in #fedora-meeting-1 for this important meeting. This will be Round 3 of this meeting for the Beta release of F17.

Wednesday, April 11, 2012 @21:00 UTC (17:00 EDT/14:00 PDT)

"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: [3]

In the meantime, keep an eye on the Fedora 17 Beta Blocker list: [4]

Ongoing Beta RC test results can be seen here: [5]

See you there, Wednesday, in #fedora-meeting-1.

-Robyn, fingers and toes crossed thoroughly"

  1. rbergero at redhat.com
  2. http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000914.html
  3. https://fedoraproject.org/wiki/Go_No_Go_Meeting
  4. http://fedoraproject.org/wiki/Current_Release_Blockers
  5. https://fedoraproject.org/wiki/Category:Fedora_17_Beta_RC_Test_Results

Fedora 17 Beta is declared GOLD

Robyn Bergeron - Fedora Project Leader[1] on Thu Apr 12 05:11:27 UTC 2012 announced[2],

"At today's F17 Beta Go/No-Go meeting, the Fedora 17 Beta release was declared gold. F17 Beta will be released Tuesday, April 17, 2012.

Thanks to everyone involved for pulling this one together and participating in the meetings, things came together well this week. :)

For those interested in the details:

Minutes: [3] Logs: [4]

Full minutes follow below.


Fedora-meeting-1: F17 Beta go no go meeting

Meeting started by rbergeron at 21:00:32 UTC. The full logs are available at [5]"

  1. rbergero at redhat.com
  2. http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000915.html
  3. http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.html
  4. http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.log.html
  5. http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.log.html

Fedora Events

The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (December 2011 - May 2012)

  • North America (NA)[1]
  • Central & South America (LATAM): [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]
  1. http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29
  2. http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29_2
  3. http://fedoraproject.org/wiki/Events#FY12_Q4_.28December_2012_-_February_2013.29
  4. http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29_3

Past Events

Archive of Past Fedora Events[1]

  1. http://fedoraproject.org/wiki/FedoraEvents/PastEvents

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.