From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
 
(297 intermediate revisions by 3 users not shown)
Line 2: Line 2:
==Announcements==
==Announcements==


In this section, we cover announcements from the Fedora Project, including general announcements<ref>
Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements<ref>http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Fedora Events<ref>http://fedoraproject.org/wiki/Events</ref>.
http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Events<ref>http://fedoraproject.org/wiki/Events</ref>.


Contributing Writer: [[User:Rashadul|Rashadul Islam]]
Contributing Writer: [[User:rashadul|Rashadul Islam]]


<references/>
<references/>
===FEDORA ANNOUNCEMENTS===
====Notice: dnssec-conf updates in Fedora 11 and 12====
[[User:stickster|Paul W. Frields]], Fedora Project Leader, announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-February/002765.html</ref> that the Fedora Project recently had been issued an update to the dnssec-conf package, to fix an issue that had been caused Fedora 11 and 12 systems using BIND (named) to put an inordinately heavy load on RIPE nameservers. He also mentioned, "However, this update has been found to break some BIND configurations
as seen in this bug: <ref>https://bugzilla.redhat.com/show_bug.cgi?id=563232</ref>


'''The problem occurs in these packages:'''
===Breaking News of the Week and Month===
* dnssec-conf-1.21-3.fc11
* dnssec-conf-1.21-7.fc12


To determine if your system is affected, run the following command:
====[Guidelines Change] Changes to the Packaging Guidelines==== 
* rpm -q dnssec-conf


If one of the above package descriptors does not appear, your system
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
is not affected and you may safely ignore this message. If you are
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
affected, please continue reading.


* '''Workaround'''
"A new section has been added to the SysV Initscripts section, discussing
If you have already accepted this update, you can downgrade the
the proper use of subsys locking. Even though Fedora packages should no
package and start the failed BIND (named) daemon again using these
longer be using SysV Initscripts as a primary service mechanism, Red Hat
commands:
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>


* su -c 'yum downgrade dnssec-conf'
---
* su -c 'service named start'


* '''Solution'''
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>


System owners running BIND name servers on Fedora 11 or 12 systems are advised not to accept the specific dnssec-conf pacakge updates listed above.  There are several ways to avoid these specific updates.
---
* If you use the PackageKit graphical client, or another graphical client, deselect the dnssec-conf update in the dialog that lists package updates.


* If you use the yum command-line client, use this command to exclude dnssec-conf from the list of packages to be updated:
The PHP Packaging guidelines have been updated to include guidance about
* su -c 'yum --exclude=dnssec-conf update'
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.
<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>


* '''Remediation'''
---
A new update is being prepared to address this problem for Fedora 11 and 12 users, and will be pushed to our mirrors as soon as possible.
Users who are not running BIND nameservers (named) on their Fedora 11 and 12 can safely disregard this notice.  When the new updates are
pushed, a follow-up announcement will be made here.  At that time, affected system owners can safely accept the replacement updates."


<references/>
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 new section on the Documentation= field in systemd unit files (F17+)
has been added.
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
 
---
 
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 RHEL conditionalization has been removed from the Python3 example
spec file, as it is no longer valid.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
 
---


====Notice: dnssec-conf updates in Fedora 11 and 12====
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).


On Tue, Feb 09, 2010 at 05:29:27PM -0500, [[User:stickster|Paul W. Frields]] wrote:
'''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.'''
* Remediation:
A new update is being prepared to address this problem for Fedora 11 and 12 users, and will be pushed to our mirrors as soon as possible. Users who are not running BIND nameservers (named) on their Fedora 11 and 12 can safely disregard this notice.  When the new updates are pushed, a follow-up announcement will be made here.  At that time,affected system owners can safely accept the replacement updates.


On Thu, Feb 11, 2010 at 16:13:52 UTC 2010, Fedora Project Leader [[User:stickster|Paul W. Frields]] briefed<ref>http://lists.fedoraproject.org/pipermail/announce/2010-February/002768.html</ref>, "Packages are now available in the updates-testing repository, and most mirrors should include them at this point.  Community testing for
As a reminder: The Fedora Packaging Guidelines are living documents! If
these packages would be appreciated.  To install them:
you find something missing, incorrect, or in need of revision, you can
* su -c 'yum --enablerepo=updates-testing update dnssec-conf'
suggest a draft change. The procedure for this is documented here:
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"


To report findings:
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
* '''Fedora 11:''' <ref>https://admin.fedoraproject.org/updates/F11/FEDORA-2010-1696</ref>
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
* '''Fedora 12:''' <ref>https://admin.fedoraproject.org/updates/F12/FEDORA-2010-1748</ref>"
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>


<references/>
<references/>


====Fedora 12 re-spins Released====
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====  
 
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>
 
"Greetings! (...or perhaps I should say.... bonjour!)


[[User:Jbwillia|Ben Williams]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-February/002766.html</ref> that the Fedora Unity Project was proud to announce the release of new ISO Re-Spins of Fedora 12. He also mentioned, " These Re-Spin ISOs are based on the officially released Fedora 12 installation media and include all updates released as of February  2nd, 2010.
I'd like to share a few reminders and announcements regarding the  
The ISO images are available for i386, x86_64, architectures via Jigdo or Torrent starting Wednesday  February 10th, 2010 (saving about 437MB of updates for a default install).
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.


Go to <ref>http://spins.fedoraunity.org/spins</ref> to get the bits!
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.


We are glad to be able to announce the current Fedora 12 Re-Spin, 20100202, despite problems in this Re-Spin. Nonetheless, we, Fedora Unity, have decided to release this Re-Spin with the following side-note:
To place a subsidy request, please follow these steps:


'''Due to a newly discovered  bug the re-spins do not include all the SCSI drivers (BUSLOGIC as an example which is used by VMware)'''
1: Pre-register at
<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>


We would like to give a special thanks to the following for testing this Re-Spin:
Additionally, a few notes regarding the hotel in Paris:


* vwbusguy-              Scott Williams
There are other events in Paris during this time period; most notably,
* Southern_Gentleman      Ben Williams
our first day of FUDCon will be taking place at the Open World Forum
* kanarip                Jeroen van Meeuwen
conference, on the day in which the public is encouraged to participate
* fenrus2                Dennis Johnson
in and learn about open source projects.  OWF had nearly 2000 attendees
* BobLfoot                Bob Lightfoot
last year.  Accordingly, rooms might be in short supply as we approach
* adm1                    Davis Leggett
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. :)


Fedora Unity Re-Spin 20100202 Changelog (<ref>http://spins.fedoraunity.org/changelogs/20100202/</ref> )
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.


'''Testing Results'''
For instructions on booking your hotel, please read the Lodging/Hotel
A full test matrix can be found at our Test Matrix (<ref>http://spins.fedoraunity.org/Members/Southern_Gentleman/F12-20100202-matrix/</ref>)
section of the FUDCon: Paris wiki:
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
<references/>


'''About Fedora Unity Re-Spins'''
====Fedora Infrastructure announces status.fedoraproject.org==== 


Fedora Unity has taken up the Re-Spin task to provide the community with the chance to install Fedora with recent updates already included.
* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>


This is a community project, for and by the community. You can contribute to the community by joining our test process.
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


Go to <ref>http://spins.fedoraunity.org/spins</ref> to get the bits!
This site provides an easy way for Fedora contributors and users to
check on the status of services provided by Fedora Infrastructure.


'''Assistance Needed'''
The site auto reloads every minute, and also provides a rss feed at
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.


If you are interested in helping with the testing or mirroring efforts, please contact the Fedora Unity team.
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.


Contact information is available at <ref>http://fedoraunity.org/<ref> or the #fedora-unity channel on the Freenode IRC Network (irc.freenode.net).
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'''.  


To report bugs in the Re-Spins please use <ref>http://bugs.fedoraunity.org/</ref>"
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
issues with outages in our infrastructure affecting status reporting. "


<references/>
<references/>


====New paths for development====
====Beats are open!====
 
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>


[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-February/002767.html</ref>,"As part of the No Frozen Rawhide<ref>https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal</ref> initiative, a couple new paths are showing up on our public mirrors.  Previously rawhide was published to pub/fedora/linux/development/<arch>.  In the very near future that path will change to pub/fedora/linux/development/rawhide/<arch>.  At the same time, a new path will appear, pub/fedora/linux/development/13/<arch>. This path will be where the Fedora 13 stabilization happens as we work toward releasing Fedora 13.  Rawhide will move on and start seeing changes more appropriate for Fedora 14 and beyond.
"The Release Notes beats for Fedora 18 are now open:
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


This change will happen at the Alpha freeze point, which is this coming Tuesday. In the mean time, these new paths are visible on our master mirror but they are just hardlinks back to the existing content in pub/fedora/linux/development/<arch> These hardlinks are there to help mirrors prepare for the new paths.
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:
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>


Look forward to more announcements regarding No Frozen Rawhide as the freeze date nears!"
As a reminder, the wiki drafts of beats are due on 12 September."


<references/>
<references/>


===FEDORA DEVELOPMENT NEWS===
=== Fedora Development News ===
[[User:Poelstra|John Poelstra]]
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.
[[User:Mmcgrath | Mike McGrath]]


====qt-4.6/kde-4.4 updates==== 
'''Acceptable Types of Announcements'''
[[User:Rdieter|Rex Dieter]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000560.html</ref>, "the kde-sig is beginning work to prepare qt-4.6/kde-4.4 updates, which will be landing in f11 and f12 koji buildroots shortly.
* Policy or process changes that affect developers.
* Infrastructure changes that affect developers.
* Tools changes that affect developers.
* Schedule changes
* Freeze reminders


Maintainers of qt/kde packages, please be aware of this if doing builds yourself.  If you have any concerns or questions, please drop by #fedora-kde on freenode/irc (or followup to this on -devel list)."
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


<references/>
<references/>


====No Frozen Rawhide coming soon! New paths on mirrors!====  
====New bodhi release in production====
[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000561.html</ref>,"With a burst of testing last week, we confirmed that our infrastructure should handle No Frozen Rawhide<ref>http://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal</ref>. Feature freeze is tomorrow, which is when we'd branch our source control, and when we'd enact no frozen rawhide. The timing is a bit tight, so we may have to delay a day or two in order to get this done, but the end result would be two nightly trees being published.
 
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>
 
"A new release of Bodhi has just been deployed to production.
<ref>https://admin.fedoraproject.org/updates</ref>
 
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>
 
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)


/pub/fedora/linux/development/rawhide/  will become the new path of Rawhide.  It will continue to not have install images, and it will be the place where builds from the devel branch in CVS go to.  It'll be  Fedora 14 intended content.
* Add X-Bodhi mail headers (Till Maas)


/pub/fedora/linux/development/13/  will become the new path of the branched Fedora 13 content.  This is where builds from the F-13/ branch
* Gracefully handle private bugs (Cole Robinson)
in CVS will go, after they pass through bodhi as "stable".


/pub/fedora/linux/updates/testing/13/  will be where potential Fedora 13 builds go after passing through bodhi as "testing".  This is where you'll find the latest stuff proposed for freeze break and where testing and peer review of these freeze breaks will happen.  When a maintainer feels enough testing has happened, or enough karma triggers the bodhi auto request, the build will be marked "stable" and show up in the development/13 tree at the next nightly compose.
* Set the default request for new updates to 'testing' in the web form


Even though we've been talking about No Frozen Rawhide for quite a while, this will indeed surprise some people, so we will be trying to be
* 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.
extra verbose in what we are doing over the next few days, and always available for questions.  Unfortunately I have to step out for a few
hours and thus any responses to this email will not be seen by me for a few hours.


You can find us at #fedora-devel on Freenode if you wish to discuss live, or help us with documenting these changes and setting expectations
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
with our developers and users."


He would be updating <ref>http://fedoraproject.org/wiki/No_Frozen_Rawhide_Implementation</ref> with current progress and plans.


<references/>
Full list of changes since 0.8.7
--------------------------------


====LD Changes To Implicit DSO Linking Update==== 
Kalpa Welivitigoda (1):
Charley Wang announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000563.html</ref>, "This is an update to let maintainers know that the changes to LD outlined here :
      fixed input box alignment issue in login box #579
<ref>https://fedoraproject.org/wiki/Features/ChangeInImplicitDSOLinking</ref>
have been pushed to Fedora rawhide.


The details behind what this feature will do, along with how to get failing packages to build can be found here : <ref>https://fedoraproject.org/wiki/UnderstandingDSOLinkChange</ref>
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'


Also, packages that have failed to build under these new changes can be found here : <ref>https://fedoraproject.org/wiki/DSOLinkBugs</ref>
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


Roland Grunberg and I will rebuild these packages continually and update the DSOLinkBugs when we can and/or suggest patches.
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.


We will also be available as much as possible via e-mail and on IRC freenode at #fedora-DSO to help you make the necessary changes." He also thanked everyone for their time.
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"


<references/>
<references/>


====Fedora 13 Alpha Freeze in one week (minus one day)!====  
====Build F-18 collection packages for all language translators====
[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000564.html</ref> on Thu Feb at 11 00:23:55 UTC 2010 that the Fedora 13 Alpha freeze is this coming Tuesday.
 
<ref>https://fedoraproject.org/wiki/Alpha_Freeze_Policy</ref>
* 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>
 
"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.


Jessy also briefed, "This time around things are going to be different and interesting. We're in the middle of deploying No Frozen Rawhide <ref>https://fedoraproject.org/wiki/No_Frozen_Rawhide_Proposal</ref> which will change how freeze breaks are requested.  The intention is to use bodhi to submit update requests for Fedora 13.  When requested for testing, these will be published to the fedora 13 updates-testing repo where peers can review and provide karma on your request.  If marked stable, they will go into pub/fedora/linux/development/13 and be included in the Alpha. We're still working on the documentation for all of this.
Thank you so much.


More announcements to come!"
noriko
Fedora Localization Project"


<references/>
<references/>


====Fedora 13 Milestone Reached: Feature Freeze-2010-02-09====  
====Fedora 18 Alpha to slip by another one week====
[[User:Poelstra|John Poelstra]] announced <ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000565.html</ref>, "A friendly reminder that yesterday, February 9, 2010, we reached Feature Freeze for Fedora 13."
 
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>
 
"Today at Go/No-Go meeting it was decided to slip Fedora 18
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
full log is at <ref>http://bit.ly/PC16PF</ref>.  


A summary of the Fedora 13 milestones and exception process is here:
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
<ref>https://fedoraproject.org/wiki/Important_Release_Milestones</ref>
will be pushed out by one week.


As previously noted, at Feature Freeze it is expected that all features are *significantly* "feature complete" and ready for testing:  
The next Go/No-Go meeting is on Thursday Sep 06, same place
<ref>https://fedoraproject.org/wiki/Feature_Freeze_Policy<ref>.
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
#fedora-meeting).


A review of the status section on the following feature pages shows that the following feature pages have had a recent update OR the feature does not appear to be "feature complete" based on the information provided.
If you have an accepted blocker bug, please try to fix it
as soon as possible to help us with Fedora 18 Alpha release!"


<ref>https://fedoraproject.org/wiki/Features/BetterWebcamSupportF13</ref>
<references/>
<ref>https://fedoraproject.org/wiki/Features/Gnome2.30</ref>
<ref>https://fedoraproject.org/wiki/Features/IntelliJ_IDEA</ref>
<ref>https://fedoraproject.org/wiki/Features/NetworkManagerCmdline</ref>
<ref>https://fedoraproject.org/wiki/Features/NetworkManagerMobileStatus</ref>
<ref>https://fedoraproject.org/wiki/Features/NouveauDisplayPort</ref>
<ref>https://fedoraproject.org/wiki/Features/SystemtapStaticProbes</ref>
<ref>https://fedoraproject.org/wiki/Features/UdisksImprovements</ref>


Feature owners, please update your feature page as soon as possible so that we have the most current information possible going into our first test release.  Feature pages which remain updated or feature incomplete by 2010-02-16 will be sent to FESCo for review.


p.s. All feature owners have been bcc'd on this email."
=== Fedora Events ===


<references/>
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.


===FEDORA EVENTS===
====Upcoming Events (September 2012 - November 2012)====
Fedora events are the 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!
* '''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 2009 to February 2010)====
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#FY10_Q4_.28December_2009_-_February_2010.29</ref>
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q4_.28December_2009_-_February_2010.29_2</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q4_.28December_2009_-_February_2010.29_3</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY10_Q4_.28December_2009_-_February_2010.29_4</ref>


<references/>
<references/>
Line 216: Line 366:


====Additional information====
====Additional information====
* '''[[Reimbursements]] -- reimbursement guidelines.'''
* [[Reimbursements]] -- reimbursement guidelines.
* '''[[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).'''
* [[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).
* '''[[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.'''
* [[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.
* [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
* [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
* [[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