From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 58: Line 58:
Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2900
Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2900


===== Contact Information: ====
===== Contact Information: =====


Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above."
Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above."
Line 127: Line 127:
<references/>
<references/>


==== Call for Test Days for Fedora 16  ====  
==== String Freeze 2011-08-02 ====
[[User:Adamw|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-July/000813.html</ref>:


"Hi, folks. The Test Day cycle for Fedora 16 will open shortly, and we're putting out the call for anyone who has an idea for a Test Day. There are many open slots on the schedule<ref>https://fedoraproject.org/wiki/QA/Fedora_16_test_days</ref> - and if they all fill up or you would like to run a set of Test Days on related topics, we can organize events outside of the scheduled Thursday windows too.
[[User:noriko|Noriko Mizumoto]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000817.html</ref>:


It's often a good idea to have a Test Day for a major change or new feature you're introducing to the distribution, but we can run a Test Day on just about any topic. There is a full guide to organizing Test Days available<ref>https://fedoraproject.org/wiki/QA/SOP_Test_Day_management</ref> - and the QA team is happy both to help you run a Test Day and to butt out and let you run it yourself, whichever you prefer! If you're interested in running a Test Day, please contact QA via the test mailing list, file a ticket in QA trac<ref>https://fedorahosted.org/fedora-qa</ref>  and/or pencil in your event on the schedule, create a Wiki page based on the template (see the SOP for details), and get down to work. Thanks!
"Fedora Packagers


--  
It is String Freeze date on 2011-08-02.
Adam Williamson
Fedora Localization team will soon start translating latest packages via
Fedora QA Community Monkey
Transifex. Our goal is Fedora software translation to be 100% completed
IRC: adamw
as many languages as possible.
http://www.happyassassin.net"
 
Please make sure that your latest POT file has been uploaded to
Transifex for translators.
If you think that you need to break the string freeze, then you should
ask for approval from the Fedora Localization Team prior to breaking the
freeze. Software string freeze policy can be found at<ref>https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy</ref>
 
Thank you so much for your support in advance.
 
Regards,
 
noriko
Fedora L10N"
 
==== Changes to the Packaging Guidelines  ==== 
[[User:Spot|Tom Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-July/000815.html</ref>:
 
"Here are the latest changes to the Fedora Packaging Guidelines:
 
---
 
Some rpm versions pass pathnames to the automatic filtering macros, so a
section has been added to the guidelines to help packagers deal with it<ref>https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Pathnames</ref>
 
---
 
For a while, Fedora considered mono packages to be
architecture-specific, and installed assemblies to %{_libdir}. However,
after discussions with upstream, we now consider mono packages to be
architecture (and platform) independent. This means that mono packages
should be correctly installed into the GAC in /usr/lib or installed into
/usr/lib/PACKAGENAME.
 
As a notable exception, any ELF binary libraries generated in a mono
package must be correctly installed into %{_libdir}, because these files
are architecture-specific.
 
Also, even though we consider mono packages to be architecture
independent, they must not be marked as "noarch". Although the
assemblies are the same, the files may differ due to strings referring
to the build architecture.<ref>https://fedoraproject.org/wiki/Packaging:Mono#File_Locations</ref>
 
---
 
It was decided that gnome shell extension packages should have the
prefix gnome-shell-extension (with no "s" on the end).<ref>https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28gnome_shell_extensions.29</ref>
 
---
 
The section in the Fedora Packaging Guidelines concerning libexecdir has
been improved and expanded<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir</ref>
 
---
 
The Fedora Java Packaging Guidelines have been updated to reflect the
latest macros for Maven 3.<ref>https://fedoraproject.org/wiki/Packaging:Java</ref>
 
---
 
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
 
Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar,
Stanislav Ochotnicky, 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<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
 
Thanks,
 
~spot"


<references/>
<references/>

Revision as of 13:49, 3 August 2011

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Pascal Calarco

Fedora Announcements

Outage: Server reboots - 2011-08-01 14:00 UTC

Kevin Fenzi announced[1]:

"There will be an outage starting at 2011-08-01 14:00 UTC, which will last approximately 2 hours.

To convert UTC to your local time, take a look at[2] or run:

date -d '2011-08-01 14:00 UTC'

Reason for outage:

A number of servers are being upgraded and must be rebooted. Where possible, services should continue to be available during this outage, but users and maintainers may see short periods of instability or interruptions in some services.

Affected Services:
Unaffected Services:

Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2900

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above."

Fedora 15 for IBM System z 64bit official release

Dan Horák announced[1]:

"It's been a longer time since the Fedora 15 release for the primary architectures than we expected, but here we are.

As today, the Fedora IBM System z (s390x) Secondary Arch team proudly presents the Fedora 15 for IBM System z 64bit official release!

And without further ado, here the links to the actual release:

http://secondary.fedoraproject.org/pub/fedora-secondary/releases/15/Fedora/s390x/

http://secondary.fedoraproject.org/pub/fedora-secondary/releases/15/Everything/s390x/os/

and obviously on all mirrors that mirror the secondary arch content.

The first directory contains the normal installation trees as well as one DVD ISO with the complete release.

Everything as usual contains, well, everything. :)

For Fedora 14 we have collected a couple of example config files, kickstart examples and a nice README here[2]

beware that currently the content there is outdated, but most of the information should be still valid. We're working on fixing that over the next weeks.

Additional information about know issues, the current progress and state for future release, where and how the team can be reached and just anything else IBM System z on Fedora related can be found here[3] for architecture specific release notes and here[4] for more general s390x notes.

Thanks go out to everyone involved in making this happen!

Your Fedora/s390x Maintainers

-- Dan Horák, RHCE Senior Software Engineer, BaseOS

Red Hat Czech s.r.o., Purkyňova 99, 612 45 Brno"

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

String Freeze 2011-08-02

Noriko Mizumoto announced[1]:

"Fedora Packagers

It is String Freeze date on 2011-08-02. Fedora Localization team will soon start translating latest packages via Transifex. Our goal is Fedora software translation to be 100% completed as many languages as possible.

Please make sure that your latest POT file has been uploaded to Transifex for translators. If you think that you need to break the string freeze, then you should ask for approval from the Fedora Localization Team prior to breaking the freeze. Software string freeze policy can be found at[2]

Thank you so much for your support in advance.

Regards,

noriko Fedora L10N"

Changes to the Packaging Guidelines

Tom Callaway announced[3]:

"Here are the latest changes to the Fedora Packaging Guidelines:

---

Some rpm versions pass pathnames to the automatic filtering macros, so a section has been added to the guidelines to help packagers deal with it[4]

---

For a while, Fedora considered mono packages to be architecture-specific, and installed assemblies to %{_libdir}. However, after discussions with upstream, we now consider mono packages to be architecture (and platform) independent. This means that mono packages should be correctly installed into the GAC in /usr/lib or installed into /usr/lib/PACKAGENAME.

As a notable exception, any ELF binary libraries generated in a mono package must be correctly installed into %{_libdir}, because these files are architecture-specific.

Also, even though we consider mono packages to be architecture independent, they must not be marked as "noarch". Although the assemblies are the same, the files may differ due to strings referring to the build architecture.[5]

---

It was decided that gnome shell extension packages should have the prefix gnome-shell-extension (with no "s" on the end).[6]

---

The section in the Fedora Packaging Guidelines concerning libexecdir has been improved and expanded[7]

---

The Fedora Java Packaging Guidelines have been updated to reflect the latest macros for Maven 3.[8]

---

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

Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar, Stanislav Ochotnicky, 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[9]

Thanks,

~spot"

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 (June - August 2011)

  • North America (NA)[1]
  • Central & South America (LATAM): [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Past Events

Archive of Past Fedora Events[1]

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.