mNo edit summary |
No edit summary |
||
(133 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
==Announcements== | ==Announcements== | ||
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: | Contributing Writer: [[User:rashadul|Rashadul Islam]] | ||
<references/> | <references/> | ||
=== | ===Breaking News of the Week and Month=== | ||
< | ====[Guidelines Change] Changes to the Packaging Guidelines==== | ||
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref> | |||
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref> | |||
"A new section has been added to the SysV Initscripts section, discussing | |||
the proper use of subsys locking. Even though Fedora packages should no | |||
longer be using SysV Initscripts as a primary service mechanism, Red Hat | |||
Enterprise Linux and EPEL do. Additionally, | |||
Red Hat points partners to the Fedora Guidelines when they build for RHEL. | |||
<ref>https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism</ref> | |||
--- | |||
The review guidelines now reflect the use of sha256sum (instead of | |||
md5sum) to confirm upstream source integrity. | |||
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref> | |||
--- | |||
The PHP Packaging guidelines have been updated to include guidance about | |||
when it is appropriate to have an explicit Requires on httpd & mod_php, | |||
how to handle explicit Requires on PHP extensions, and how to handle a | |||
Requires for a minimum PHP version. | |||
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement</ref> | |||
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires</ref> | |||
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version</ref> | |||
--- | |||
A new section on Macros has been added to the Packaging Guidelines, | |||
covering Packaging of Additional RPM Macros. | |||
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref> | |||
--- | |||
A new section on the Documentation= field in systemd unit files (F17+) | |||
has been added. | |||
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref> | |||
--- | |||
A short section on the Group tag in Fedora packages has been added. | |||
All current versions of Fedora (and their respective RPM versions) treat | |||
the Group tag as optional. Packages may include a Group: field for | |||
compatibility with EPEL, but are not required to do so. | |||
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref> | |||
--- | |||
<ref> | The RHEL conditionalization has been removed from the Python3 example | ||
spec file, as it is no longer valid. | |||
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref> | |||
--- | |||
These guidelines (and changes) were approved by the Fedora Packaging | |||
Committee (FPC). | |||
'''Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.''' | |||
If you find | As a reminder: The Fedora Packaging Guidelines are living documents! If | ||
you find something missing, incorrect, or in need of revision, you can | |||
suggest a draft change. The procedure for this is documented here: | |||
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>" | |||
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref> | |||
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref> | |||
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref> | |||
<references/> | <references/> | ||
==== | ====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== | ||
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref> | |||
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref> | |||
"Greetings! (...or perhaps I should say.... bonjour!) | |||
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 | |||
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - 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: | |||
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref> | |||
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: | |||
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>" | |||
<references/> | <references/> | ||
==== | ====Fedora Infrastructure announces status.fedoraproject.org==== | ||
* 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> | |||
"I'm happy to announce the general availability of our | |||
status.fedoraproject.org site. | |||
This site provides an easy way for Fedora contributors and users to | |||
check on the status of services provided by Fedora Infrastructure. | |||
The site auto reloads every minute, and also provides a rss feed at | |||
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>. | |||
If you run into a problem or issue that is not reflected at | |||
status.fedoraproject.org, please do report it to us in #fedora-admin on | |||
irc.freenode.net or via ticket at | |||
<ref>https://fedorahosted.org/fedora-infrastructure/newticket</ref> | |||
We update the site status information manually so we need to be aware | |||
of the issue in order to keep the site accurate. | |||
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/> | ||
====Beats are open!==== | |||
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref> | |||
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref> | |||
"The Release Notes beats for Fedora 18 are now open: | |||
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref> | |||
If you're looking for a way to dip your toes in the water, so to | |||
speak, writing a beat is a great way to get started. If you're a | |||
regular, don't forget about the checkBeat program: | |||
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref> | |||
As a reminder, the wiki drafts of beats are due on 12 September." | |||
<references/> | |||
=== Fedora Development News === | === 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. | |||
The | |||
'''Acceptable Types of Announcements''' | '''Acceptable Types of Announcements''' | ||
Line 93: | Line 194: | ||
<references/> | <references/> | ||
==== | ====New bodhi release in production==== | ||
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref> | |||
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref> | |||
"A new release of Bodhi has just been deployed to production. | |||
<ref>https://admin.fedoraproject.org/updates</ref> | |||
Bugs and enhancement requests can be filed here: | |||
<ref>http://bodhi.fedorahosted.org</ref> | |||
Major changes in bodhi 0.9.2 | |||
--------------------------------- | |||
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean) | |||
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines | |||
* | * The submitter of an update can no longer effect the karma (Till Maas) | ||
* Fix duplicate status change email notifications. (Till Maas) | |||
* Mention age of updates in testing digest mails (Till Maas) | |||
* Support e-mail threading in notification e-mails (Till Maas) | |||
* Add X-Bodhi mail headers (Till Maas) | |||
* Gracefully handle private bugs (Cole Robinson) | |||
* Set the default request for new updates to 'testing' in the web form | |||
* Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable. | |||
* 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" | |||
<references/> | <references/> | ||
==== | ====Build F-18 collection packages for all language translators==== | ||
* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref> | |||
* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref> | |||
"Hi Fedora package maintainers | |||
Please build and push your package with latest translation file (e.g. | |||
pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31. | |||
Your packages with latest translation will be composed into test live | |||
image on 3-Sep Monday. Then various language translators worldwide will | |||
test the image in their own languages. Any issue will be filed as bug. | |||
This is only one chance for translators to check and modify Localization | |||
quality of your packages by checking UI, and we need your help. | |||
Thank you so much. | |||
noriko | |||
Fedora Localization Project" | |||
<references/> | |||
==== | ====Fedora 18 Alpha to slip by another one week==== | ||
* 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> | |||
"Today at Go/No-Go meeting it was decided to slip Fedora 18 | |||
Alpha release by one week due to remaining open blocker bugs<ref>http://qa.fedoraproject.org/blockerbugs/current</ref> and incomplete test matrices for Alpha <ref>https://fedoraproject.org/wiki/Test_Results:Current_Base_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test</ref>. Meeting's | |||
full log is at <ref>http://bit.ly/PC16PF</ref>. | |||
As a result, ALL MAJOR MILESTONES, and their dependent tasks, | |||
will be pushed out by one week. | |||
The next Go/No-Go meeting is on Thursday Sep 06, same place | |||
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST | |||
#fedora-meeting). | |||
If you have an accepted blocker bug, please try to fix it | |||
as soon as possible to help us with Fedora 18 Alpha release!" | |||
<references/> | <references/> | ||
Line 230: | Line 348: | ||
=== Fedora Events === | === Fedora Events === | ||
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 ( | ====Upcoming Events (September 2012 - November 2012)==== | ||
* North America (NA)<ref>http://fedoraproject.org/wiki/Events# | * '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref> | ||
* Central & South America (LATAM) | * '''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# | * '''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# | * '''India, Asia, Australia (India/APJ)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3</ref> | ||
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref> | |||
<references/> | <references/> | ||
Line 252: | 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
Breaking News of the Week and Month
[Guidelines Change] Changes to the Packaging Guidelines
"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]
- ↑ Tom Callaway tcallawa at redhat.com
- ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html
- ↑ https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism
- ↑ https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review
- ↑ https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement
- ↑ https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires
- ↑ https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version
- ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros
- ↑ https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field
- ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag
- ↑ https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file
- ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
- ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html
- ↑ https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
- ↑ 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]"
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. "
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."
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
New bodhi release in production
"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"
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"
- ↑ noriko.mizumoto at gmail.com
- ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html
Fedora 18 Alpha to slip by another one week
"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
- 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!"
- ↑ jreznik at redhat.com
- ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html
- ↑ http://qa.fedoraproject.org/blockerbugs/current
- ↑ https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
- ↑ http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
- ↑ http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
- ↑ 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]
- ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29
- ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29
- ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2
- ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3
- ↑ https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release
Past Events
Archive of Past Fedora Events[1]
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