From Fedora Project Wiki

< FWN‎ | Beats

mNo edit summary
No edit summary
 
(166 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>
 
---
 
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>


====FUDCon LATAM 2011 bids====
---


'''Paul W. Frields<ref>http://pfrields.fedorapeople.org/</ref> on Fri Sep 17 17:53:31 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-September/002862.html</ref>,'''
A short section on the Group tag in Fedora packages has been added.
All current versions of Fedora (and their respective RPM versions) treat
the Group tag as optional. Packages may include a Group: field for
compatibility with EPEL, but are not required to do so.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref>


"The bid period for the next Fedora Users and Developers Conference (FUDCon) in the LATAM region is open, and will remain open for a few more weeks.  The bid process for FUDCon is outlined here:
---
<ref>https://fedoraproject.org/wiki/FUDCon_bid_process</ref>


Two bids have already been received for FUDCon at this point, and the process will continue soon with an award, a budget, and an open and transparent planning process:
The RHEL conditionalization has been removed from the Python3 example
<ref>http://fedoraproject.org/wiki/FUDCon:LATAM_2011_Bid_Panama</ref>
spec file, as it is no longer valid.
<ref>http://fedoraproject.org/wiki/FUDCon:LATAM_2011_Bid_Foz</ref>
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>


Bids will continue to be accepted until *September 30, 2010*.  Bids must be published on the Fedora wiki, and a URL for the bid sent to the fudcon-planning list:
---
<ref>https://lists.fedoraproject.org/mailman/listinfo/fudcon-planning</ref>


The majority budget holder, the Community Architecture team, will consult with the bid teams and regional Ambassador leadership, work with the Fedora Project Leader to decide on a location and date, and make an announcement of the next LATAM region FUDCon soon afterward. Decisions for a FUDCon location are made on the basis of many factors, including costs, quality and quantity of bid information provided, facilities available, bid team commitment, and the desire to move FUDCon around a given region where practical.
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).


Once the venue and dates are decided, planning for the LATAM region FUDCon event is expected to happen on the general fudcon-planning list.  Planning will include regular, weekly meetings and use of a publicly visible ticket queue.  This transparency helps the Fedora community participate; community members can help organizers plan and execute the work that goes into the FUDCon event.  That participation can produce a higher quality event that meets or exceeds attendee expectations.
'''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.'''


'''FUDCon is held several times each year around the globe as part of Fedora's premier events strategy. You can read more about Fedora events here:
As a reminder: The Fedora Packaging Guidelines are living documents! If
<ref>https://fedoraproject.org/wiki/Premier_Fedora_Events</ref>
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>"


'''Please remove 'announce-list' from any replies to this message, since they'll be removed from its moderation queue. Thank you!'''"
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====  
The fedora development news list is intended to be a low traffic announce-only list for Fedora development.<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref>


* '''Acceptable Types of Announcements'''
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
- Policy or process changes that affect developers.
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>
- Infrastructure changes that affect developers.
- Tools changes that affect developers.
- Schedule changes
- Freeze reminders


* '''Unacceptable Types of Announcements'''
"Greetings! (...or perhaps I should say.... bonjour!)
- Periodic automated reports (violates the INFREQUENT rule)
- Discussion
- Anything else not mentioned above


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/>


====We have reached Fedora 14 Feature Complete====   
====Fedora Infrastructure announces status.fedoraproject.org====   


=====By John Poelstra=====
* 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>


John Poelstra <ref>John Poelstra poelstra at redhat.com</ref> on Wed Sep 15 22:46:50 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000684.html</ref>,
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


"Thank you to all the feature owners and developers for all their hard work to make Fedora 14 the best Fedora release yet. We are almost to the end!
This site provides an easy way for Fedora contributors and users to
check on the status of services provided by Fedora Infrastructure.


As a follow-up to last week's reminder
The site auto reloads every minute, and also provides a rss feed at
<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000676.html</ref>
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.


ALL feature pages are now expected to be at 100% completion. The following features are not listed at 100% complete and are being sent to FESCo (<ref>https://fedorahosted.org/fesco/ticket/468</ref>) for re-evaluation for inclusion in the Fedora 14 feature list if they remain incomplete:
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.


<ref>https://fedoraproject.org/wiki/Features/D_Programming</ref> (yes, a mere technicality at 99% done)
As with everything in Fedora Infrastructure, this application is open
<ref>https://fedoraproject.org/wiki/Features/GdbIndex</ref>
source. Source is available from:
<ref>https://fedoraproject.org/wiki/Features/GNUstep</ref>
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
<ref>https://fedoraproject.org/wiki/Features/MemoryDebuggingTools</ref>
and is released under a '''GPLv2+ license'''.  
<ref>https://fedoraproject.org/wiki/Features/Python_2.7</ref>
 
<ref>https://fedoraproject.org/wiki/Features/Spice</ref>
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/>


=====David Malcolm =====
====Beats are open!====


To continue the thread, David Malcolm </ref>David Malcolm dmalcolm at redhat.com<ref> on Thu Sep 16 21:30:43 UTC 2010 announced <ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000688.html</ref>,
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>


"On Wed, 2010-09-15 at 15:46 -0700, John Poelstra wrote:
"The Release Notes beats for Fedora 18 are now open:
> Thank you to all the feature owners and developers for all their hard work to make Fedora 14 the best Fedora release yet.  We are almost to the end!
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
>  
> As a follow-up to last week's reminder
> http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000676.html
>
> ALL feature pages are now expected to be at 100% completion.  The following features are not listed at 100% complete and are being sent to FESCo (https://fedorahosted.org/fesco/ticket/468) for re-evaluation for inclusion > in the Fedora 14 feature list if they remain incomplete:


> https://fedoraproject.org/wiki/Features/MemoryDebuggingTools
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>


I held off on saying "100%" there as I hoped to add C++ support to the "what is this RAM being used for" heuristics.  Unfortunately that part of it needs some optimization work before it can be enabled.  The rest
As a reminder, the wiki drafts of beats are due on 12 September."
of the feature works, but has bugs, so I've marked it as 100%; C++ support deferred; I've updated the feature page accordingly, and I'm working on improving the docs.


> https://fedoraproject.org/wiki/Features/Python_2.7</ref>
<references/>


This is essentially done (given the caveat in the release notes on that page), but a few stragglers are left to rebuild; some of them are fiddly.  I believe that there's no significant risk to the release as a whole from those; I hope to look at them later tonight/tomorrow.
=== 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.


Sorry about this (got bogged down in RHEL work)"
'''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/>


====Fedora 14 Beta Change Deadline Reached 2010-09-14====  
====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


'''John Poelstra<ref>John Poelstra poelstra at redhat.com</ref> on Wed Sep 15 22:59:53 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000685.html</ref>,'''
* The submitter of an update can no longer effect the karma (Till Maas)


"As a reminder, we have reached the Beta Change Deadline for Fedora 14.
* Fix duplicate status change email notifications. (Till Maas)


"At the change deadlines for Alpha and Beta, pushes to the branched development repository (e.g. /pub/fedora/linux/development/14), are suspended until the Release Candidate has been successfully tested and staging has started to the mirrors."
* Mention age of updates in testing digest mails (Till Maas)


More details are located here: <ref>https://fedoraproject.org/wiki/Change_deadlines</ref>"
* Support e-mail threading in notification e-mails (Till Maas)


<references/>
* Add X-Bodhi mail headers (Till Maas)


====Fedora 14 Beta Release Date at Risk==== 
* Gracefully handle private bugs (Cole Robinson)


'''John Poelstra<ref>John Poelstra poelstra at redhat.com</ref> on Thu Sep 16 22:31:14 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000686.html</ref>,'''
* Set the default request for new updates to 'testing' in the web form


"We have missed the Fedora 14 Beta RC compose scheduled today because of unresolved Fedora 14 Beta Blocker bugs.
* 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.


<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=611991&hide_resolved=1</ref>(NEW or ASSIGNED)
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)


As soon as these bugs are resolved with new packages we will request an RC compose from Release Engineering."


<references/>
Full list of changes since 0.8.7
--------------------------------


====bodhi v0.7.9 deployed==== 
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579


'''Luke Macken<ref>Luke Macken lmacken at redhat.com</ref> on Mon Sep 20 18:19:06 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000687.html</ref>,'''
Luke Macken (25):
      Convert our tags_url to a byte string before passing it to urlgrabber.
      Add a script to detect when older builds become the 'latest' in stable
      Update our test suite to reproduce ticket [ticket:683]
      Fix a bug in our critpath policy ([ticket:683]).
      Set the default request for new updates to 'testing'
      Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
      Fix a busted unit test (test_push_EPEL_critpath_before_tested)
      Add pkg_resources __requires__ hacks to bodhi tools to mitigate version
conflicts
      Handle the case where a release doesn't have any overrides
      Change our X-Bodhi-Update-Release header to use the short name
      Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
      Update our unit tests to assume submitters cannot alter karma
      Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
      Merge branch 'feature/bodhi1-fedmsg' into develop
      Fix a typo in the metrics tool
      Fix a typo in the new mail headers
      Re-organize our links, and add one to the new update feedback guidelines
      Clean up stray buildroot overrides
      Version bump for 0.9.2
      Our build script uses bz2
      Merge branch 'release/0.9.2'


"A new version of bodhi has just hit production.  This release contains a number of bugfixes and enhancements.
Mathieu Bridon (6):
<ref>https://admin.fedoraproject.org/updates</ref>
      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


=====Web UI Changes=====
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.


* Improved editing functionality
Till Maas (8):
    - Only unpush edited updates when builds are altered
      Add X-Bodhi mail headers
    - Make a note in the comments of which builds were added/removed
      Support e-mail threading in notification e-mails
* Allow people to revert their karma vote more than once
      Mention age of updates in testing digest mails
* Add mouseover tooltips to the update status with more details
      Use format string instead of string concatenation
* Prevent different versions of a package from being added to the same update
      Import exceptions from sqlite3
* Handle more types of bugzilla auto-linking in comments (ex: rhbz#1234)
      Remove files used by mercurial
* Link to the newer update in the obsoleted ones
      model.py: Change karma from Submitter to 0
* Link to gitweb instead of viewvc
      Fix notification on automatic status change"
* Set default (un)stable karma values if re-enabled
* Anonymous karma has never effected karma, so we now mark them as being ignored in the interface to make it obvious
* Get the 'suggest reboot' flag working again
* Allow non-critpath updates to be pushed to stable after meeting our critpath requirements
* Allow maintainers to request that their update be pushed to stable before the automatic approval job runs, if it already meets the time-in-testing requirements.


=====Client Changes=====
<references/>


* Add --stablekarma, --unstablekarma, and --disable-autokarma client arguments
====Build F-18 collection packages for all language translators====
* Fix a bug in using `bodhi --push-build=` on multi-build updates
* Add a --bodhi-url command-line option
* Instead of requiring only one argument with a comma separated list of updates, support several builds as several arguments.


=====API Changes=====
* 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>


* Remove our API pagination query limit of 1000
"Hi Fedora package maintainers
* Add a new 'author_group' field to each comment in our JSON API


=====Backend Changes=====
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.


* Add the new 'dist-fN-updates{-testing,}-pending' tags to builds so AutoQA can start testing them before they get pushed
Thank you so much.
* List security & critpath testing updates in our updates-testing digest emails
* Download and inject the pkgtags sqlite db into our repodata from the pkgdb (which will be utilized by `yum search`)
* Email the proventesters about stale unapproved critical path updates
* Update the bug titles for all security updates before pushing (since security bug titles frequently change after the update is submitted to reflect the CVE id)
* Improved sanity checking in the masher when resuming pushes
* Properly capture & log stderr from our mash subprocess
* Improved metrics report generator (soon to be integrated into the web interface)


=====Bugs & RFEs=====
noriko
Fedora Localization Project"


Please file and bug reports or enhancement requests here:
<references/>
<ref>https://fedorahosted.org/bodhi/newticket</ref>"


<references/>
====Fedora 18 Alpha to slip by another one week====


====Fedora 14 Beta Go/No-Go Meeting Wednesday, September 22, 2010 @ 21:00 UTC==== 
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
'''John Poelstra<ref>John Poelstra poelstra at redhat.com</ref> on Tue Sep 21 18:59:05 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000689.html</ref>,'''
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>


"Join us on irc.freenode.net #fedora-meeting for this important meeting.
"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>.  


'''Wednesday, September 22, 2010 @ 21:00 UTC (17:00 EDT/14:00 PDT)'''
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
will be pushed out by one week.


"Before each public release Development, QA, and Release Engineering  meet to determine if the release criteria are met for a particular  release. This meeting is called the: Go/No-Go Meeting."
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).


"Verifying that the Release criteria are met is the responsibility of the QA Team."
If you have an accepted blocker bug, please try to fix it
as soon as possible to help us with Fedora 18 Alpha release!"


For more details about this meeting see:
<references/>
<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>


In the meantime keep an eye on the Fedora 14 Beta Blocker list and help us get the testing matrix completed by testing.


<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=F14Beta&hide_resolved=1</ref>
=== Fedora Events ===
<ref>http://fedoraproject.org/wiki/Category:Fedora_14_Beta_RC_Test_Results</ref>"


<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 (Sept 2010 - November 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_Q3_.28Sept_2010_-_November_2010.29</ref>
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28September_2010_-_November_2010.29</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sep._2010_-_Nov._2010.29</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sept_2010_-_November_2010.29_2</ref>


<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 225: 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"