From Fedora Project Wiki

< FWN‎ | Beats

(Announcement beat updating)
No edit summary
 
(186 intermediate revisions by 2 users not shown)
Line 2: Line 2:
==Announcements==
==Announcements==


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


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


<references/>
<references/>


===Fedora 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>http://lists.fedoraproject.org/pipermail/announce/2010-August/thread.html</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>
 
---


====Announcing the release of Fedora 14 Alpha!!====
The PHP Packaging guidelines have been updated to include guidance about
Dennis Gilmore<ref>Dennis Gilmore dennis at ausil.us</ref> on Tue Aug 24 14:15:34 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-August/002852.html</ref>,"The Fedora 14 "Laughlin" Alpha release is available!".
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>


He also mentioned, "This release offers a preview of some of the best free and open source technology currently under
---
development. Catch a glimpse of the future:
http://fedoraproject.org/get-prerelease


=====What is the Alpha release?=====
A new section on Macros has been added to the Packaging Guidelines,
The Alpha release contains all the features of Fedora 14 in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A
covering Packaging of Additional RPM Macros.
Beta release is code-complete, and bears a very strong resemblance to the third and final release. The final release of Fedora 14 is due in November.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>


We need your help to make Fedora 14 the best release yet, so please take a moment of your time to download and try out the Alpha and make sure the things that are important to you are working. If you find a bug, please report it-- every bug you uncover is a chance to improve the experience for millions of Fedora users worldwide. Together, we can make Fedora a rock-solid distribution.  (Read down to the end of the announcement for more information on how to help.)
---


Fedora 14 is named in honor of distinguished physicist Robert B. Laughlin, whose fields of research have included, among other things, the topic of emergence. Emergence is the process by which a group of individual components interact to produce a system that is more complex than the sum of its parts - a perfect description of an open source community.
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>


=====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 and session management.''' Fedora 14 introduces '''systemd''', a smarter, more efficient way of starting up and managing the background daemons that services we all use every day - such as '''NetworkManager''' and '''PulseAudio''' - rely on.
A short section on the Group tag in Fedora packages has been added.
* '''Desktop virtualization'''. High-quality access to QEMU virtual machines moves a step closer with the introduction of '''Spice''', a complete open source solution for interaction with virtualized desktops.
All current versions of Fedora (and their respective RPM versions) treat
* '''Faster JPEG compression/decompression'''. The replacement of '''libjpeg''' with '''libjpeg-turbo''' brings speed improvements to a wide range of applications when handling images in JPEG format, including photo managers, video editors and PDF readers.
the Group tag as optional. Packages may include a Group: field for
* '''New and updated programming languages'''. Fedora 14 sees the introduction of '''D''', a systems programming language combining power and high performance with programmer productivity, as well as updates to '''Python''',
compatibility with EPEL, but are not required to do so.
'''Erlang''', and '''Perl'''.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref>
* '''Better tools for developers'''. Simpler, faster debugging with '''gdb''' indexing and new commands for finding and fixing memory leaks, as well as new versions of '''NetBeans''' and '''Eclipse'''.
* '''The latest desktop environments'''. '''KDE 4.5''' introduces window tiling and better notification features, along with many stability improvements. '''Sugar 0.90''' features major usability improvements and
support for 3G networks.
* '''Improved netbook experience with MeeGo™'''. The '''MeeGo™ Netbook UX 1.0''' provides a user interface tailored specifically for netbooks, building on the foundations laid by '''Moblin''' in previous Fedora releases.
* '''Fedora on the cloud'''. From Fedora 14 onward images for EC2 will be provided for each new release, allowing users of Amazon's on-demand cloud computing platform to use the latest Fedora.
* '''IPMI server management made simple'''. New to Fedora 14 is '''ipmiutil''', an easy-to-use, fully-featured IPMI server management utility that allows a wide range of management functions to be performed with just a few commands.
* '''Support for SCAP'''. Fedora 14 introduces an open source framework for the Security Content Automation Protocol (SCAP), allowing users to automatically scan their system to check whether it complies with a defined security configuration.
* '''Perl 6 support with Rakudo'''. Fedora 14 comes with Rakudo Perl, an implementation of the Perl 6 specification based on the Parrot virtual machine, which enables developers to write new applications or port existing ones to
Perl 6.  
* '''More powerful data analysis'''. Given that Fedora 14 is named after one of the giants of modern theoretical physics, it seems appropriate that Laughlin sees the introduction to Fedora of '''ROOT''', an obejct-oriented, open-source platform for data acquisition, simulation and data analysis developed by CERN. Support for the increasingly popular '''R''' statistical programming language is also broadened with a range of new addons. 
 
These and many other improvements provide a wide and solid base for future releases, further increasing the range of possibilities for developers and helping to maintain Fedora's position at the leading edge of free and open source technology.


A more complete list and details of each new cited feature is available here:
---
<ref>http://fedoraproject.org/wiki/Releases/14/FeatureList</ref>


We have nightly composes of alternate spins available here:
The RHEL conditionalization has been removed from the Python3 example
<ref>http://alt.fedoraproject.org/pub/alt/nightly-composes/</ref>
spec file, as it is no longer valid.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>


=====Issues and Details=====
---


For more information including common and known bugs, tips on how to report bugs, and the official release schedule, please refer to the release notes:
These guidelines (and changes) were approved by the Fedora Packaging
<ref>http://fedoraproject.org/wiki/Fedora_14_Alpha_release_notes</ref>
Committee (FPC).


ATI/AMD Radeon|In particular, if a blank screen is presented during installation, especially with ATI/AMD Radeon video, please review <ref>https://fedoraproject.org/wiki/Common_F14_bugs#radeon-anaconda</ref>
'''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.'''


=====Contributing=====
As a reminder: The Fedora Packaging Guidelines are living documents! If
Bug reports are helpful, especially for Alpha.  If you encounter any issues please report them and help make this release of Fedora the best ever.
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>"


Thank you, and we hope to see you in the Fedora project!"
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/>
<references/>


===Fedora Development News===
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====   
====Fedora 14 Alpha Go/No-Go Meeting====
=====Fedora 14 Alpha Go/No-Go Meeting August 19, 2010 @ 12:00 AM UTC=====   
John Poelstra<ref>John Poelstra poelstra at redhat.com</ref> on Tue Aug 17 23:59:56 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000662.html</ref>,


======Where======
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
"Join us on irc.freenode.net #fedora-meeting for this important meeting.
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>


======When======
"Greetings! (...or perhaps I should say.... bonjour!)
Thursday, August 19, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT--Wednesday, August 18, 2010* )


======Details======
I'd like to share a few reminders and announcements regarding the  
"Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
release. This meeting is called the: '''Go/No-Go Meeting'''."


"'''Verifying that the Release criteria are met is the responsibility of the QA Team.'''"
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.


For more details about this meeting see:<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
To place a subsidy request, please follow these steps:


======Fedora 14 Alpha Blocker list======
1: Pre-register at
In the meantime keep an eye on the Fedora 14 Alpha Blocker list (which is currently EMPTY!)
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1</ref>"
put an X in the $$$ column
2: Read about the funding request process and place a funding request
ticket in the FUDCon-planning ticket tracker here:
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>


<references/>
Additionally, a few notes regarding the hotel in Paris:


=====Fedora 14 Alpha Go/No-Go Meeting: 2010-08-12 @ 12:00 UTC Recap===== 
There are other events in Paris during this time period; most notably,
Adam Williamson<ref>Adam Williamson awilliam at redhat.com</ref> on Thu Aug 12 02:10:41 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000657.html</ref>,
our first day of FUDCon will be taking place at the Open World Forum
conference, on the day in which the public is encouraged to participate
in and learn about open source projects. OWF had nearly 2000 attendees
last year. Accordingly, rooms might be in short supply as we approach
FUDCon; please, book your hotel as soon as possible, not only for
affordability purposes, but also so that you have a bed to sleep in. :)


"'''The first Fedora 14 Alpha Go/No-Go Meeting was held 2010-08-12 at 12:00 UTC (so evening of 2010-08-11 in North America).''' The outcome of the meeting was a decision to slip the Alpha release by one week due to one bug agreed to be a definite blocker:
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.


<ref>https://bugzilla.redhat.com/show_bug.cgi?id=623129</ref> "xdriver=vesa is not honored"
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/>


and one bug that is potentially a blocker, pending more data:
====Fedora Infrastructure announces status.fedoraproject.org==== 


<ref>https://bugzilla.redhat.com/show_bug.cgi?id=596985</ref> "hang at start of X11 on fresh install from DVD"
* 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>


All other bugs considered were agreed not to be release blockers and removed from the list.
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


A slip announcement will be sent with more details on the slip specifically. We aim to build an RC4 tomorrow afternoon American time
This site provides an easy way for Fedora contributors and users to
(2010-08-12) with the fix for 623129 (and possibly fixes for a couple of other bugs we decided were not blockers but would be nice to fix), and continue to research 596985 to decide if it is a blocker. If we decide it is, an RC5 build will be required.
check on the status of services provided by Fedora Infrastructure.


The automated summary of the meeting can be found here:
The site auto reloads every minute, and also provides a rss feed at
<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-08-12/gonogo.2010-08-12-00.00.html</ref>
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.


The full log of the meeting can be found here:
If you run into a problem or issue that is not reflected at
<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-08-12/gonogo.2010-08-12-00.00.log.html</ref>
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.


Thanks to all for attending and providing input."
As with everything in Fedora Infrastructure, this application is open
source. Source is available from:
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
and is released under a '''GPLv2+ license'''.
 
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
issues with outages in our infrastructure affecting status reporting. "


<references/>
<references/>


====Want to help pick the F14 Release Slogan?====  
====Beats are open!====
Robyn Bergeron Robyn<ref>Bergeron robyn.bergeron at gmail.com</ref> on Wed Aug 11 20:40:12 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000659.html</ref>,


"We need a slogan for the F14 release. '''A release slogan is a short call-to-action that fits the artwork theme from Design''', found at
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
<ref>https://fedoraproject.org/wiki/F14_release_slogan#Themes</ref>. (F13's slogan was "'''Rock it'''.")
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>


If you are interested in suggesting ideas for the release slogan, please take a look at the Release Slogan SOP, and the criteria for
"The Release Notes beats for Fedora 18 are now open:
selection, at <ref>https://fedoraproject.org/wiki/Release_slogan_SOP</ref>. The slogan must be:
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


* short (1-3 words)
If you're looking for a way to dip your toes in the water, so to
* a call to action
speak, writing a beat is a great way to get started. If you're a
* positive
regular, don't forget about the checkBeat program:
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>


It should reinforce that Fedora helps the user achieve something great. It should also reflect some of ideas and themes found in the
As a reminder, the wiki drafts of beats are due on 12 September."
release artwork, and, if possible, also touch upon the Four Foundations (<ref>https://fedoraproject.org/wiki/Foundations</ref>).


Please put your slogan ideas here:<ref>https://fedoraproject.org/wiki/F14_release_slogan#New_slogan_ideas</ref>
<references/>


'''The deadline for submissions is Tuesday, August 17, at 21:00 UTC''', which is our next Marketing meeting(<ref>https://fedoraproject.org/wiki/Marketing_meetings</ref>). We'll be discussing submissions there, and then the FPL, Mo Duffy, and the Marketing team lead (that's me!) will take that input and '''select the final slogan on Wednesday, August 18'''.  
=== 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.


Let me know if you have any questions, comments, or concerns -- and let the wiki table know if you have any ideas!"
'''Acceptable Types of Announcements'''
* Policy or process changes that affect developers.
* Infrastructure changes that affect developers.
* Tools changes that affect developers.
* Schedule changes
* Freeze reminders
 
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


<references/>
<references/>


====One week slip of Fedora 14 schedule====  
====New bodhi release in production====
Jared K. Smith<ref>Jared K. Smith jsmith at fedoraproject.org</ref> on Thu Aug 12 01:57:40 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000656.html</ref>,


"Today we held our readiness meeting for the Alpha release of Fedora 14. As you may know, this is a meeting with representatives from the
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
Development, Release Engineering, and Quality Assurance teams. In these meetings, we evaluate the list of blocker bugs and give a "go"
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>
or "no go" signal on the state of the Fedora release.


You can read the minutes of the meeting here<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-08-12/gonogo.2010-08-12-00.00.html</ref>, but in short the decision was made that the release has not passed its release criteria<ref>http://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria</ref>.  When this happens, the entire release schedule is slipped by a week, and we work to get things in better shape for the next meeting. We'll get the schedule<ref>http://fedoraproject.org/wiki/Releases/14/Schedule</ref> updated in the next day or so, but in general this means that our '''general availability date for Fedora 14 has now gone from October 26th to November 2nd'''.
"A new release of Bodhi has just been deployed to production.
<ref>https://admin.fedoraproject.org/updates</ref>


During composition of any further release candidates, the Fedora Release Engineering and Quality Assurance teams plan to be quite conservative in the updates they pull into the release candidates, so that we don't inadvertently create more blocker bugs. '''I'd also like to thank those who have really pushed hard to try to get the Alpha into shape. In particular, the Release Engineering team put in a lot of extra hours to compose our release candidates, and the QA team did a fantastic job of testing the release candidates and knocking out as many blocker bugs as possible'''.
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>


While I regret the fact that the schedule has slipped, I'm confident it was the right decision to ensure that Fedora 14 is a rock-solid
Major changes in bodhi 0.9.2
release."
---------------------------------


<references/>
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)


====155 more python packages need to be rebuilt for Python 2.7==== 
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
Nils Philippsen<ref>Nils Philippsen nils at redhat.com</ref> on Wed Aug 11 19:26:56 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000658.html</ref>,


"a lot of packages were rebuilt for Python 2.7 recently, but unfortunately they've turned out to be not all that needed rebuilding.
* The submitter of an update can no longer effect the karma (Till Maas)
Essentially, all packages that contain .py files that aren't below /usr/lib(64)/python need to be rebuilt so that their respective
pre-built .pyc/.pyo files are built with the new Python version.


If the packages aren't rebuilt, python will either attempt to rebuild the .pyc/.pyo files (and fail due to SELinux policy) during runtime (if run as root<ref>https://bugzilla.redhat.com/show_bug.cgi?id=621726 - 'SELinux is preventing /usr/bin/python "write" access on /usr/share/system-config-firewall.'</ref>) or the program will take longer to startup because the python interpreter needs to parse the .py files everytime (and can't just use the respective .pyc/.pyo files since they're invalid).
* Fix duplicate status change email notifications. (Till Maas)


The reason why this hasn't been noticed/why those packages haven't been covered in the mass rebuild is because they don't require
* Mention age of updates in testing digest mails (Till Maas)
"python(abi)" (which was used to find out which packages to rebuild) even though the contained .pyc/.pyo files clearly do. This is because
the pythondeps.sh used by rpmbuild only adds that dependency to packages which have modules in the standard paths<ref>https://bugzilla.redhat.com/show_bug.cgi?id=623233 - 'python(abi)autodetection needed for all .py[co] files, not just those
beneath /usr/lib*/python*'</ref>.


Thanks to Kalev Lember who wrote a script identifying the affected packages. Using its output, Dave Malcolm has just mass-filed bugs
* Support e-mail threading in notification e-mails (Till Maas)
against the packages which we could identify and he's looking to get these rebuilt en-masse as well. Owners or comaintainers still would need to file update requests so the packages actually end up where the users can get them ;-). For this purpose, I've attached two lists to this mail: one listing the affected packages and their owners and comaintainers, the other listing the affected packages each person owns or comaintains.


Please file updates when your packages have been rebuilt and nag us if they don't get rebuilt in time, whatever that means.
* Add X-Bodhi mail headers (Till Maas)


Thanks for your help"
* Gracefully handle private bugs (Cole Robinson)


<references/>
* Set the default request for new updates to 'testing' in the web form


====New bodhi release in production==== 
* 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.
Luke Macken<ref>Luke Macken lmacken at redhat.com</ref> on Thu Aug 12 21:57:28 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000660.html</ref>,


"A new version of bodhi has just hit production.  This release contains a number of bugfixes and improvements, along with some important process changes.
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
      <ref>https://admin.fedoraproject.org/updates</ref>


=====ChangeLog=====
* Package update acceptance criteria compliance <ref>https://fedoraproject.org/wiki/Package_update_acceptance_criteria</ref>


      - Disable direct-to-stable pushes(<ref>https://fedorahosted.org/bodhi/ticket/434</ref>)
Full list of changes since 0.8.7
--------------------------------


      - Minimum time-in-testing requirements
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579


          - Every day bodhi will look for updates that have been in testing for N days (fedora: N=7, epel: N=14), and will add a comment notifying the maintainer that the update is now able to be pushed to stable.
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'


          - When someone tries to push an update to stable, bodhi will look to see if it has the appropriate karma, or if it has been in testing for more than N days.
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


* Critical path update changes
Ralph Bean (19):
  - Hide obsolete updates in our critpath view(<ref>https://fedorahosted.org/bodhi/ticket/447</ref>)
      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.


  - Disabled strict critical path procedures for EPEL
Till Maas (8):
      - EPEL is back to the same process that it has always had
      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"


  - Add a new nagmail message for unapproved critical path updates
<references/>


* RSS feed & grid of unapproved critical path updates
====Build F-18 collection packages for all language translators====
* <ref>https://admin.fedoraproject.org/updates/rss/rss2.0?critpath=True&release=F13</ref>
* <ref>https://admin.fedoraproject.org/updates/critpath?unapproved=True&release=F13</ref>
* RSS feed & grid of user-specific comments(<ref>https://fedorahosted.org/bodhi/ticket/445</ref>)
    <ref>https://admin.fedoraproject.org/updates/comments?user=lmacken</ref>
* <ref>https://admin.fedoraproject.org/updates/rss/rss2.0?comments=True&user=lmacken</ref>
* Package-specific RSS feeds of updates(<ref>https://fedorahosted.org/bodhi/ticket/339</ref>)
    <ref>https://admin.fedoraproject.org/updates/rss/rss2.0?package=kernel</ref>
* Add more links to the package-specific page
      <ref>https://admin.fedoraproject.org/updates/TurboGears2</ref>
* Show 7 days worth of entries in our RSS feeds, as opposed to 20 entries (<ref>https://fedorahosted.org/bodhi/ticket/339</ref>)
* Bodhi command-line client fixes
  - Output now goes to stdout, instead of stderr (<ref>https://fedorahosted.org/bodhi/ticket/449</ref>)
    (Thanks to Till Maas)


  - Duplicate logging issue resolved(<ref>https://bugzilla.redhat.com/show_bug.cgi?id=613533</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>


  - Support using --critpath and --type with --testable
"Hi Fedora package maintainers


* Link to the submitter and release on the home page & testing list (Thanks to Till Maas)
Please build and push your package with latest translation file (e.g.
* Made the suggest_reboot flag actually configurable
pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31.
    (<ref>https://fedorahosted.org/bodhi/ticket/352</ref>)
Your packages with latest translation will be composed into test live
* Notify the security team when an update is edited and turned into a security update (<ref>https://fedorahosted.org/bodhi/ticket/403</ref>)
image on 3-Sep Monday. Then various language translators worldwide will
* Only verify the autokarma thresholds if it is enabled (Thanks to Till Maas)
test the image in their own languages. Any issue will be filed as bug.
* Only touch bugs under the Fedora/EPEL Bugzilla products
This is only one chance for translators to check and modify Localization
    (<ref>https://fedorahosted.org/bodhi/ticket/448</ref>)
quality of your packages by checking UI, and we need your help.
* Prevent the masher from pushing obsolete updates
* Prevent obsolete updates from getting auto-promoted to stable
* Obsolete updates upon deletion, as opposed to destroying them.
* Added more unit tests (up to 122)
* Link up bug numbers and other URLs in the text of comments
* Document the `newpackage` update type in the bodhi-client commands
  (<ref>https://bugzilla.redhat.com/show_bug.cgi?id=621828</ref>)
* Set bugs to MODIFIED upon submission
  (<ref>https://fedorahosted.org/bodhi/ticket/343</ref>)
* Added a `bodhi --push-request={stable,testing}` command to improve our releng updates push workflow
* A new /updates/releases JSON API and python-fedora BodhiClient.get_releases() method for AutoQA
* Have the build auto-completion widget query candidate builds from koji, as opposed to looking in /mnt/koji/packages
    (<ref>https://fedorahosted.org/bodhi/ticket/173</ref>)


=====Bugs & RFEs=====
Thank you so much.
Please file and bug reports or enhancement requests here:<ref>https://fedorahosted.org/bodhi/newticket</ref>"
 
noriko
Fedora Localization Project"


<references/>
<references/>


====Outage: PHX2 network outage - 2010-08-15 01:00 UTC====  
====Fedora 18 Alpha to slip by another one week====
Mike McGrath<ref>Mike McGrath mmcgrath at redhat.com</ref> on Fri Aug 13 00:12:20 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000661.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>


"'''There will be an outage starting at 2010-08-15 01:00 UTC, which will last approximately 4 hours.'''
"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>.


To convert UTC to your local time, take a look at <ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
As a result, ALL MAJOR MILESTONES, and their dependent tasks,  
or run:
will be pushed out by one week.
date -d '2010-08-15 01:00 UTC'


=====Reason for outage=====
The next Go/No-Go meeting is on Thursday Sep 06, same place
Network work is being done in our primary hosting facility.  Some services may be offline during this time.  It is possible nothing will go offline.
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
#fedora-meeting).


=====Affected Services=====
If you have an accepted blocker bug, please try to fix it
* Bodhi - <ref>https://admin.fedoraproject.org/updates/</ref>
as soon as possible to help us with Fedora 18 Alpha release!"
* Buildsystem - <ref>http://koji.fedoraproject.org/</ref>
* CVS / Source Control
* Email system
* Fedora Account System - <ref>https://admin.fedoraproject.org/accounts/</ref>
* Fedora Community - <ref>https://admin.fedoraproject.org/community/</ref>
* Fedora Hosted - <ref>https://fedorahosted.org/</ref>
* Fedora People - <ref>http://fedorapeople.org/</ref>
* Fedora Talk - <ref>http://talk.fedoraproject.org/</ref>
* Mirror Manager - <ref>https://admin.fedoraproject.org/mirrormanager/</ref>
* Package Database - <ref>https://admin.fedoraproject.org/pkgdb/</ref>
* Smolt - <ref>http://smolts.org/</ref>
* Translation Services - <ref>http://translate.fedoraproject.org/</ref>
* Wiki - <ref>http://fedoraproject.org/wiki/</ref>


=====Unaffected Services=====
<references/>
* BFO - <ref>http://boot.fedoraproject.org/</ref>
* DNS - ns1.fedoraproject.org, ns2.fedoraproject.org</ref>
* Docs - <ref>http://docs.fedoraproject.org/</ref>
* Main Website - <ref>http://fedoraproject.org/</ref>
* Mirror List - <ref>https://mirrors.fedoraproject.org/</ref>
* Spins - <ref>http://spins.fedoraproject.org/</ref>
* Start - <ref>http://start.fedoraproject.org/</ref>
* Torrent - <ref>http://torrent.fedoraproject.org/</ref>


=====Ticket Link=====
The link is at<ref>https://fedorahosted.org/fedora-infrastructure/ticket/2335</ref>


=====Contact Information=====
=== Fedora Events ===
Please join '''#fedora-admin in irc.freenode.net''' or respond to this email<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000661.html</ref> to track the status of this outage."


<references/>
The purpose of Fedora Event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning and press releases.


===Fedora Events===
====Upcoming Events (September 2012 - November 2012)====
Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
* '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref>
* '''Central & South America (LATAM)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29</ref>
* '''Europe, Middle East, and Africa (EMEA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2</ref>
* '''India, Asia, Australia (India/APJ)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3</ref>


====Upcoming Events (June 2010 - August 2010)====
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29</ref>
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4</ref>


<references/>
<references/>
====Past Events====
====Past Events====
Archive of Past Fedora Events<ref>http://fedoraproject.org/wiki/FedoraEvents/PastEvents</ref>
Archive of Past Fedora Events<ref>http://fedoraproject.org/wiki/FedoraEvents/PastEvents</ref>
Line 322: Line 372:
* [[Event reports]] -- guidelines and suggestions.
* [[Event reports]] -- guidelines and suggestions.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
===Fedora Press Releases===
Fedora press releases will be found at the link:
http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases

Latest revision as of 11:18, 31 August 2012

Announcements

Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements[1], development announcements[2] and Fedora Events[3].

Contributing Writer: Rashadul Islam

  1. ↑ http://lists.fedoraproject.org/pipermail/announce/
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/
  3. ↑ http://fedoraproject.org/wiki/Events

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

  • Contributor: [[User:Spot|Tom Callaway][1]
  • Posted Date: Wed Aug 1 19:28:57 UTC 2012[2]

"A new section has been added to the SysV Initscripts section, discussing the proper use of subsys locking. Even though Fedora packages should no longer be using SysV Initscripts as a primary service mechanism, Red Hat Enterprise Linux and EPEL do. Additionally, Red Hat points partners to the Fedora Guidelines when they build for RHEL. [3]

---

The review guidelines now reflect the use of sha256sum (instead of md5sum) to confirm upstream source integrity. [4]

---

The PHP Packaging guidelines have been updated to include guidance about when it is appropriate to have an explicit Requires on httpd & mod_php, how to handle explicit Requires on PHP extensions, and how to handle a Requires for a minimum PHP version. [5] [6] [7]

---

A new section on Macros has been added to the Packaging Guidelines, covering Packaging of Additional RPM Macros. [8]

---

A new section on the Documentation= field in systemd unit files (F17+) has been added. [9]

---

A short section on the Group tag in Fedora packages has been added. All current versions of Fedora (and their respective RPM versions) treat the Group tag as optional. Packages may include a Group: field for compatibility with EPEL, but are not required to do so. [10]

---

The RHEL conditionalization has been removed from the Python3 example spec file, as it is no longer valid. [11]

---

These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).

Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.

As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: [12]"

Enclosure: Here is one late change to the Fedora Packaging Guidelines:[13] [14] [15]

  1. ↑ Tom Callaway tcallawa at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html
  3. ↑ https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism
  4. ↑ https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review
  5. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement
  6. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires
  7. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version
  8. ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros
  9. ↑ https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field
  10. ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag
  11. ↑ https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file
  12. ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
  13. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html
  14. ↑ https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
  15. ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

  • Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron][1]
  • Posted Date: Fri Aug 3 17:00:53 UTC 2012[2]

"Greetings! (...or perhaps I should say.... bonjour!)

I'd like to share a few reminders and announcements regarding the upcoming FUDCon in Paris, France, on October 13-15, 2012.

If you are planning to attend FUDCon and need a travel subsidy to do so, the ticketing system is now open for those requests. Requests will be accepted through August 15, 2012. Please note that funding requests without a ticket will not be considered. Preference will be given to attendees from the EMEA region who are actively contributing to Fedora, and have detailed their participation plans for FUDCon in their request.

To place a subsidy request, please follow these steps:

1: Pre-register at [3] - and put an X in the $$$ column 2: Read about the funding request process and place a funding request ticket in the FUDCon-planning ticket tracker here: [4]

Additionally, a few notes regarding the hotel in Paris:

There are other events in Paris during this time period; most notably, our first day of FUDCon will be taking place at the Open World Forum conference, on the day in which the public is encouraged to participate in and learn about open source projects. OWF had nearly 2000 attendees last year. Accordingly, rooms might be in short supply as we approach FUDCon; please, book your hotel as soon as possible, not only for affordability purposes, but also so that you have a bed to sleep in. :)

We currently have a rate of EUR81 per night at the ibis Paris La Vilette Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. However, this rate will expire at the end of August, and any remaining rooms in our block will expire.

For instructions on booking your hotel, please read the Lodging/Hotel section of the FUDCon: Paris wiki: [5]"

  1. ↑ rbergero at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html
  3. ↑ http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration
  4. ↑ https://fedorahosted.org/fudcon-planning/wiki/FundingRequest
  5. ↑ http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel

Fedora Infrastructure announces status.fedoraproject.org

  • Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ][1]
  • Posted Date: Thu Aug 30 20:31:24 UTC 2012[2]

"I'm happy to announce the general availability of our status.fedoraproject.org site.

This site provides an easy way for Fedora contributors and users to check on the status of services provided by Fedora Infrastructure.

The site auto reloads every minute, and also provides a rss feed at [3].

If you run into a problem or issue that is not reflected at status.fedoraproject.org, please do report it to us in #fedora-admin on irc.freenode.net or via ticket at [4] We update the site status information manually so we need to be aware of the issue in order to keep the site accurate.

As with everything in Fedora Infrastructure, this application is open source. Source is available from: [5] and is released under a GPLv2+ license.

This application is hosted at the link[6] to avoid any issues with outages in our infrastructure affecting status reporting. "

  1. ↑ kevin at scrye.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html
  3. ↑ http://status.fedoraproject.org/changes.rss of any changes
  4. ↑ https://fedorahosted.org/fedora-infrastructure/newticket
  5. ↑ http://git.fedorahosted.org/git/fedora-status.git
  6. ↑ https://openshift.redhat.com

Beats are open!

  • Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton][1]
  • Posted Date: Tue Aug 28 15:35:59 UTC 2012[2]

"The Release Notes beats for Fedora 18 are now open: [3]

If you're looking for a way to dip your toes in the water, so to speak, writing a beat is a great way to get started. If you're a regular, don't forget about the checkBeat program: [4]

As a reminder, the wiki drafts of beats are due on 12 September."

  1. ↑ kevin at scrye.com
  2. ↑ http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html
  3. ↑ https://fedoraproject.org/wiki/Category:Documentation_beats
  4. ↑ http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html

Fedora Development News

The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above
  1. ↑ https://admin.fedoraproject.org/mailman/listinfo/devel-announce

New bodhi release in production

  • Contributor: [[User:Lmacken|Luke Macken ][1]
  • Posted Date: Thu Aug 9 21:53:41 UTC 2012[2]

"A new release of Bodhi has just been deployed to production. [3]

Bugs and enhancement requests can be filed here: [4]

Major changes in bodhi 0.9.2

  • fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
  • Re-organized the links on the front page, and link to the new Update Feedback Guidelines
  • The submitter of an update can no longer effect the karma (Till Maas)
  • Fix duplicate status change email notifications. (Till Maas)
  • Mention age of updates in testing digest mails (Till Maas)
  • Support e-mail threading in notification e-mails (Till Maas)
  • Add X-Bodhi mail headers (Till Maas)
  • Gracefully handle private bugs (Cole Robinson)
  • Set the default request for new updates to 'testing' in the web form
  • Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
  • Fixed the input box alignment in the login box (Kalpa Welivitigoda)


Full list of changes since 0.8.7

Kalpa Welivitigoda (1): 

     fixed input box alignment issue in login box #579

Luke Macken (25): 

     Convert our tags_url to a byte string before passing it to urlgrabber.
     Add a script to detect when older builds become the 'latest' in stable
     Update our test suite to reproduce ticket [ticket:683]
     Fix a bug in our critpath policy ([ticket:683]).
     Set the default request for new updates to 'testing'
     Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
     Fix a busted unit test (test_push_EPEL_critpath_before_tested)
     Add pkg_resources __requires__ hacks to bodhi tools to mitigate version

conflicts 

     Handle the case where a release doesn't have any overrides
     Change our X-Bodhi-Update-Release header to use the short name
     Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
     Update our unit tests to assume submitters cannot alter karma
     Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
     Merge branch 'feature/bodhi1-fedmsg' into develop
     Fix a typo in the metrics tool
     Fix a typo in the new mail headers
     Re-organize our links, and add one to the new update feedback guidelines
     Clean up stray buildroot overrides
     Version bump for 0.9.2
     Our build script uses bz2
     Merge branch 'release/0.9.2'

Mathieu Bridon (6): 

     Have bodhi-init create all the tables
     masher: Fix the comparison
     masher: Reuse variable
     setup: Fix the Turbogears version requirement
     Don't version control auto-generated files
     setup: Add missing dependencies

Ralph Bean (19): 

     Sending messages with fedmsg.
     No longer using fedmsg schema/validation.
     fedmsg.ini -> fedmsg-config.py
     More detail in the update.complete message.
     More concise send_message calls.
     Ignore dev db.
     Merge branch 'master' into bodhi1-fedmsg
     Updates for the latest fedmsg.  Getting tests passing.
     Merge branch 'master' into bodhi1-fedmsg
     Ignore mashing fedora file.
     Fixed what I think is a regression in login template.
     Merge branch 'master' into bodhi1-fedmsg
     Update to test fedmsg config.  Work with both tests and under WSGI.
     Version bump for fedmsg in staging.
     Only send the comment with a comment is added, not the whole update.
     Using a "bodhi" user/group for mod_wsgi.
     fedmsg+ssl changes to bodhi.spec.
     Use modern fedmsg config format.
     Disable message signing for bodhi tests.

Till Maas (8): 

     Add X-Bodhi mail headers
     Support e-mail threading in notification e-mails
     Mention age of updates in testing digest mails
     Use format string instead of string concatenation
     Import exceptions from sqlite3
     Remove files used by mercurial
     model.py: Change karma from Submitter to 0
     Fix notification on automatic status change"
  1. ↑ lmacken at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html
  3. ↑ https://admin.fedoraproject.org/updates
  4. ↑ http://bodhi.fedorahosted.org

Build F-18 collection packages for all language translators

  • Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto][1]
  • Posted Date: Thu Aug 30 09:17:01 UTC 2012[2]

"Hi Fedora package maintainers

Please build and push your package with latest translation file (e.g. pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31. Your packages with latest translation will be composed into test live image on 3-Sep Monday. Then various language translators worldwide will test the image in their own languages. Any issue will be filed as bug. This is only one chance for translators to check and modify Localization quality of your packages by checking UI, and we need your help.

Thank you so much.

noriko Fedora Localization Project"

  1. ↑ noriko.mizumoto at gmail.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html

Fedora 18 Alpha to slip by another one week

  • Contributor: [[User:JaroslavReznik|Jaroslav Reznik][1]
  • Posted Date: Thu Aug 30 23:26:35 UTC 2012[2]

"Today at Go/No-Go meeting it was decided to slip Fedora 18 Alpha release by one week due to remaining open blocker bugs[3] and incomplete test matrices for Alpha [4][5][6]. Meeting's full log is at [7].

As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week.

The next Go/No-Go meeting is on Thursday Sep 06, same place but different time (19:00 UTC, 3 PM EDT, 21:00 CEST

  1. fedora-meeting).

If you have an accepted blocker bug, please try to fix it as soon as possible to help us with Fedora 18 Alpha release!"

  1. ↑ jreznik at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html
  3. ↑ http://qa.fedoraproject.org/blockerbugs/current
  4. ↑ https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
  5. ↑ http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
  6. ↑ http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
  7. ↑ http://bit.ly/PC16PF


Fedora Events

The purpose of Fedora Event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning and press releases.

Upcoming Events (September 2012 - November 2012)

  • North America (NA)[1]
  • Central & South America (LATAM)[2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Guideline to write Fedora Press Releases[5]

  1. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29
  2. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29
  3. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2
  4. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3
  5. ↑ https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release

Past Events

Archive of Past Fedora Events[1]

  1. ↑ http://fedoraproject.org/wiki/FedoraEvents/PastEvents

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.

Fedora Press Releases

Fedora press releases will be found at the link: http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases

Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Announcements&oldid=300097"