FWN/Beats/Announcements: Difference between revisions

     fixed input box alignment issue in login box #579

     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

     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'

     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

     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.

     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"

Search

FWN/Beats/Announcements: Difference between revisions

Latest revision as of 11:18, 31 August 2012

Contents

Announcements

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

Fedora Infrastructure announces status.fedoraproject.org

Beats are open!

Fedora Development News

New bodhi release in production

Build F-18 collection packages for all language translators

Fedora 18 Alpha to slip by another one week

Fedora Events

Upcoming Events (September 2012 - November 2012)

Past Events

Additional information

Fedora Press Releases

@@ Line 2: / Line 2: @@
 ==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/>
-===Fedora Announcement News===
+===Breaking News of the Week and Month===
-====F13 Release Events - Mission completed!====
+====[Guidelines Change] Changes to the Packaging Guidelines====
-[[User:Jsimon|Joerg Simon]]<ref>Joerg Simon</ref> on Monday, July 26 at 10:26:52 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-July/002841.html</ref>,"FAmSCo want to thank all of you who held a F13 Release Party<ref>https://fedoraproject.org/wiki/F13_release_events</ref>!
-A special thank you goes out to all of you who posted Event Reports before the DeadLine<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2010-06-07/fedora-meeting-1.2010-06-07-18.05.html</ref>!
+* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
+* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
-Now it is Dinner-Time ;) pick 5 of your regional Fellows and/or Friends and have a great Evening -
+"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.
+<ref>https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism</ref>
-we will pay for your Food and Drinks as a Thank You.
+---
-* Bert Desmet <ref>http://fedoraproject.org /wiki/Release_Party_F13_Ghent#Reports</ref>
+The review guidelines now reflect the use of sha256sum (instead of
-* Pierros Papadeas <ref>http://pierros.papadeas.gr/?p=133</ref>
+md5sum) to confirm upstream source integrity.
-* René Jr Purcell <ref>http://arsenicks.wordpress.com/2010/06/17/fedora-13-release-party-quebec/</ref>
+<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
-* Truong Anh Tuan <ref>http://www.iwayvietnam.com/en/success-of-the-1st-vietnam-open-day.html</ref>
-* Nilesh Vaghela <ref>http://www.vglug.info/forums/vglug-discussion/fwd-fedora-13-release-party-photos</ref>
-* Rangeen Basu Roy <ref>https://fedoraproject.org/wiki/Release_Party_F13_Bangalore#Reports</ref>
-* David Ramsey <ref>http://diamondramsey.wordpress.com/2010/07/20/release-party-f13-tokyo-report/</ref>
-* José López <ref>http://www.taygon.com/?p=397</ref>
-* Edna Rheiner <ref>http://www.fedora.org.gt/linux-party-una-verdadera-fiesta-de-distros/</ref>
-* Neville A. Cross <ref>http://www.taygon.com/?p=409</ref>
-We want to make sure that you have no trouble in getting the money and that you get it fast - so please have a proper receipt, that you can send to me '''FAS:jsimon'''"
+---
+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.
+<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>
+---
+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>
+---
+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:
+<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
+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/>
-===Fedora Development News===
+====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!)
-====Red Hat Bugzilla 3.6 Upgrade Public Beta====
+I'd like to share a few reminders and announcements regarding the
-[[User:Jlaska|James Laska]]<ref>James Laska</ref> on Thu Jul 22 11:55:49 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000639.html</ref>,
+upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
-" I am sending this on behalf of Dave Lawrence and the bugzilla team at Red Hat.  Please forward this on to any appropriate lists that were missed.
-> Greetings,
+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.
-> The Red Hat Bugzilla team is happy to announce the first public beta release of the next version of Red Hat Bugzilla based on the upstream 3.6 code base.
+To place a subsidy request, please follow these steps:
->
-> Please test drive at:
+: Pre-register at
->
+<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
+put an X in the $$$ column
+: 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>
->      <ref>https://partner-bugzilla.redhat.com</ref>
+Additionally, a few notes regarding the hotel in Paris:
->
-> Over the years Red Hat has made substantial customizations to Bugzilla to fit into the Engineering tool chain. Over time the upstream has incorporated some of these customizations or solved them in different ways. Upgrading reduces our customization footprint (and thus maintenance) while bringing many bug fixes & enhancements.
+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 main area of focus for our public betas is stability. Functionality that currently works in our 3.4 code base should
+We currently have a rate of EUR81 per night at the ibis Paris La Vilette
-> continue to work as expected in the new 3.6 release. These include various ajax optimizations, needinfo actor support, frontpage.cgi, product
+Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October.
-> browser, several various UI enhancements, and of course the XMLRPC API.
+However, this rate will expire at the end of August, and any remaining
->
+rooms in our block will expire.
-> Please feel free to point your various scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly.
+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/>
-> There are numerous other changes behind the scenes that we haven't> listed. The goal is to make sure that functionality that people have come to expect in 3.4 is possible in the new system.
+====Fedora Infrastructure announces status.fedoraproject.org====
->
-> There are also numerous new features/fixes that are part of the upstream 3.6 release. For more detailed information on what has changed since the last release, check out the release notes page at <ref>https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html</ref> .
+* 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>
-> The database is a recent snapshot of the live database so should be useful for testing to make sure the information is displayed properly and changeable. Also with a full snapshot it is possible to test for any performance related issues. Email has been disabled so that unnecessary spam is not sent out. So feel free to make changes to bugs to verify proper working order.
+"I'm happy to announce the general availability of our
->
+status.fedoraproject.org site.
-> We are asking for everyone to get involved as much as possible with testing and feedback on the beta releases to help us make this the most robust and stable release possible.
+This site provides an easy way for Fedora contributors and users to
->
+check on the status of services provided by Fedora Infrastructure.
-> Please file any enhancement requests or bug reports in our current Bugzilla system at <ref>https://bugzilla.redhat.com</ref> . File them under the Bugzilla product and relevant component with the version 3.6. With everyone's help we can make this a great release.
->
-> Thanks The Red Hat Bugzilla Team"
+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 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'''.
+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/>
-====Fedora 14 branching and dist-git roll out====
+====Beats are open!====
-[[User:JesseKeating|Jesse Keating]]<ref>Jesse Keating</ref> on Sat Jul 24 06:54:53 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000640.html</ref>,"Hey all!  It's that time again, we're gearing up to branch for Fedora 14 this coming Tuesday!  There is a major twist this time around, we're going to attempt a roll out of dist-git!
-Dist-git is our replacement for the CVS system we are currently using. This is a pretty big deal, but we're going to try to make it as smooth as possible.  In the next few days I'll be finalizing our git server setup and polishing up the user interface tool you all will be using to interact with the source control and build system.
+* 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>
-The conversion will take a couple days, which means our normal short outage for branching will be a bit extended.  I wish there was another way, but converting over 9K cvs repos into git repos does take sometime.  I really feel that this move is worth the extended outage.
+"The Release Notes beats for Fedora 18 are now open:
+<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
-The tool you all will use to interact with git and the buildsystem is called "fedpkg".  It comes from the fedora-packager package.  There is a version of it available now in all active Fedora and EPEL releases, although it is built to work against our staging environment where we have been testing the setup for a while.  This setup is slightly different than the final version, but you can install it and poke around the help system to get a feel for what's going on.  Most of the make targets have made it over and are named the same; build, sources, srpm, etc...  Many of the targets can take arguments and options.  Where the make system used shell variables, fedpkg uses options and arguments.
+If you're looking for a way to dip your toes in the water, so to
-Each target takes a --help argument that will show any available options.  Fedpkg does not yet have a man page, that may be coming soon.
+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>
-We're also going to be working on wiki pages to document the new stuff and archive the old stuff.  We're going to need help on this too, so if you want to pitch in, by all means!
+As a reminder, the wiki drafts of beats are due on 12 September."
-As I mentioned above, this is an attempt.  We are trying this pretty early, which I wouldn't normally do.  However we have a good roll back plan.  We are going to keep the CVS server as is, although turned read-only during and after the dist-git rollout.  If something fails beyond reasonable repair with the dist-git attempt we will re-enable write access to the CVS server (after we branch it for Fedora 14). Otherwise we will keep it around, in some capacity, as a read-only reference point.
+<references/>
-I'm certain we will run into some bumps along the way, and some wrinkles to iron out.  I ask that you are patient with us as we work through these, and as we either get updates pushed out of fedpkg or make adjustments to the git repos on the git server.  This transition has been a long time coming, and I'm really happy to be the one to make it happen.  Keep in mind that this will be the first iteration of our transition, and it will operate mostly the same as dist-cvs did with a few improvements.  Later on we will start to explore more interesting advancements such as automatic patch management with exploded sources, linking to upstream source repositories, automatic %changelog generation from git changelogs, or things I haven't even thought about.  Most of all, we won't be using CVS any more and that feels really good to me.
+=== Fedora Development News ===
+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.
-If you're curious about how the new system will work or have concerns, or want to help, you can reply to this email thread or find me on IRC as "Oxf13" (that's an o, not a zero).  If you run across bugs in fedpkg, you can file them in the fedora-packager hosted trac space <ref>https://fedorahosted.org/fedora-packager/</ref> or just find me on IRC as well.
+'''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
-Thanks again for your patience, both in waiting so long for us to make this move, and for bearing with us during the transition."
+'''Unacceptable Types of Announcements'''
+* Periodic automated reports (violates the INFREQUENT rule)
+* Discussion
+* Anything else not mentioned above
 <references/>
-====Fedora 14 Feature Freeze is tomorrow (2010-07-27)====
+====New bodhi release in production====
-[[User:Poelstra|John Poelstra]]<ref>John Poelstra</ref> on Mon Jul 26 20:59:07 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000641.html</ref>,"A friendly reminder that tomorrow, Tuesday, July 27, 2010, is Feature Freeze for Fedora 14.
-Feature Freeze means that all accepted features for Fedora 14 must be *significantly* "feature complete", ready for testing, and have a current status.
+* 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>
-<ref>https://fedoraproject.org/wiki/Feature_Freeze_Policy</ref>
+"A new release of Bodhi has just been deployed to production.
-<ref>https://fedoraproject.org/wiki/Features/Policy/Milestones#Feature_Freeze</ref>
+<ref>https://admin.fedoraproject.org/updates</ref>
-If you have a feature that will not be feature complete by tomorrow that is okay.  Simply change the wiki page category to Category:FeatureReadyForWrangler (edit text at the very bottom of the page) and include the reason and your plans in the commit comment.  I'll see that your feature is targeted for Fedora 15 instead."
+Bugs and enhancement requests can be filed here:
+<ref>http://bodhi.fedorahosted.org</ref>
-<references/>
+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
-====f14 boost-1.44.0 upgrade: pushed====
+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'
-Benjamin Kosnik<ref>Benjamin Kosnik(bkoz at redhat.com)</ref> on Tue Jul 27 17:19:25 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000642.html</ref>,"The boost maintainers have updated the boost package to the current release (1.44.0) in rawhide for F14. More info here:
+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
-<ref>https://fedoraproject.org/wiki/Features/F14Boost144</ref>
+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.
-Rebuilds for devel packages that require boost are mandatory, as SONAME was bumped. Help from package maintainers with rebuilding packages with
+Till Maas (8):
-boost dependencies is appreciated."
+      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/>
-====Outage: Build System - 2010-07-28 07:15 UTC====
+====Build F-18 collection packages for all language translators====
-[[User:JesseKeating|Jesse Keating]]<ref>Jesse Keating</ref> on Wed Jul 28 07:05:27 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000643.html</ref>,"There will be an outage starting at 2010-07-28 07:15 UTC, which will last approximately 48 hours.
+* 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
-To convert UTC to your local time, take a look at <ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
+Please build and push your package with latest translation file (e.g.
-or run:
+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.
-date -d '2010-07-28 07:15 UTC'
+Thank you so much.
-=====Reason for outage=====
+noriko
-dist-git migration and Fedora 14 branching
+Fedora Localization Project"
-=====Affected Services=====
+<references/>
-Buildsystem - <ref>http://koji.fedoraproject.org/</ref>
-CVS / Source Control
-=====Unaffected Services=====
+====Fedora 18 Alpha to slip by another one week====
-All others
-=====Ticket Link=====
+* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
-N/A
+* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>
-=====Contact Information=====
+"Today at Go/No-Go meeting it was decided to slip Fedora 18
-Jesse Keating <jkeating at redhat.com> or Oxf13 on IRC
+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>.
-Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."
+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
+#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!"
 <references/>
-===Fedora User Announcements===
-The list<ref>http://lists.fedoraproject.org/pipermail/users/2010-July/thread.html</ref>,Fedora User Announcements, provides community assistance, encouragement, and advice for Fedora users.
-<references/>
+=== 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.
-===Fedora Events===
+====Upcoming Events (September 2012 - November 2012)====
-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!
+* '''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 (June 2010 - August 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#FY11_Q2_.28June_2010_-_August_2010.29</ref>
-* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2</ref>
-* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3</ref>
-* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4</ref>
 <references/>
@@ Line 183: / Line 372: @@
 * [[Event reports]] -- guidelines and suggestions.
 * [[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