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 4: / Line 4: @@
 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>.
-Contributing Writer: [[User:Pcalarco|Pascal Calarco]]
+Contributing Writer: [[User:rashadul|Rashadul Islam]]
 <references/>
-==== Upcoming elections for FAmSCo, FESCo, and the Fedora Board ====
+===Breaking News of the Week and Month===
-Fedora Project Leader, [[User:User:Jsmith|Jared K. Smith]]  announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-October/003007.html</ref>:
+====[Guidelines Change] Changes to the Packaging Guidelines====
-"One of the things I like most about Fedora is the orderly way in which
+* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
-people are able to move in and out of leadership positions within our
+* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
-community.  Each development cycle, we have a set of elections for the
-steering committees and for the Fedora Board.  The next election cycle
-is nearly upon us, so I'd like to take this opportunity to share the
-details of the upcoming elections with you.
-As quick reminder, the nomination period for this election cycle will
+"A new section has been added to the SysV Initscripts section, discussing
-open on 25 October 2011, and will close promptly on 5 November 2011 at
+the proper use of subsys locking. Even though Fedora packages should no
-:59:59 UTC.  The full elections schedule, along with more details
+longer be using SysV Initscripts as a primary service mechanism, Red Hat
-about the elections, can be found at
+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>
-* https://fedoraproject.org/wiki/Elections
+---
-I strongly encourage you to consider running for an open position in
+The review guidelines now reflect the use of sha256sum (instead of
-one of the elections.  This is one way to serve your fellow community
+md5sum) to confirm upstream source integrity.
-members and help move Fedora forward at the same time.  Additionally,
+<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
-I'm looking for a few volunteers to help with the coordination of the
-candidate questionnaires and town hall meetings.  If you're willing to
-help, please let me know.
-===== Fedora Board =====
+---
-This election cycle will fill two elected seats for the Board (seats
-E1 and E2). Prior to the election I will also announce the first of
-two appointed seat in this cycle (seats A1 and A2), with the second
-appointment announcement to follow after the election. For more
-information on nominations, and the process refer to:
-* https://fedoraproject.org/wiki/Board_nominations
+The PHP Packaging guidelines have been updated to include guidance about
-* https://fedoraproject.org/wiki/Board/Elections
+when it is appropriate to have an explicit Requires on httpd & mod_php,
-* https://fedoraproject.org/wiki/Board/History
+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>
-===== FESCo =====
+---
-This cycle will also see four candidates elected to open seats in the
-Fedora Engineering Steering Committee. For information on the
-nominations and elections:
-* https://fedoraproject.org/wiki/FESCo_election_policy
+A new section on Macros has been added to the Packaging Guidelines,
-* https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
+covering Packaging of Additional RPM Macros.
+<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>
-===== FAmSCo =====
+---
-This election cycle will also see candidates elected to fill all all
-seven seats on the Fedora Ambassadors Steering Committee.  For more
-information, refer to:
-* https://fedoraproject.org/wiki/FAmSCo_election_rules
+A new section on the Documentation= field in systemd unit files (F17+)
-* https://fedoraproject.org/wiki/FAmSCo_elections
+has been added.
-* https://fedoraproject.org/wiki/FAmSCo_election_2011_nominations
+<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
-== Candidate Questionnaire and Town Hall meetings ==
+---
-Additionally, the nomination period also serves as the time for the
-community to present questions to be posed to candidates. If you wish
-to ask questions to be answered by candidates, you can add them<ref>https://fedoraproject.org/wiki/F17_elections_questionnaire</ref>. Candidates
-will have the questions posed to them and responses made available to
-the community before the voting period begins.
-As we get closer to the elections, we will try to schedule several
+A short section on the Group tag in Fedora packages has been added.
-Town Hall Meetings in IRC to help you get to know the candidates
+All current versions of Fedora (and their respective RPM versions) treat
-better, and to ask them additional questions.
+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>
-As always, I'm thankful to those who have given their time, talents,
+---
-and abilities to serve the Fedora community.
---
+The RHEL conditionalization has been removed from the Python3 example
-Jared Smith
+spec file, as it is no longer valid.
-Fedora Project Leader"
+<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
-<references/>
+---
-==== Subsidy requests for FUDCon Blacksburg are now OOOOOPEN! ====
-[[User:Rbergero|Robyn Bergeron]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-October/003006.html</ref>
-"Greetings, FUDCon friends, near and far:
-As you are probably aware, the 2012 North American FUDCon will be held
-in Blacksburg, Virginia, on the campus of Virginia Tech.  If you are
-planning on attending, it's never too early to pre-register, and to
-start thinking about your travel plans. FUDCon Blacksburg will take
-place January 13-15, 2012.
-https://fedoraproject.org/wiki/FUDCon:Blacksburg_2012
-I'm happy to announce that we are officially accepting subsidy requests
-for travel to Blacksburg. If you are requesting a subsidy, we just have
-a few steps that we ask you to follow:
-: Register<ref>https://fedoraproject.org/wiki/FUDCon:Blacksburg_2012#Pre-registration</ref> on the FUDCon: Blacksburg wiki page in the pre-registration area.
-: Put an X in the $$$ column.
-: Create a funding request ticket in the FUDCon trac<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>
-General information about being sponsored can be found at:
-* http://fedoraproject.org/wiki/Sponsoring_event_attendees
-Requests are processed in a first-come, first-served manner, though
-generally prioritization is giving to local travel over international
-travel first.  Requests will be reviewed by fellow Fedora community
-members at FUDCon subsidy request meetings over the next few weeks.
-The first subsidy meeting will take place on Wednesday, November 9th.
-The time and IRC channel will be announced as we approach that day.
-As always, participation both in planning as well as subsidy granting is
+These guidelines (and changes) were approved by the Fedora Packaging
-ALWAYS welcome.  Please join us on the fudcon-planning mailing list for
+Committee (FPC).
-information about meetings, as well as for general FUDCon updates, and
-see the "meetings" section of your FUDCon's wiki page for meeting
-information.
-Mailing list:
+'''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.'''
-* https://admin.fedoraproject.org/mailman/listinfo/fudcon-planning
+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>"
-FUDCon Blacksburg Meetings:
+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>
-* https://fedoraproject.org/wiki/FUDCon:Blacksburg_2012#Meetings"
+<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
 <references/>
-==== Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30 ====
+====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====
-Kevin Fenzi announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-October/003005.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>
-"All existing users of the Fedora Account System (FAS)<ref>https://admin.fedoraproject.org/accounts</ref> are required to change their password and upload a NEW ssh public key before 2011-11-30.  Failure to do so may result in your account being marked inactive.  Passwords changed and NEW ssh public keys uploaded after 2011-10-10 will meet this requirement.
+"Greetings! (...or perhaps I should say.... bonjour!)
-====== Backgound and reasoning: ======
+I'd like to share a few reminders and announcements regarding the
+upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
-This change event has NOT been triggered by any specific compromise or vulnerability in Fedora Infrastructure. Rather, we believe, due to the large number of high profile sites with security breaches in recent months, that this is a great time for all Fedora contributors and users to review their security settings and move to "best practices" on their
+If you are planning to attend FUDCon and need a travel subsidy to do so,
-machines. Additionally, we are putting in place new rules for passwords to make them harder to guess.
+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.
-====== New Password Rules: ======
+To place a subsidy request, please follow these steps:
-* Nine or more characters with lower and upper case letters, digits and
+: Pre-register at
-  punctuation marks.
+<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
-* Ten or more characters with lower and upper case letters and digits.
+put an X in the $$$ column
-* Twelve or more characters with lower case letters and digits
+: Read about the funding request process and place a funding request
-* Twenty or more characters with all lower case letters.
+ticket in the FUDCon-planning ticket tracker here:
-* No maximum length.
+<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>
-====== Some Do's and Don'ts: ======
+Additionally, a few notes regarding the hotel in Paris:
-* NEVER store your ssh private key on a shared or public system.
+There are other events in Paris during this time period; most notably,
-* ALWAYS use a strong passphrase on your ssh key.
+our first day of FUDCon will be taking place at the Open World Forum
-* If you must store passwords, use an application specifically for this
+conference, on the day in which the public is encouraged to participate
-  purpose like revelation, gnome-keyring, seahorse, or keepassx.
+in and learn about open source projects.  OWF had nearly 2000 attendees
-* Regularly apply your operating system's security related updates.
+last year.  Accordingly, rooms might be in short supply as we approach
-* Only use ssh agent forwarding when needed ( .ssh/config:
+FUDCon; please, book your hotel as soon as possible, not only for
-  "ForwardAgent no")
+affordability purposes, but also so that you have a bed to sleep in. :)
-* DO verify ssh host keys via dnssec protected dns. ( .ssh/config:
-  "VerifyHostKeyDNS yes")
-* DO consider a seperate ssh key for Fedora Infrastructure.
-* Work with and use security features like SELinux and iptables.
-* Review the Community Standard Infrastructure security document (link
-  below)
-====== Q&A: ======
+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.
-Q: My password and ssh private key are fine and secure!
+However, this rate will expire at the end of August, and any remaining
-Can't I just skip this change?
+rooms in our block will expire.
-No.  We believe the new guidelines above provide an added measure of
-security compared to the previous requirements.  We want all users of
-our infrastructure to follow the new guidelines to improve one aspect
-of security across the systems they share.  Awareness is also an
-aspect of good security.  By requiring these changes, we also hope to
-maintain and improve awareness of the process for changing passwords
-and keys.
-Q: Can I just change my password and re-upload my same ssh public key?
-Or upload a bogus ssh public key and then re-upload my old one?
-A: No. We've installed safeguards to ensure that your new ssh public
-key is different from your old one. Additionally, some of our
-contributors may have had accounts on compromised high profile Linux
-sites recently, and we want to make sure no ssh private keys or
-passwords used in Fedora Infrastructure were obtained via those
-incidents.
-Q: This is a hassle. How often is this going to happen?
-A: The last mass password change in Fedora was more than 3 years ago.
-Absent a triggering event, these mass changes will be infrequent.
-Q: The new password length requirements/rules are too strict.
-How will I remember passwords that are that long?
-A: You can employ a password storage application (see above), or
-use a method like diceware (see below), or construct a memorable
-sentence or phrase.
-Q: How do I generate a new ssh key? How do I use it for just Fedora
-hosts?
-A: See http://fedoraproject.org/wiki/Cryptography and use a
-~/.ssh/config file to match fedoraproject.org hosts for that key.
-Q: I never uploaded a ssh key to the Fedora Account System, nor am I
-in a group that needs one, do I still have to upload a new one?
-A: No. If you don't have a ssh public key uploaded or desire to do so,
-you can just change your password.
-More reading:
-* http://infrastructure.fedoraproject.org/csi/security-policy/en-US/html-single/
-* https://fedoraproject.org/wiki/Infrastructure_mass_password_update
-* http://xkcd.com/936/
-* http://www.iusmentis.com/security/passphrasefaq/
-* http://world.std.com/~reinhold/diceware.html
-* http://fedoraproject.org/wiki/Cryptography
-<references/>
-===== Outage: value server migration - 2011-10-13 20:30UTC =====
-Kevin Fenzi announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-October/003004.html</ref>:
-" There will be an outage starting at 2011-10-13 20:30 UTC, which will
- last approximately 1 hour.
- To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
- or run:
-<code>
- date -d '2011-10-13 20:30 UTC'
-</code>
-====== Reason for outage: ======
- We are migrating smolt and zodbot over to new RHEL6 server instances.
-====== Affected Services: ======
-* Smolt - http://smolts.org/
-* zodbot irc bot.
-====== Unaffected Services: ======
-* BFO - http://boot.fedoraproject.org/
-* Bodhi - https://admin.fedoraproject.org/updates/
-* Buildsystem - http://koji.fedoraproject.org/
-* GIT / Source Control
-* DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
-* Docs - http://docs.fedoraproject.org/
-* Email system
-* Fedora Account System - https://admin.fedoraproject.org/accounts/
-* Fedora Community - https://admin.fedoraproject.org/community/
-* Fedora Hosted - https://fedorahosted.org/
-* Fedora Insight - https://insight.fedoraproject.org/
-* Fedora People - http://fedorapeople.org/
-* Fedora Talk - http://talk.fedoraproject.org/
-* Main Website - http://fedoraproject.org/
-* Mirror List - https://mirrors.fedoraproject.org/
-* Mirror Manager - https://admin.fedoraproject.org/mirrormanager/
-* Package Database - https://admin.fedoraproject.org/pkgdb/
-* Spins - http://spins.fedoraproject.org/
-* Start - http://start.fedoraproject.org/
-* Torrent - http://torrent.fedoraproject.org/
-* Translation Services - http://translate.fedoraproject.org/
-* Wiki - http://fedoraproject.org/wiki/
-====== Ticket Link: ======
- https://fedorahosted.org/fedora-infrastructure/ticket/2971
-====== Contact Information: ======
-Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above."
+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/>
-===== Results of the voting for the Fedora 17 release name =====
+====Fedora Infrastructure announces status.fedoraproject.org====
-Fedora Project Leader, [[User:Jsmith|Jared K. Smith]] announced:
+* 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 voting has concluded for the Fedora 17 release name, and the
+"I'm happy to announce the general availability of our
-results are in!  Thank you to the Fedora community members who made
+status.fedoraproject.org site.
-name suggestions and participated in the voting.
-The Fedora 17 release name is: Beefy Miracle
+This site provides an easy way for Fedora contributors and users to
+check on the status of services provided by Fedora Infrastructure.
-Voting period:  Tuesday 2011-11-04 00:00:00 UTC to Monday 2011-10-10
+The site auto reloads every minute, and also provides a rss feed at
-:59:59 UTC
+<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.
-Number of valid ballots cast:  292
+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.
-Using the range voting method, each release name candidate could
+As with everything in Fedora Infrastructure, this application is open
-attain a maximum of (292*8) = 2336 votes.
+source. Source is available from:
+<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
+and is released under a '''GPLv2+ license'''.
-====== Results: ======
+This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
-<code>
+issues with outages in our infrastructure affecting status reporting. "
-Votes :: Name
--------------------------------
-:: Beefy Miracle
-:: Liege
-:: Never
-:: Gernsback
-:: Rocky Ripple
-:: Alpharabius
-:: Panguipulli
-:: Tubeteika
-</code>
---
-Jared Smith
-Fedora Project Leader"
 <references/>
-===== Announcing the release of Fedora 16 Beta!! =====
+====Beats are open!====
-[[User:ausil|Dennis Gilmore]] announced<ref></ref>:
-"Mark your calendars, and get ready to go exploring: The release of
-Fedora 16, codenamed "Verne," is scheduled for release in early
-November. Fedora is the leading edge, free and open source operating
-system that continues to bring everyone fresh, innovative features
-with each release, delighting users worldwide every six months.
-We are proud to announce the availability of the Beta release of Fedora 16.
-Come see why we love Fedora so much. We are betting you will, too.
-Download it now:
-http://fedoraproject.org/get-prerelease?anF16b
-====== What is the Beta Release? ======
-The Beta release is the last important milestone of Fedora 16. Only
-critical bug fixes will be pushed as updates leading to the general
-release of Fedora 16 in early November. We invite you to join us in
-making Fedora 16 a solid release by downloading, testing, and
-providing your valuable feedback.
-Of course, this is a beta release, meaning that some problems may
-still be lurking. A list of the problems we already know about is
-found at the Common F16 bugs page, seen here:
-http://fedoraproject.org/wiki/Common_F16_bugs
-====== Features ======
-This release of Fedora includes a variety of features both over and
-under the hood that show off the power and flexibility of the
-advancing state of free software. Examples include:
-* System Boot. Fedora 16 introduces GRUB2, the long-awaited
-next-generation boot-loader for Linux. GRUB2 automatically recognizes
-other operating systems, supports LVM2 and LUKS partitions, and is
-more customizable than the previous version. In this release, only x86
-systems with a BIOS uses GRUB2 by default. Work is ongoing for making
-GRUB2 the default for other architectures and systems.
-* Services Management. Fedora 15 introduced the Systemd services
-management program. This release features better integration of
-Systemd via conversion to native systemd services from legacy init
-scripts in many software components -- for desktop users, this means
-faster boot times; for system administrators it means more powerful
-management of services.
-* Desktop Updates. The two major desktop environments have been
-updated to the latest releases: KDE Software Compilation 4.7 and GNOME
-.1 development release.
-* SELinux Enhancements. SELinux policy package now includes a
-pre-built policy that will only rebuild policy if any customizations
-have been made. A sample test run shows 4 times speedup on installing
-the package from 48 Seconds to 12 Seconds and max memory usage from
-M to 6M. In addition to that, SELinux file name transition allows
-better policy management. For instance, policy writers can take
-advantage of this and write a policy rule that states, if a SELinux
-unconfined process creates a file named resolv.conf in a directory
-labelled etc_t, the file should get labeled appropriately. This
-results is less chances of mislabeled files. Also, from this release
-onwards, selinuxfs is mounted at /sys/fs/selinux instead of in
-/selinux. All the affected components including anaconda, dracut,
-livecd-tools and policycoreutils have been modified to work with this
-change.
-* System Accounts. Fedora now standardizes on login.defs as
-authority for UID/GID space allocation, and has moved boundary between
-system and user accounts from 500 to 1000 to match conventions
-followed by several other Linux distributions. Upgrading from a
-existing release will not be affected by this change and you can use
-kickstart to override this change during installation if necessary.
-* HAL Removal. HAL, a hardware abstraction layer which has been a
-deprecated component for several releases, has been completely removed
-from all Fedora spins and DVD. Software components using HAL have
-moved over to using udisks and upower as well as libudev for device
-discovery. This results in faster system bootup and faster startup for
-applications depending on device discovery.
-* Cloud Updates. Fedora now includes a number of new and improved
+* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
-features to support cloud computing, including HekaFS, a "cloud ready"
+* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>
-version of GlusterFS, including additional auth*/crypto/multi-tenancy;
-pacemaker-cloud, application service high availability in a cloud
-environment; and IaaS implementations such as Aeolus and OpenStack.
-* Virtualization. Once again Fedora raises the bar on
+"The Release Notes beats for Fedora 18 are now open:
-virtualization support, including expanded virtual network support, an
+<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
-improved Spice for managing virtual machines, restored Xen support, a
-new virtual machine lock manager, and improved ability to browse guest
-file systems.
-* Developer Improvements. Developers get many goodies with Verne,
+If you're looking for a way to dip your toes in the water, so to
-including updated Ada, Haskell and Perl environments, a new Python
+speak, writing a beat is a great way to get started. If you're a
-plugin for GCC and a number of new and improved APIs.
+regular, don't forget about the checkBeat program:
+<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>
-And that's only the beginning. A more complete list and details of all
+As a reminder, the wiki drafts of beats are due on 12 September."
-the new features in Fedora 16 is available here:
-http://fedoraproject.org/wiki/Releases/16/FeatureList
-We have nightly composes of alternate spins available here:
-http://alt.fedoraproject.org/pub/alt/nightly-composes/
-====== Contributing to Fedora ======
-For more information on common and known bugs, tips on how to report
-bugs, and the official release schedule, please refer to the release
-notes:
-* http://docs.fedoraproject.org
-There are many ways to contribute beyond bug reporting. You can help
-translate software and content, test and give feedback on software
-updates, write and edit documentation, help with all sorts of
-promotional activities, and package free software for use by millions
-of Fedora users worldwide. To get started, visit
-http://join.fedoraproject.org today!"
 <references/>
@@ Line 458: / Line 194: @@
 <references/>
-===== Remaining F16 blockers and F16 planning (2011-10-26) =====
+====New bodhi release in production====
-[[User:Adamw|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-October/000847.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>
-"Hey, folks. This mail brought to you by my ever-increasing empty liquor bottle collection and ever-receding hairline.
+"A new release of Bodhi has just been deployed to production.
+<ref>https://admin.fedoraproject.org/updates</ref>
-We unfortunately still have open blockers today, which means we will likely do a TC3 compose tonight instead of RC1. The remaining unaddressed blockers are:
+Bugs and enhancement requests can be filed here:
+<ref>http://bodhi.fedorahosted.org</ref>
-. https://bugzilla.redhat.com/show_bug.cgi?id=668282 "PackageKit yum
+Major changes in bodhi 0.9.2
-backend uses incorrect encoding for dynamic category names, makes them
+---------------------------------
-show up with '?' characters in KPackageKit"
-Nils reported that he would complete work on this today, but has not
+* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
-checked in today at all. This leaves us somewhat stuck, as only Richard
-Hughes and Nils are really qualified to work on this. Richard is away
-this week.
-. https://bugzilla.redhat.com/show_bug.cgi?id=731245 "KDE fails to
+* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
-start inside a VM , large amount of memory [@ miCopyRegion]"
-Soren fixed the initial issue, but KDE on qxl still doesn't really work
+* The submitter of an update can no longer effect the karma (Till Maas)
-correctly. Details and logs are in the latest comments on the bug, and
-I'm currently uploading a live image for convenient reproduction. Again,
-contributions are welcome here.
-. https://bugzilla.redhat.com/show_bug.cgi?id=736893 "New Install of
+* Fix duplicate status change email notifications. (Till Maas)
-Fedora 16 TC1 on iBFT iSCSI NIC fails on first reboot"
-Again, we're still rather looking for information from the reporter
+* Mention age of updates in testing digest mails (Till Maas)
-here. Tim may be able to acquire an iBFT NIC for testing today.
-. https://bugzilla.redhat.com/show_bug.cgi?id=748747 "Totem doesn't
+* Support e-mail threading in notification e-mails (Till Maas)
-display video when using software 3D rendering"
-Did not hear from ajax in relation to this bug today. Again, we really
+* Add X-Bodhi mail headers (Till Maas)
-need development input on this one.
-. https://bugzilla.redhat.com/show_bug.cgi?id=747377 "heap corruption
+* Gracefully handle private bugs (Cole Robinson)
-via multi-threaded "git grep""
-This is the bug in glibc 12.999 and 13 which can at least potentially
+* Set the default request for new updates to 'testing' in the web form
-cause just about any app to crash. We're in the middle of addressing it;
-a fixed glibc is out for testing and we are now mass-rebuilding all
-packages which hit stable since glibc 12.999 made it to the buildroot.
-This, obviously, isn't speeding up the whole release process any.
-Thanks everyone!
+* 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.
---
-Adam Williamson
-Fedora QA Community Monkey
-IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
-http://www.happyassassin.net"
-<references/>
+* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
-===== New bodhi bugfix release in production =====
-Luke Macken announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-October/000845.html</ref>:
+Full list of changes since 0.8.7
+--------------------------------
-"======bodhi v0.8.3======
+Kalpa Welivitigoda (1):
+      fixed input box alignment issue in login box #579
-Yesterday I pushed out a new bugfix release of bodhi into production. The
+Luke Macken (25):
-bodhi-client is currently on it's way to updates-testing for all releases.
+      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'
-* https://admin.fedoraproject.org/updates
+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
-I raced to get this out before the infrastructure freeze today, and since then
+Ralph Bean (19):
-there have already been many more bugfixes in git, so expect another release
+      Sending messages with fedmsg.
-shortly after F16 is released.
+      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.
-Please file bugs here<ref>https://fedorahosted.org/bodhi/newticket</ref>
+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"
-======Client fixes======
+<references/>
-* bodhi -L dies with out-of-range exception after branching f16<ref>https://fedorahosted.org/bodhi/ticket/625</ref><ref>https://bugzilla.redhat.com/show_bug.cgi?id=746780</ref>
+====Build F-18 collection packages for all language translators====
-* bodhi -r dist-f14 -b 676195 don't respect -r option<ref>https://bugzilla.redhat.com/show_bug.cgi?id=747939</ref>
+* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref>
+* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref>
-======Server fixes======
+"Hi Fedora package maintainers
-* Default to update ID-based URLs<ref>https://fedorahosted.org/bodhi/ticket/632</ref>
+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.
-* fedora-easy-karma submits too many comments to bodhi when bodhi has a server problem (edit)<ref>https://bugzilla.redhat.com/show_bug.cgi?id=698441</ref>
+Thank you so much.
-* Bodhi no longer adds comments to Security Response bugs<ref>https://fedorahosted.org/bodhi/ticket/485</ref>
+noriko
+Fedora Localization Project"
-======Buildroot override fixes======
-* Buildroot overrides require commit access to devel branch rather than branch override applies to<ref>https://fedorahosted.org/bodhi/ticket/620</ref>
-* Cannot request build root override<ref>https://bugzilla.redhat.com/show_bug.cgi?id=729722</ref>
-* buildroot overrides stay after expiration date<ref>https://bugzilla.redhat.com/show_bug.cgi?id=723071</ref>
-======Masher fixes======
-* Updates-testing report emails should use package names not update number<ref>https://fedorahosted.org/bodhi/ticket/644</ref>
-* Current updateinfo data is broken (epoch="None")<ref>https://bugzilla.redhat.com/show_bug.cgi?id=652296</ref>
-* Fedora Update System suggests to reboot when not asked to do so<ref>https://bugzilla.redhat.com/show_bug.cgi?id=681850</ref>
-Package fixes
--------------
-* bodhi-server should require python-fedora-turbogears<ref>https://bugzilla.redhat.com/show_bug.cgi?id=743975</ref>
 <references/>
-===== last stable push for f16 GA =====
+====Fedora 18 Alpha to slip by another one week====
-[[User:ausil|Dennis Gilmore]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-October/000843.html</ref>:
+* 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>
-"Hi all,
+"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>.
-on Monday October 24 we will be doing the last push to stable, after
+As a result, ALL MAJOR MILESTONES, and their dependent tasks,
-that the only things that will get pushed to stable before GA will be
+will be pushed out by one week.
-things that have been accepted as release blockers.
-Thanks
+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).
-Release Engineering"
+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/>
-===== F16 Final Change Deadline is Monday, Oct. 24 =====
-[[User:Rbergero|Robyn Bergeron]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-October/000842.html</ref>:
+=== Fedora Events ===
-"Greetings,
-This is your friendly reminder that the Final Change Deadline for F16 is
-Monday, October 24, 2011.
-* https://fedoraproject.org/wiki/Change_deadlines
-"After the change deadlines for the Final release no more updates are
-made to the branched development repository (e.g.
-/pub/fedora/linux/development/16).
-The only exceptions are accepted blocker and "nice to have" bugs:
-* https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
-* https://fedoraproject.org/wiki/QA:SOP_nth_bug_process
-All updates after this time are considered zero day updates of the
-release, and are pushed to the updates repository which is available on
-the public availability date. For example, the repository for Fedora 16
-is /pub/fedora/linux/updates/16."
-The next step in the process is to create a final release candidate (RC)
+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.
-to pass on to QA for testing as soon as possible. The RC is scheduled to be
-created on Tuesday, October 25.  Outstanding blocker bugs can delay the
-creation of the RC, possibly resulting in a one-week slip of the schedule.
-Current outstanding blocker bugs can be seen here<ref>https://fedoraproject.org/wiki/Current_Release_Blockers</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>
-Thanks,
+Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>
-Robyn"
-<references/>
-=== Fedora Events ===
-The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning.
-Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding.
-In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
-====Upcoming Events (September - December 2011)====
-* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q3_.28Sept_2011_-_November_2011.29</ref>
-* Central & South America (LATAM): <ref>http://fedoraproject.org/wiki/Events#FY12_Q3_.28September_2011_-_December_2011.29</ref>
-* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_September_2011.29</ref>
-* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY12_Q3_.28September_2011_-_November_2011.29</ref>
 <references/>
@@ Line 646: / 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