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://www.redhat.com/archives/fedora-announce-list/</ref>, development announcements<ref>http://www.redhat.com/archives/fedora-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 ANNOUNCE LIST===
+===Breaking News of the Week and Month===
-====CC license changeover complete====
-Ian Weller  announced about the CC license changeover complete <ref>http://www.redhat.com/archives/fedora-announce-list/2009-November/msg00001.html</ref>. He mentioned, “The Docs team has finished converting all current documentation and project content from the OPL to a CC BY-SA 3.0 Unported license.
-Additional information can be found at <ref>https://fedoraproject.org/wiki/Relicensing_OPL_to_CC_BY_SA</ref></ref>http://www.redhat.com/archives/fedora-announce-list/2009-October/msg00001.html</ref>
+====[Guidelines Change] Changes to the Packaging Guidelines====
-Thanks again to Tom "spot" Callaway, Richard Fontana of Red Hat Legal
+* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
-and all the Fedora contributors who helped with the conversion. Here's
+* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
-to freer documentation for Fedora 12!”
+"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>
+---
+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/>
-====Reminder: Fedora Board IRC meeting 1700 UTC 2009-11-05====
+====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====
-Paul W. Frields, the Fedora Project Leader, announced <ref> http://www.redhat.com/archives/fedora-announce-list/2009-October/msg00009.html</ref> as reminder about the Fedora Board IRC Meeting. He said, “The Board is holding its monthly public meeting on Thursday, November 5, 2009, at 1700 UTC on IRC Freenode.  For this meeting, the public is invited to do the following:
+* 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!)
+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:
-Join #fedora-board-meeting to see the Board's conversation.
+: Pre-register at
-Join #fedora-board-questions to discuss topics and post questions. This channel is read/write for everyone.”
+<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>
-Note that daylight savings time ends in the USA on November 1, and on November 5, 1700 UTC == 12:00pm US Eastern == 9:00am US Pacific.
+Additionally, a few notes regarding the hotel in Paris:
-<references/>
+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. :)
-====Announcing Fedora-Medical SIG.====
+We currently have a rate of EUR81 per night at the ibis Paris La Vilette
-Susmit shannigrahi had announced Fedora-Medical SIG<ref>http://www.redhat.com/archives/fedora-announce-list/2009-October/msg00008.html</ref>. On his announcement, he mentioned how the idea came from (Fedora India mailing list <ref> https://www.redhat.com/archives/fedora-india/2009-July/msg00060.html</ref>), how to make the Fedora Medical SIG successful, the initial SIG page <ref> http://fedoraproject.org/wiki/SIGs/FedoraMedical</ref> and the goal of the SIG. He said, “Simply put, the goal of the SIG is going to be:
+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.
-. Working on identifying the various workflows / needs of the medical
+For instructions on booking your hotel, please read the Lodging/Hotel
-or healthcare community in terms of software.
+section of the FUDCon: Paris wiki:
-. Bring together and package the software those fitting in the workflow.
+<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
-. Composing a spin to get a out-of-the-box solution.
-. At a later stage, developing any crucial app that may be lacking.
-”
 <references/>
-====Fedora 12 now in RC freeze====
+====Fedora Infrastructure announces status.fedoraproject.org====
-Bill Nottingham announced on behalf of the Fedora Release Engineering, “Fedora 12 now in RC freeze” <ref>http://www.redhat.com/archives/fedora-devel-announce/2009-November/msg00001.html</ref>. He said, “We are reaching a very deep freeze now as we try and get a final release candidate for Fedora 12. Bodhi is now open for submitting
-F-12 updates, and we hope to have update repositories for testing later this weekend.
+* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
-If you have critical blocking issues, you can continue to file tag requests with 'make tag-request', and they will be considered.
+* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>
-For the majority of updates, though, please use bodhi.”
+"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
+<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.
-</references>
+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'''.
-===FEDORA DEVELOPMENT ANNOUNCEMENTS===
+This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
-====Outage Notification - 2009-11-05 13:00 UTC====
+issues with outages in our infrastructure affecting status reporting. "
-“There will be an outage starting at 2009-11-05 13:00 UTC, which will last
-approximately 1 hour.”, announced<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-November/msg00000.html</ref> Mike McGrath. He widely mentioned, “
-To convert UTC to your local time, take a look at
-<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
-or run:
-date -d '2009-11-05 13:00 UTC'
+<references/>
-Affected Services:
+====Beats are open!====
-Buildsystem
-DNS
-Torrent
-Translation Services
-Websites
-Unaffected Services:
+* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
-CVS / Source Control
+* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>
-Database
-Fedora Hosted
-Fedora People
-Fedora Talk
-Mail
-Mirror System
-Ticket Link:<ref>https://fedorahosted.org/fedora-infrastructure/ticket/1785</ref>
+"The Release Notes beats for Fedora 18 are now open:
+<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
-Reason for Outage:
+If you're looking for a way to dip your toes in the water, so to
-IBM wants us reseat the DIMMs and get FRU information off of them.  Don is
+speak, writing a beat is a great way to get started. If you're a
-going to do this work for us (thanks ibiblio).  Seth is going to do a
+regular, don't forget about the checkBeat program:
-graceful shutoff.
+<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>
-Contact Information:
+As a reminder, the wiki drafts of beats are due on 12 September."
-Please join #fedora-admin in irc.freenode.net or respond to this email to
-trackthe status of this outage.”
 <references/>
-====Addition to the Policy for non responsive maintainers====
+=== Fedora Development News ===
-Kevin announced, “FESCo has made an additional 'fast track' process for non responsive maintainers available for some rare cases.”<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00010.html</ref>
+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.
+'''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
-<ref>https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers#Fast_Track_procedure</ref>
+'''Unacceptable Types of Announcements'''
-For more details. <ref>https://fedorahosted.org/fesco/ticket/251</ref>
+* Periodic automated reports (violates the INFREQUENT rule)
-As well as: <ref>http://meetbot.fedoraproject.org/fedora-meeting/2009-09-18/fedora-meeting.2009-09-18-16.59.log.html#l-31</ref>
+* Discussion
+* Anything else not mentioned above
 <references/>
-====Upcoming Bugzilla Changes====
+====New bodhi release in production====
-Edward Kirk on behalf of the Fedora Bug Triage Team mentioned the upcoming Bugzilla Changes <ref>http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00009.html</ref>.
+* 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)
+* 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.
-He said, “This e-mail is designed to let you know about two things happening around November 17, 2009 (Fedora 12 release day) and what you need to do, if anything.
+* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
-(1) We will be automatically changing the version all rawhide bugs to Fedora 12.This will result in regular bugs reported against rawhide during the Fedora 12 development cycle being changed to version '12' instead of their current assignment, 'rawhide'.  This is done in order to more accurately tell where in the lineage of releases the bug was last reported because over time 'rawhide'becomes ambiguous.
-Note that this procedure does not apply to bugs that are against component 'Package Review' or bugs that have the 'FutureFeature' or 'Tracking' keywords set.
+Full list of changes since 0.8.7
-They will stay open as rawhide bugs indefinitely.
+--------------------------------
-If you do not want your bugs changed to version '12', add the FutureFeature keyword.
+Kalpa Welivitigoda (1):
-If you need help changing a large amount of bugs manually, we'd be glad to help. Stop by #fedora-bugzappers on irc.freenode.net and we'll help you.
+      fixed input box alignment issue in login box #579
-(2) All bugs for upcoming EOL releases (at this point, Fedora 10) will get a comment on release day, explaining that one month of maintenance remains. These bugs must move to a later version if still applicable or they will be automatically closed in one month with a resolution of WONTFIX.”
+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'
-More about these processes is here:<ref>https://fedoraproject.org/wiki/BugZappers/HouseKeeping</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
+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"
 <references/>
-====Request your FUDCon funding now: cutoff Thursday 19:30 UTC====
+====Build F-18 collection packages for all language translators====
-Mel Chua announced, <ref>http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00008.html</ref> “Request your FUDCon funding now: cutoff Thursday 19:30 UTC”.
+* 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.
+Thank you so much.
-Here is the brief, “We’d like to wrap up budgeting for FUDCon Toronto 2009 as the happy date draws nearer. And we need your help. Ask us for money!
+noriko
-Before Thursday October 29 at 19:30 UTC, that is. More details here (the blog post below will lead you to instructions on the wiki outlining how to request funding):<ref>http://blog.melchua.com/2009/10/25/request-your-fudcon-funding-now-cutoff-thursday-1930-utc/<ref>
+Fedora Localization Project"
-I look forward to a flooded inbox on Thursday afternoon. ;)”
 <references/>
-====Notice: Fedora 12 Tagging Status Update====
+====Fedora 18 Alpha to slip by another one week====
-Warren Togami announced <ref>http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00007.html</ref> that Fedora Release Engineering had decided to deal with the 250+ backlog of Bodhi update requests by tagging them all into f12-final. Bodhi is now disabled for Fedora 12 updates. He said, “
-Questions
+* 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>
-) Why tag all Update requests into f12-final?
-At this point of the schedule we realized that there were updates sitting in the queue from since October. They were sitting there. Not getting pushed to any repository. Rawhide gives these packages several more weeks of testing exposure. This was decided to be better than a flood of day zero updates that are poorly tested.
-) When will we be able to submit Updates again?
+"Today at Go/No-Go meeting it was decided to slip Fedora 18
-Rel-eng will decide when to begin accepting Updates for Fedora 12 again during Monday's rel-eng meeting. Meanwhile please use the rel-eng ticketing system to request tagging into f12-final.
+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>.
-) How do I file a tag request to include my package into Fedora 12?
+As a result, ALL MAJOR MILESTONES, and their dependent tasks,
-<ref>https://fedorahosted.org/rel-eng/</ref>
+will be pushed out by one week.
-Please file tag request tickets here if you want your package build to be included in Fedora 12. Please include details like:
-* Full Name-Version-Release of your package(s)
-* What changed?
-* How risky is this change?
-* How important is this change?
-* How well tested is this package build?
-* Is this package in the critical-path list?
-) Which packages are critical-path?
+The next Go/No-Go meeting is on Thursday Sep 06, same place
-<ref>https://fedorahosted.org/pipermail/autoqa-results/2009-October/001714.html</ref>
+but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
-Unfortunately we do not yet have a permanent URL with the critical-path list. This page contains an auto-generated list of critical-path packages as of today.
+#fedora-meeting).
-If your package is not critical-path and not a risk to others to update, then it is highly likely proper to tag at this point of the schedule.
-) How many untagged packages are there?
+If you have an accepted blocker bug, please try to fix it
-koji list-tagged --latest dist-f12-updates-candidate
+as soon as possible to help us with Fedora 18 Alpha release!"
-This command lists all packages that are not tagged for f12-final. In some cases these are false positives because a newer package is instead tagged into f12-final. After you have tested your package and verified it doesn't make things worse, please file rel-eng tickets to have it included.
-Please direct questions to fedora-devel-list.
-“
 <references/>
-====Reminder: Tagging Policy for Fedora 12====
-Warren announced the Tagging Policy for Fedora 12<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00006.html</ref>. He also detailed about the following on the announcement:
-What Qualifies for Tagging? Many Builds Not Tagged, but Probably Should Be
-How to Request Tagging <ref>https://fedorahosted.org/rel-eng</ref
-Upcoming Deadlines <ref>https://fedoraproject.org/wiki/Schedule</ref>
-<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 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====
+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_Q3_.28September_2009_-_November_2009.29</ref>
-* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_2</ref>
-* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_3</ref>
-* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_4</ref>
 <references/>
 ====Past Events====
-Archive of Past Fedora Events<ref>http://fedoraproject.org/wiki/Events#Past_Events</ref>
+Archive of Past Fedora Events<ref>http://fedoraproject.org/wiki/FedoraEvents/PastEvents</ref>
 <references/>
+====Additional information====
+* [[Reimbursements]] -- reimbursement guidelines.
+* [[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.
+* [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
+* [[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