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:Pcalarco|Pascal Calarco]]
+Contributing Writer: [[User:rashadul|Rashadul Islam]]
 <references/>
-===Fedora Announcement News===
+===Breaking News of the Week and Month===
-The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at<ref>https://admin.fedoraproject.org/mailman/listinfo/announce</ref>
-<references/>
+====[Guidelines Change] Changes to the Packaging Guidelines====
+* 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>
+"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>
+---
+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>
+---
+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>
+---
-==== Appointment to the Fedora Board ====
+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>
-[[User:Jsmith|Jared K. Smith]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-November/002889.html</ref>:
+---
-"The Fedora Board consists of five elected seats and four appointed seats.  As part of the normal Board succession process<ref>https://fedoraproject.org/wiki/Board/SuccessionPlanning</ref>, one Board appointment is made before elections and the other is made after the election cycle.
+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>
-I'm happy to announce that Toshio Kuratomi has accepted the responsibility of serving on the Fedora Board.  Toshio is a great contributor to open source in general, and has been actively collaborating with people throughout the Fedora Project for many years.  I have no doubt that he'll work tirelessly to increase the level of trust, transparency, communication, and innovation within the Fedora community.  I thank Toshio for his willingness to serve, and I hope the whole Fedora community will join me in welcoming him to the Board.
+---
-Toshio will fill seat A2 (see the Board History<ref>https://fedoraproject.org/wiki/Board/History
+A short section on the Group tag in Fedora packages has been added.
-</ref> for a list of the seats), which has been held by Colin Walters.  I'd also like to take
+All current versions of Fedora (and their respective RPM versions) treat
-this opportunity to publicly thank Colin for the work he's done on behalf of the Fedora Board.
+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>
-Elections for the two open elected seats on the Board (as well as FAmSCo and FESCo elections) will begin on November 20th at UTC 0001,
+---
-as shown on the Fedora wiki's Elections page<ref>https://fedoraproject.org/wiki/Elections
-</ref>.  All community members are encouraged to cast their vote until the elections close at
-the end of the day on November 28th.  After the end of elections, another appointment will be made for the remaining Board seat (seat A2).
--
+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>
-Jared Smith
+---
-Fedora Project Leader"
-<references/>
+These guidelines (and changes) were approved by the Fedora Packaging
+Committee (FPC).
-===Fedora Development News===
+'''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.'''
-The development list<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref> is intended to be a LOW TRAFFIC announce-only list for Fedora development.
-'''Acceptable Types of Announcements'''
+As a reminder: The Fedora Packaging Guidelines are living documents! If
-* Policy or process changes that affect developers.
+you find something missing, incorrect, or in need of revision, you can
-* Infrastructure changes that affect developers.
+suggest a draft change. The procedure for this is documented here:
-* Tools changes that affect developers.
+<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
-* Schedule changes
-* Freeze reminders
-'''Unacceptable Types of Announcements'''
+Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
-* Periodic automated reports (violates the INFREQUENT rule)
+<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
-* Discussion
+<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
-* Anything else not mentioned above
 <references/>
-==== Moving /var/run and /var/lock to tmpfs in Rawhide ====
+====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====
-Lennart Poettering announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-November/000726.html</ref>:
+* 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>
-"Heya!
+"Greetings! (...or perhaps I should say.... bonjour!)
-I hereby want to let everybody know that in the next days I will turn on /var/run and /var/lock on tmpfs on Rawhide/F15. This is in accordance
+I'd like to share a few reminders and announcements regarding the
-with the following accepted F15 feature<ref>https://fedoraproject.org/wiki/Features/var-run-tmpfs</ref>
+upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
-My current tests indicate that we will not run into too much trouble with this and most things should continue to work just fine. However, of
+If you are planning to attend FUDCon and need a travel subsidy to do so,
-course I run only a small subset of packages of the fedora archive on my machine. So here's what might happen and which might need fixing over
+the ticketing system is now open for those requests.  Requests will be
-the next weeks in various packages:
+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.
-* Not all packages might be able to create their directory in /var/run on start-up. Since SUSE and Ubuntu have already been shipping systems with tmpfs on /var/run and /var/lock for quite a while I expect the number of packages that are incapable of doing this to be very small. If your software nonetheless fails with this issue, then there are two options to fix this: a) patch the program in question, so that it is able to recreate the directories in /var/run, or b) ship a simple drop-in file for /etc/tmpfiles.d/ which  recreates these directories on boot. (see below)
+To place a subsidy request, please follow these steps:
-* There might be permission problems, since the rpms might have set different perms on the subdirs of /var/run than the software itself might apply when starting up. In this case, a drop-in file in /etc/tmpfiles.d/ might  help. (see below)
+: 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>
-* The SELinux policy might trigger AVCs and disallow creation of the dirs in question. In this case Dan will be of help of course, so make sure to file a bug. And I guess I don't need to mention this but temporarily falling back to permissive mode is a short-term workaround for this.
+Additionally, a few notes regarding the hotel in Paris:
-* In some cases daemons might want to create more than one file/dir below /var/run which are supposed to be labelled differently. In this case the daemon can either be modified to fix its labels up itself, or a drop-in file in /etc/tmpfiles.d/ might help (see below).
+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. :)
-* Many .spec files currently own subdirs of /var/run. These need to be updated to %ghost those dirs only, so that the automatic removal of these files/dirs on boot doesnt cause rpm to complain. The list of packages which own such files/subdir you find on the aforementioned feature page. I will mass-file bugs against these packages later tonight, requesting the %ghosting of these entries. For more information on the %ghost directive in .spec files see this page<ref>http://www.rpm.org/max-rpm-snapshot/s1-rpm-inside-files-list-directives.html#S3-RPM-INSIDE-FLIST-GHOST-DIRECTIVE</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.
-Action items:
+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/>
-a) Lennart will mass-file bugs regarding %ghost usage tonight
+====Fedora Infrastructure announces status.fedoraproject.org====
-b) Lennart will switch on /var/run and /var/lock on tmpfs either tomorrow or the day after tomorrow
+* 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>
-c) YOU need to edit your .spec file and place a %ghost where appropriate.
+"I'm happy to announce the general availability of our
+status.fedoraproject.org site.
-d) YOU need to test if you package still works, and if necessary file AVC bugs, add an /etc/tmpfiles.d drop-in file to your program, or patch it so that it is able to recreate these directories beneath /var/run on its own.
+This site provides an easy way for Fedora contributors and users to
+check on the status of services provided by Fedora Infrastructure.
-On /etc/tmpfiles.d:
+The site auto reloads every minute, and also provides a rss feed at
+<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.
-This is a new feature of systemd, but which is apparently very much liked by people outside of systemd, so this might actually find adoption
+If you run into a problem or issue that is not reflected at
-even on systems which will not adopt systemd any time soon, since it actually is not specific at all to systemd. By dropping a simple
+status.fedoraproject.org, please do report it to us in #fedora-admin on
-configuration file in /etc/tmpfiles.d you can ensure that volatile files and directories are: a) created, deleted or emptied at boot b) their
+irc.freenode.net or via ticket at
-permissions/ownership fixed c) its directory contents cleaned up in regular intervals (a la tmpwatch) and d) it is properly re-labeled at
+<ref>https://fedorahosted.org/fedora-infrastructure/newticket</ref>
-boot.
+We update the site status information manually so we need to be aware
+of the issue in order to keep the site accurate.
-As an example, here's how such a file might look like for the screen package (name it /etc/tmpfiles.d/screen.conf):
+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'''.
-<code>
+This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
-d /var/run/screens 1777 root root 10d
+issues with outages in our infrastructure affecting status reporting. "
-d /var/run/uscreens 0755 root root 10d12h
+<references/>
-</code>
-This encodes that two directories are created under the listed names, with
+====Beats are open!====
-automatic clean up after 10 days resp. 10 days and 12h.
-For more details consult the man page<ref>http://0pointer.de/public/systemd-man/tmpfiles.d.html</ref>
+* 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>
-Thank you for your attention!
+"The Release Notes beats for Fedora 18 are now open:
+<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
-Lennart Poettering - Red Hat, Inc."
+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>
+As a reminder, the wiki drafts of beats are due on 12 September."
 <references/>
-==== Fedora Board, FESCo & FAmSCo Elections - Voting Information ====
+=== 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.
-[[User:rbergero | Robyn Bergeron]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-November/000725.html</ref>
+'''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
-"Greetings,
+'''Unacceptable Types of Announcements'''
+* Periodic automated reports (violates the INFREQUENT rule)
+* Discussion
+* Anything else not mentioned above
-The elections for the Fedora Board, Fedora Engineering Steering Committee (FESCo), and the Fedora Ambassadors Steering Committee
+<references/>
-(FAmSCo) began at 0000 UTC on 20th November 2010, and are scheduled to run until 23:59 UTC on 28th November 2010.  (Please refer to a UTC
-time zone converter<ref>http://www.timeanddate.com/worldclock/converter.html</ref> if you are unsure of your time zone's relation to UTC.)
-All groups have chosen to use the Range Voting method<ref>http://en.wikipedia.org/wiki/Range_voting</ref>.
+====New bodhi release in production====
-Ballots may be cast on the Fedora Elections System<ref>https://admin.fedoraproject.org/voting</ref>.  If this is the first time
+* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
-you've used the voting system, please refer to the Fedora Elections Guide<ref>http://pfrields.fedorapeople.org/documents/elections-guide</ref>.
+* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>
-To read more about the candidates, please refer to each group's
+"A new release of Bodhi has just been deployed to production.
-nomination pages:
+<ref>https://admin.fedoraproject.org/updates</ref>
-* FAmSCo<ref>http://fedoraproject.org/wiki/FAmSCo_election_2010_nominations</ref>
+Bugs and enhancement requests can be filed here:
-* Fedora Project Board<ref>http://fedoraproject.org/wiki/Board/Elections/Nominations</ref>
+<ref>http://bodhi.fedorahosted.org</ref>
-* FESCo<ref>http://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations</ref>
-There is more general information about the election, as well as finding links for reading candidate answers to questionnaires and IRC town
+Major changes in bodhi 0.9.2
-hall transcripts<ref>http://fedoraproject.org/wiki/Elections</ref>.
+---------------------------------
-Please remember to cast your vote!
+* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
-Thanks,
+* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
-Robyn"
+* The submitter of an update can no longer effect the karma (Till Maas)
-<references/>
+* 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.
-==== Fedora Board Election IRC Town Hall transcript ====
+* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
-[[User:Toshio|Toshio Kuratomi]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-November/000724.html</ref>:
-"The Fedora Board Town Hall happened today at 15:00 UTC.  The transcript of the townhall is at the following URL:
+Full list of changes since 0.8.7
+--------------------------------
-Log<ref>http://meetbot.fedoraproject.org/fedora-townhall/2010-11-19/board-townhall.2010-11-19-14.59.log.html</ref>
+Kalpa Welivitigoda (1):
+      fixed input box alignment issue in login box #579
-Minutes<ref>http://meetbot.fedoraproject.org/fedora-townhall/2010-11-19/board-townhall.2010-11-19-14.59.html</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'
-Minutes (text)<ref>http://meetbot.fedoraproject.org/fedora-townhall/2010-11-19/board-townhall.2010-11-19-14.59.txt</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
-Thanks to the candidates for answering questions and thanks to all the audience members for the insightful questions.
+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.
--Toshio"
+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/>
-==== FESCo Election IRC Town Hall Transcript ====
+====Build F-18 collection packages for all language translators====
+* 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.
-[[User:kyle | Kyle McMartin]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-November/000723.html</ref>:
+Thank you so much.
-"The IRC logs of the discussion are available<ref>http://meetbot.fedoraproject.org/fedora-townhall/2010-11-18/fesco-townhall.2010-11-18-15.02.log.html</ref>
+noriko
+Fedora Localization Project"
-I'll be making an edited transcript available (I'll link it from the wiki<ref>https://fedoraproject.org/wiki/Elections</ref>) which should be a little easier to read, in the next day or so.
+<references/>
-Thanks to our candidates, and to all who attended and submitted questions.
+====Fedora 18 Alpha to slip by another one week====
-regards,
+* 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>
-Kyle M."
+"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>.
+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 Events===
-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 (Sept 2010 - November 2010)====
+=== Fedora Events ===
-* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sept_2010_-_November_2010.29</ref>
-* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28September_2010_-_November_2010.29</ref>
+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.
-* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sep._2010_-_Nov._2010.29</ref>
-* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sept_2010_-_November_2010.29_2</ref>
+====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>
+Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>
 <references/>
 ====Past Events====
 Archive of Past Fedora Events<ref>http://fedoraproject.org/wiki/FedoraEvents/PastEvents</ref>
@@ Line 204: / 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