From Fedora Project Wiki

< FWN‎ | Beats

 
(26 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
<references/>
 
<references/>
  
===Breaking News of the Week===
+
===Breaking News of the Week and Month===
 +
 
 
====[Guidelines Change] Changes to the Packaging Guidelines====   
 
====[Guidelines Change] Changes to the Packaging Guidelines====   
Tom Callaway
 
Tom Callaway tcallawa at redhat.com
 
Thu Apr 12 20:57:29 UTC 2012
 
lists.fedoraproject.org/pipermail/announce/2012-April/003057.html
 
  
"A bundling exception for boost within Passenger was granted, due to the
+
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
intrusive nature of the forked changes, the efforts of the maintainer to
+
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
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
+
"A new section has been added to the SysV Initscripts section, discussing
boost in sync with the current boost releases.
+
the proper use of subsys locking. Even though Fedora packages should no
 +
longer be using SysV Initscripts as a primary service mechanism, Red Hat
 +
Enterprise Linux and EPEL do. Additionally,
 +
Red Hat points partners to the Fedora Guidelines when they build for RHEL.
 +
<ref>https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism</ref>
  
The package must also include a Requires: bundled(boost) = $VERSION
+
---
where $VERSION is the boost version being bundled.
 
  
https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Packages_granted_exceptions
+
The review guidelines now reflect the use of sha256sum (instead of
 +
md5sum) to confirm upstream source integrity.
 +
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
  
 
---
 
---
  
Packages which have SysV initscripts that contain 'non-standard service
+
The PHP Packaging guidelines have been updated to include guidance about
commands' (commands besides start, stop, reload, restart, or
+
when it is appropriate to have an explicit Requires on httpd & mod_php,
try-restart) must convert those commands into standalone helper scripts.
+
how to handle explicit Requires on PHP extensions, and how to handle a
Systemd does not support non-standard unit commands.
+
Requires for a minimum PHP version.
 +
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement</ref>
 +
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires</ref>
 +
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version</ref>
 +
 
 +
---
  
https://fedoraproject.org/wiki/Packaging:Systemd#Unit_Files
+
A new section on Macros has been added to the Packaging Guidelines,
 +
covering Packaging of Additional RPM Macros.
 +
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>
  
 
---
 
---
  
A section was added to the systemd Packaging Guidelines page with a link
+
A new section on the Documentation= field in systemd unit files (F17+)
to the Tmpfiles.d Packaging Guidelines page, since systemd uses Tmpfiles.d.
+
has been added.
 +
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
 +
 
 +
---
  
https://fedoraproject.org/wiki/Packaging:Systemd#Tmpfiles.d
+
A short section on the Group tag in Fedora packages has been added.
 +
All current versions of Fedora (and their respective RPM versions) treat
 +
the Group tag as optional. Packages may include a Group: field for
 +
compatibility with EPEL, but are not required to do so.
 +
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref>
  
 
---
 
---
  
The Ruby Packaging Guidelines were almost completely rewritten. If you
+
The RHEL conditionalization has been removed from the Python3 example
maintain ruby packages in Fedora, we advise that you review the new
+
spec file, as it is no longer valid.
guidelines.
+
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
 +
 
 +
---
  
https://fedoraproject.org/wiki/Packaging:Ruby
+
These guidelines (and changes) were approved by the Fedora Packaging
 +
Committee (FPC).
  
---
+
'''Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.'''
  
An informational note about Software Collection macros in Fedora
+
As a reminder: The Fedora Packaging Guidelines are living documents! If
Packages was added:
+
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>"
  
https://fedoraproject.org/wiki/Packaging:Guidelines#Software_Collection_Macros
+
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
 +
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
 +
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
  
---
+
<references/>
  
The guidelines relating to PIE and Hardened Packages were updated. Now,
+
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 
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
+
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
keep running until the machine is rebooted, not start on demand and quit
+
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>
on idle.
 
  
* Your package has suid binaries, or binaries with capabilities.
+
"Greetings! (...or perhaps I should say.... bonjour!)
  
* Your package runs as root.
+
I'd like to share a few reminders and announcements regarding the
 +
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
  
https://fedoraproject.org/wiki/Packaging:Guidelines#PIE
+
If you are planning to attend FUDCon and need a travel subsidy to do so,
 +
the ticketing system is now open for those requests.  Requests will be
 +
accepted through August 15, 2012. Please note that funding requests
 +
without a ticket will not be considered. Preference will be given to
 +
attendees from the EMEA region who are actively contributing to Fedora,
 +
and have detailed their participation plans for FUDCon in their request.
  
---
+
To place a subsidy request, please follow these steps:
  
Rules involving appropriate scripting within Fedora Package spec files
+
1: Pre-register at
were added to the Guidelines:
+
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
 +
put an X in the $$$ column
 +
2: Read about the funding request process and place a funding request
 +
ticket in the FUDCon-planning ticket tracker here:
 +
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>
  
https://fedoraproject.org/wiki/Packaging:Guidelines#Scripting_inside_of_spec_files
+
Additionally, a few notes regarding the hotel in Paris:
  
---
+
There are other events in Paris during this time period; most notably,
 +
our first day of FUDCon will be taking place at the Open World Forum
 +
conference, on the day in which the public is encouraged to participate
 +
in and learn about open source projects.  OWF had nearly 2000 attendees
 +
last year.  Accordingly, rooms might be in short supply as we approach
 +
FUDCon; please, book your hotel as soon as possible, not only for
 +
affordability purposes, but also so that you have a bed to sleep in. :)
  
The section in the systemd guidelines covering EnvironmentFiles and
+
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
support for /etc/sysconfig files was revised for clarification.
+
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. 
 +
However, this rate will expire at the end of August, and any remaining
 +
rooms in our block will expire.
  
https://fedoraproject.org/wiki/Packaging:Systemd#EnvironmentFiles_and_support_for_.2Fetc.2Fsysconfig_files
+
For instructions on booking your hotel, please read the Lodging/Hotel
 +
section of the FUDCon: Paris wiki:
 +
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
 +
 +
<references/>
  
---
+
====Fedora Infrastructure announces status.fedoraproject.org==== 
  
The Ada Packaging Guidelines were updated for new rules on packaging
+
* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
source files and updated macros.
+
* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>
  
https://fedoraproject.org/wiki/Packaging:Ada
+
"I'm happy to announce the general availability of our
 +
status.fedoraproject.org site.
  
---
+
This site provides an easy way for Fedora contributors and users to
 +
check on the status of services provided by Fedora Infrastructure.
  
The section of the Packaging Guidelines describing the "bootstrapping"
+
The site auto reloads every minute, and also provides a rss feed at
binary exception was amended for clarification:
+
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.
  
https://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions
+
If you run into a problem or issue that is not reflected at
 +
status.fedoraproject.org, please do report it to us in #fedora-admin on
 +
irc.freenode.net or via ticket at
 +
<ref>https://fedorahosted.org/fedora-infrastructure/newticket</ref>
 +
We update the site status information manually so we need to be aware
 +
of the issue in order to keep the site accurate.
  
---
+
As with everything in Fedora Infrastructure, this application is open
 +
source. Source is available from:
 +
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
 +
and is released under a '''GPLv2+ license'''.
  
The section of the Packaging Guidelines describing Duplication of system
+
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
libraries was amended to clarify the exceptions for Javascript and
+
issues with outages in our infrastructure affecting status reporting. "
parallel stacks.
 
  
https://fedoraproject.org/wiki/Packaging:Guidelines#Duplication_of_system_libraries
+
<references/>
  
---
+
====Beats are open!====
  
These guidelines (and changes) were approved by the Fedora Packaging
+
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
Committee (FPC).
+
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>
  
Many thanks to Kevin Fenzi, Bohuslav Kabrda, Brett Lentz, Marcela
+
"The Release Notes beats for Fedora 18 are now open:
Mašláňová, Bill Nottingham, Vít Ondruch, Mamoru Tasaka, and all of the
+
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
members of the FPC, for assisting in drafting, refining, and passing
 
these guidelines.
 
  
As a reminder: The Fedora Packaging Guidelines are living documents! If
+
If you're looking for a way to dip your toes in the water, so to
you find something missing, incorrect, or in need of revision, you can
+
speak, writing a beat is a great way to get started. If you're a
suggest a draft change. The procedure for this is documented here:
+
regular, don't forget about the checkBeat program:
https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
+
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>
  
Thanks,
+
As a reminder, the wiki drafts of beats are due on 12 September."
"
 
  
 
<references/>
 
<references/>
  
====Announcing the release of Fedora 18 Beta!===
+
=== Fedora Development News ===
Dennis Gilmore
+
The Development Announcement<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref> list is intended to be a LOW TRAFFIC announce-only list for Fedora development.
Dennis Gilmore dennis at ausil.us
 
Tue Apr 17 14:17:02 UTC 2012
 
http://lists.fedoraproject.org/pipermail/announce/2012-April/003058.html
 
http://lists.fedoraproject.org/pipermail/announce/2012-April/003059.html
 
  
"Look, up in the sky! It's a bird, it's a plane, it's... the Beta
+
'''Acceptable Types of Announcements'''
release of Beefy Miracle! Flying 'round the world at the speed of the
+
* Policy or process changes that affect developers.
intertubes, delivering progress, mustard, and freedom to the masses.
+
* Infrastructure changes that affect developers.
 +
* Tools changes that affect developers.
 +
* Schedule changes
 +
* Freeze reminders
  
We are delighted to announce the availability of the Beta release of
+
'''Unacceptable Types of Announcements'''
Fedora 17.  Want to get a taste of the future?  Download it now:
+
* Periodic automated reports (violates the INFREQUENT rule)
 +
* Discussion
 +
* Anything else not mentioned above
  
http://fedoraproject.org/get-prerelease
+
<references/>
 
 
== What is the Beta Release? ==
 
  
The Beta release is the last important milestone of Fedora 17.  Only
+
====New bodhi release in production====
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
+
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
be lurking. A list of the problems we already know about is found at
+
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>
the Common F17 bugs page, seen here:
 
  
http://fedoraproject.org/wiki/Common_F17_bugs
+
"A new release of Bodhi has just been deployed to production.
 +
<ref>https://admin.fedoraproject.org/updates</ref>
  
== Features ==
+
Bugs and enhancement requests can be filed here:
 +
<ref>http://bodhi.fedorahosted.org</ref>
  
This release of Fedora includes a variety of features both over and
+
Major changes in bodhi 0.9.2
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,
+
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
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!
+
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
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
+
* The submitter of an update can no longer effect the karma (Till Maas)
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
+
* Fix duplicate status change email notifications. (Till Maas)
the new features in Fedora 17 is available here:
 
  
http://fedoraproject.org/wiki/Releases/17/FeatureList
+
* Mention age of updates in testing digest mails (Till Maas)
  
We have nightly composes of alternate spins available here:
+
* Support e-mail threading in notification e-mails (Till Maas)
  
http://dl.fedoraproject.org/pub/alt/nightly-composes/
+
* Add X-Bodhi mail headers (Till Maas)
  
== Contributing to Fedora ==
+
* Gracefully handle private bugs (Cole Robinson)
  
For more information on common and known bugs, tips on how to report
+
* Set the default request for new updates to 'testing' in the web form
bugs, and the official release schedule, please refer to the release
 
notes:
 
  
http://docs.fedoraproject.org
+
* Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
  
There are many ways to contribute beyond bug reporting. You can help
+
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
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
 
http://join.fedoraproject.org today!"
 
  
<references/>
 
  
====Fedora 18 Release name voting and Poll for whether to continue naming releases====
+
Full list of changes since 0.8.7
Toshio Kuratomi
+
--------------------------------
Toshio Kuratomi a.badger at gmail.com
 
Fri Apr 20 00:04:15 UTC 2012
 
http://lists.fedoraproject.org/pipermail/announce/2012-April/003060.html
 
  
"Voting for the Fedora 18 release names has begun.  You can find the
+
Kalpa Welivitigoda (1):
potential names in the voting application:
+
      fixed input box alignment issue in login box #579
  https://admin.fedoraproject.org/voting/
 
  
If you are a Fedora contributor (defined as having signed the FPCA and being
+
Luke Macken (25):
in one other Fedora group in the account system) then you are eligilbe to
+
      Convert our tags_url to a byte string before passing it to urlgrabber.
vote.
+
      Add a script to detect when older builds become the 'latest' in stable
 +
      Update our test suite to reproduce ticket [ticket:683]
 +
      Fix a bug in our critpath policy ([ticket:683]).
 +
      Set the default request for new updates to 'testing'
 +
      Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
 +
      Fix a busted unit test (test_push_EPEL_critpath_before_tested)
 +
      Add pkg_resources __requires__ hacks to bodhi tools to mitigate version
 +
conflicts
 +
      Handle the case where a release doesn't have any overrides
 +
      Change our X-Bodhi-Update-Release header to use the short name
 +
      Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
 +
      Update our unit tests to assume submitters cannot alter karma
 +
      Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
 +
      Merge branch 'feature/bodhi1-fedmsg' into develop
 +
      Fix a typo in the metrics tool
 +
      Fix a typo in the new mail headers
 +
      Re-organize our links, and add one to the new update feedback guidelines
 +
      Clean up stray buildroot overrides
 +
      Version bump for 0.9.2
 +
      Our build script uses bz2
 +
      Merge branch 'release/0.9.2'
  
This cycle, the Board is also asking contributors to let us know if we
+
Mathieu Bridon (6):
should continue to have release names for future Fedora releases.  Even
+
      Have bodhi-init create all the tables
though the interface is the same, this portion is intended to be a poll
+
      masher: Fix the comparison
rather than a straight up vote.  The Fedora Board will look at the answers
+
      masher: Reuse variable
to determine if enough contributors value continuing to create release names
+
      setup: Fix the Turbogears version requirement
to make it worthwhile in the future.  If it does seem desirable, the Board
+
      Don't version control auto-generated files
will likely look into forming a working group to come up with a new method
+
      setup: Add missing dependencies
for creating release names for future releases.
 
  
The poll for keeping release names is also found in the voting application:
+
Ralph Bean (19):
  https://admin.fedoraproject.org/voting/
+
      Sending messages with fedmsg.
 +
      No longer using fedmsg schema/validation.
 +
      fedmsg.ini -> fedmsg-config.py
 +
      More detail in the update.complete message.
 +
      More concise send_message calls.
 +
      Ignore dev db.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Updates for the latest fedmsg.  Getting tests passing.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Ignore mashing fedora file.
 +
      Fixed what I think is a regression in login template.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Update to test fedmsg config.  Work with both tests and under WSGI.
 +
      Version bump for fedmsg in staging.
 +
      Only send the comment with a comment is added, not the whole update.
 +
      Using a "bodhi" user/group for mod_wsgi.
 +
      fedmsg+ssl changes to bodhi.spec.
 +
      Use modern fedmsg config format.
 +
      Disable message signing for bodhi tests.
  
Eligibility to answer the poll is the same as for being able to vote on the
+
Till Maas (8):
names themselves (having signed the FPCA and being in one other group)."
+
      Add X-Bodhi mail headers
 +
      Support e-mail threading in notification e-mails
 +
      Mention age of updates in testing digest mails
 +
      Use format string instead of string concatenation
 +
      Import exceptions from sqlite3
 +
      Remove files used by mercurial
 +
      model.py: Change karma from Submitter to 0
 +
      Fix notification on automatic status change"
  
 
<references/>
 
<references/>
  
=== Fedora Development News ===
+
====Build F-18 collection packages for all language translators====
The Development Announcement<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref> list is intended to be a LOW TRAFFIC announce-only list for Fedora development.
+
 
 +
* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref>
 +
* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref>
  
'''Acceptable Types of Announcements'''
+
"Hi Fedora package maintainers
* 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'''
+
Please build and push your package with latest translation file (e.g.
* Periodic automated reports (violates the INFREQUENT rule)
+
pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31.
* Discussion
+
Your packages with latest translation will be composed into test live
* Anything else not mentioned above
+
image on 3-Sep Monday. Then various language translators worldwide will
 +
test the image in their own languages. Any issue will be filed as bug.
 +
This is only one chance for translators to check and modify Localization
 +
quality of your packages by checking UI, and we need your help.
  
<references/>
+
Thank you so much.
  
 +
noriko
 +
Fedora Localization Project"
  
====Fedora 17 Beta Go/No-Go Meeting, Wednesday, March 28, @17:00 Eastern====
+
<references/>
  
Fedora New Project Leader, [[User:Rbergero|Robyn Bergeron]]<ref>rbergero at redhat.com</ref> on Thu Mar 29 20:08:46 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-March/000908.html</ref>,
+
====Fedora 18 Alpha to slip by another one week====
  
"At the Go/No-Go meeting it was decided to slip the Beta by one week<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-03-28/f17_beta_go_no_go_meeting.2012-03-28-21.00.html</ref>.
+
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
Minutes follow below<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-03-28/f17_beta_go_no_go_meeting.2012-03-28-21.00.log.html</ref>.
+
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>
  
Despite valiant efforts by many awesome people, two new blockers
+
"Today at Go/No-Go meeting it was decided to slip Fedora 18
appeared between RC1 and RC2, for which fixes are still incoming and
+
Alpha release by one week due to remaining open blocker bugs<ref>http://qa.fedoraproject.org/blockerbugs/current</ref> and incomplete test matrices for Alpha <ref>https://fedoraproject.org/wiki/Test_Results:Current_Base_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test</ref>. Meeting's
will require the creation of an RC3<ref>http://fedoraproject.org/wiki/Current_Release_Blockers</ref>.
+
full log is at <ref>http://bit.ly/PC16PF</ref>.  
  
As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be  
+
As a result, ALL MAJOR MILESTONES, and their dependent tasks,  
pushed out by one week. Beta will now be looking at an expected release
+
will be pushed out by one week.
of 2012-04-10, and F17 GA is now scheduled for 2012-05-15.
 
  
The adjustments to the full F17 schedule will be done (very late)
+
The next Go/No-Go meeting is on Thursday Sep 06, same place
tonight, and published to the Schedule wiki page<ref>http://fedoraproject.org/wiki/Schedule</ref>. Please note that
+
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
the high-level milestones shown on the wiki page have already been
+
#fedora-meeting).
updated to reflect the Beta slip.
 
  
Thanks for your patience.  We will be meeting again next Wednesday for
+
If you have an accepted blocker bug, please try to fix it
another Go/No-Go meeting."
+
as soon as possible to help us with Fedora 18 Alpha release!"
  
 
<references/>
 
<references/>
 +
  
 
=== Fedora Events ===
 
=== 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.
+
The purpose of Fedora 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 and press releases.
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 (September 2012 - November 2012)====
 +
* '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref>
 +
* '''Central & South America (LATAM)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29</ref>
 +
* '''Europe, Middle East, and Africa (EMEA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2</ref>
 +
* '''India, Asia, Australia (India/APJ)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3</ref>
  
====Upcoming Events (December 2011 - May 2012)====
+
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29</ref>
 
* Central & South America (LATAM): <ref>http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29_2</ref>
 
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q4_.28December_2012_-_February_2013.29</ref>
 
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29_3</ref>
 
  
 
<references/>
 
<references/>
Line 318: Line 372:
 
* [[Event reports]] -- guidelines and suggestions.
 
* [[Event reports]] -- guidelines and suggestions.
 
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
 
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
 +
 +
===Fedora Press Releases===
 +
 +
Fedora press releases will be found at the link:
 +
http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases

Latest revision as of 11:18, 31 August 2012

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

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

  • Contributor: [[User:Spot|Tom Callaway][1]
  • Posted Date: Wed Aug 1 19:28:57 UTC 2012[2]

"A new section has been added to the SysV Initscripts section, discussing the proper use of subsys locking. Even though Fedora packages should no longer be using SysV Initscripts as a primary service mechanism, Red Hat Enterprise Linux and EPEL do. Additionally, Red Hat points partners to the Fedora Guidelines when they build for RHEL. [3]

---

The review guidelines now reflect the use of sha256sum (instead of md5sum) to confirm upstream source integrity. [4]

---

The PHP Packaging guidelines have been updated to include guidance about when it is appropriate to have an explicit Requires on httpd & mod_php, how to handle explicit Requires on PHP extensions, and how to handle a Requires for a minimum PHP version. [5] [6] [7]

---

A new section on Macros has been added to the Packaging Guidelines, covering Packaging of Additional RPM Macros. [8]

---

A new section on the Documentation= field in systemd unit files (F17+) has been added. [9]

---

A short section on the Group tag in Fedora packages has been added. All current versions of Fedora (and their respective RPM versions) treat the Group tag as optional. Packages may include a Group: field for compatibility with EPEL, but are not required to do so. [10]

---

The RHEL conditionalization has been removed from the Python3 example spec file, as it is no longer valid. [11]

---

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

Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, 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: [12]"

Enclosure: Here is one late change to the Fedora Packaging Guidelines:[13] [14] [15]

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

  • Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron][1]
  • Posted Date: Fri Aug 3 17:00:53 UTC 2012[2]

"Greetings! (...or perhaps I should say.... bonjour!)

I'd like to share a few reminders and announcements regarding the upcoming FUDCon in Paris, France, on October 13-15, 2012.

If you are planning to attend FUDCon and need a travel subsidy to do so, the ticketing system is now open for those requests. Requests will be accepted through August 15, 2012. Please note that funding requests without a ticket will not be considered. Preference will be given to attendees from the EMEA region who are actively contributing to Fedora, and have detailed their participation plans for FUDCon in their request.

To place a subsidy request, please follow these steps:

1: Pre-register at [3] - and put an X in the $$$ column 2: Read about the funding request process and place a funding request ticket in the FUDCon-planning ticket tracker here: [4]

Additionally, a few notes regarding the hotel in Paris:

There are other events in Paris during this time period; most notably, our first day of FUDCon will be taking place at the Open World Forum conference, on the day in which the public is encouraged to participate in and learn about open source projects. OWF had nearly 2000 attendees last year. Accordingly, rooms might be in short supply as we approach FUDCon; please, book your hotel as soon as possible, not only for affordability purposes, but also so that you have a bed to sleep in. :)

We currently have a rate of EUR81 per night at the ibis Paris La Vilette Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. However, this rate will expire at the end of August, and any remaining rooms in our block will expire.

For instructions on booking your hotel, please read the Lodging/Hotel section of the FUDCon: Paris wiki: [5]"

Fedora Infrastructure announces status.fedoraproject.org

  • Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ][1]
  • Posted Date: Thu Aug 30 20:31:24 UTC 2012[2]

"I'm happy to announce the general availability of our status.fedoraproject.org site.

This site provides an easy way for Fedora contributors and users to check on the status of services provided by Fedora Infrastructure.

The site auto reloads every minute, and also provides a rss feed at [3].

If you run into a problem or issue that is not reflected at status.fedoraproject.org, please do report it to us in #fedora-admin on irc.freenode.net or via ticket at [4] We update the site status information manually so we need to be aware of the issue in order to keep the site accurate.

As with everything in Fedora Infrastructure, this application is open source. Source is available from: [5] and is released under a GPLv2+ license.

This application is hosted at the link[6] to avoid any issues with outages in our infrastructure affecting status reporting. "

Beats are open!

  • Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton][1]
  • Posted Date: Tue Aug 28 15:35:59 UTC 2012[2]

"The Release Notes beats for Fedora 18 are now open: [3]

If you're looking for a way to dip your toes in the water, so to speak, writing a beat is a great way to get started. If you're a regular, don't forget about the checkBeat program: [4]

As a reminder, the wiki drafts of beats are due on 12 September."

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

New bodhi release in production

  • Contributor: [[User:Lmacken|Luke Macken ][1]
  • Posted Date: Thu Aug 9 21:53:41 UTC 2012[2]

"A new release of Bodhi has just been deployed to production. [3]

Bugs and enhancement requests can be filed here: [4]

Major changes in bodhi 0.9.2


  • fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
  • Re-organized the links on the front page, and link to the new Update Feedback Guidelines
  • The submitter of an update can no longer effect the karma (Till Maas)
  • Fix duplicate status change email notifications. (Till Maas)
  • Mention age of updates in testing digest mails (Till Maas)
  • Support e-mail threading in notification e-mails (Till Maas)
  • Add X-Bodhi mail headers (Till Maas)
  • Gracefully handle private bugs (Cole Robinson)
  • Set the default request for new updates to 'testing' in the web form
  • Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
  • Fixed the input box alignment in the login box (Kalpa Welivitigoda)


Full list of changes since 0.8.7


Kalpa Welivitigoda (1):

     fixed input box alignment issue in login box #579

Luke Macken (25):

     Convert our tags_url to a byte string before passing it to urlgrabber.
     Add a script to detect when older builds become the 'latest' in stable
     Update our test suite to reproduce ticket [ticket:683]
     Fix a bug in our critpath policy ([ticket:683]).
     Set the default request for new updates to 'testing'
     Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
     Fix a busted unit test (test_push_EPEL_critpath_before_tested)
     Add pkg_resources __requires__ hacks to bodhi tools to mitigate version

conflicts

     Handle the case where a release doesn't have any overrides
     Change our X-Bodhi-Update-Release header to use the short name
     Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
     Update our unit tests to assume submitters cannot alter karma
     Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
     Merge branch 'feature/bodhi1-fedmsg' into develop
     Fix a typo in the metrics tool
     Fix a typo in the new mail headers
     Re-organize our links, and add one to the new update feedback guidelines
     Clean up stray buildroot overrides
     Version bump for 0.9.2
     Our build script uses bz2
     Merge branch 'release/0.9.2'

Mathieu Bridon (6):

     Have bodhi-init create all the tables
     masher: Fix the comparison
     masher: Reuse variable
     setup: Fix the Turbogears version requirement
     Don't version control auto-generated files
     setup: Add missing dependencies

Ralph Bean (19):

     Sending messages with fedmsg.
     No longer using fedmsg schema/validation.
     fedmsg.ini -> fedmsg-config.py
     More detail in the update.complete message.
     More concise send_message calls.
     Ignore dev db.
     Merge branch 'master' into bodhi1-fedmsg
     Updates for the latest fedmsg.  Getting tests passing.
     Merge branch 'master' into bodhi1-fedmsg
     Ignore mashing fedora file.
     Fixed what I think is a regression in login template.
     Merge branch 'master' into bodhi1-fedmsg
     Update to test fedmsg config.  Work with both tests and under WSGI.
     Version bump for fedmsg in staging.
     Only send the comment with a comment is added, not the whole update.
     Using a "bodhi" user/group for mod_wsgi.
     fedmsg+ssl changes to bodhi.spec.
     Use modern fedmsg config format.
     Disable message signing for bodhi tests.

Till Maas (8):

     Add X-Bodhi mail headers
     Support e-mail threading in notification e-mails
     Mention age of updates in testing digest mails
     Use format string instead of string concatenation
     Import exceptions from sqlite3
     Remove files used by mercurial
     model.py: Change karma from Submitter to 0
     Fix notification on automatic status change"

Build F-18 collection packages for all language translators

  • Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto][1]
  • Posted Date: Thu Aug 30 09:17:01 UTC 2012[2]

"Hi Fedora package maintainers

Please build and push your package with latest translation file (e.g. pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31. Your packages with latest translation will be composed into test live image on 3-Sep Monday. Then various language translators worldwide will test the image in their own languages. Any issue will be filed as bug. This is only one chance for translators to check and modify Localization quality of your packages by checking UI, and we need your help.

Thank you so much.

noriko Fedora Localization Project"

Fedora 18 Alpha to slip by another one week

  • Contributor: [[User:JaroslavReznik|Jaroslav Reznik][1]
  • Posted Date: Thu Aug 30 23:26:35 UTC 2012[2]

"Today at Go/No-Go meeting it was decided to slip Fedora 18 Alpha release by one week due to remaining open blocker bugs[3] and incomplete test matrices for Alpha [4][5][6]. Meeting's full log is at [7].

As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week.

The next Go/No-Go meeting is on Thursday Sep 06, same place but different time (19:00 UTC, 3 PM EDT, 21:00 CEST

  1. fedora-meeting).

If you have an accepted blocker bug, please try to fix it as soon as possible to help us with Fedora 18 Alpha release!"


Fedora Events

The purpose of Fedora 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 and press releases.

Upcoming Events (September 2012 - November 2012)

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

Guideline to write Fedora Press Releases[5]

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.

Fedora Press Releases

Fedora press releases will be found at the link: http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases