From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
 
(284 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===
There were no announcements on the announce@lists.fedoraproject.org last week aside from FWN 215 availability.


===Fedora Development News===
====[Guidelines Change] Changes to the Packaging Guidelines====   
====[Guidelines Change] Changes to the Packaging Guidelines 04/09 - 02/10====   
[[User:Spot|Tom "spot" Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000584.html</ref> the changes to the Packaging Guidelines 04/09 - 02/10. He said, "It has been almost a year since we announced changes to the Packaging
Guidelines, so this will be a long list. In the future, we'll try to be more timely in writing up changes and announcing them to the Fedora Community.


Here are the list of changes to the Fedora Packaging Guidelines:
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
When selecting which source to download from upstream and use in a Fedora package, the smallest available (and Fedora compatible) source
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
should be used:<ref>https://fedoraproject.org/wiki/Packaging/SourceURL#Referencing_Source</ref>


The Fortran Packaging Guidelines have been updated: <ref>https://fedoraproject.org/wiki/Packaging:Fortran</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 Ant Sample Spec in the Java Packaging Guidelines has been corrected:<ref>https://fedoraproject.org/wiki/Packaging/Java</ref>
---


The R Packaging Guidelines have been updated:<ref>https://fedoraproject.org/wiki/Packaging:R</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 Scrollkeeper scriptlets were removed from the Packaging Guidelines:<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scrollkeeper</ref>
---


The Python Packaging Guidelines were significantly rewritten including
The PHP Packaging guidelines have been updated to include guidance about
changes to address:
when it is appropriate to have an explicit Requires on httpd & mod_php,
* Python 3
how to handle explicit Requires on PHP extensions, and how to handle a
* PyGTK2 and Numpy
Requires for a minimum PHP version.
<ref>https://fedoraproject.org/wiki/Packaging:Python</ref>
<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>


Dos2unix is no longer forbidden when removing DOS line breaks in a file:<ref>https://fedoraproject.org/wiki/Packaging/Guidelines#Rpmlint_Errors</ref>
---


The Packaging Guidelines now contain a lengthy explanation of why Bundled Libraries are not permitted in Fedora: <ref>https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries</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>


The Packaging Guideline section on dealing with pre-built libraries has been improved:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-built_binaries_or_libraries</ref>
---


Fedora packages no longer need to explicitly define a BuildRoot, as RPM now always defines one:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#BuildRoot_tag</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>


The Fedora Packaging Guidelines now contain more information on how to deal with Conflicting Files in scenarios involving "common names": <ref>https://fedoraproject.org/wiki/Packaging:Conflicts#Conflicting_Files</ref>
---


There are now Packaging Guidelines for Wordpress Plugins:<ref>https://fedoraproject.org/wiki/Packaging:WordPress_plugin_packaging_guidelines</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>


There are now Packaging Guidelines for Globus Toolkit components: <ref>https://fedoraproject.org/wiki/Packaging:Globus</ref>
---


Since RPM now detects pkgconfig dependencies in all Fedora releases, it is no longer necessary for Fedora packages with .pc files to explicitly Require: pkgconfig :<ref>https://fedoraproject.org/wiki/PackagingGuidelines#Pkgconfig_Files</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>


Fedora packages should contain man pages for all included binaries and scripts, and if not present, Fedora packagers should work with upstream to add them: <ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Man_pages</ref>
---


There are now Packaging Guidelines for MPI packages: <ref>https://fedoraproject.org/wiki/Packaging:MPI</ref>
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).


There are now Packaging Guidelines for proper usage of Environment Modules: <ref>https://fedoraproject.org/wiki/Packaging:EnvironmentModules</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.'''


There are now Packaging Guidelines for proper usage of Alternatives: <ref>https://fedoraproject.org/wiki/Packaging:Alternatives</ref>
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>"


The Packaging Guidelines now have a section covering how to properly handle filtering of Automatic Provides and Requires:<ref>https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering</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>


The GConf scriptlets have been rewritten to use macros (and be much simpler): <ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GConf</ref>
<references/>


The Guidelines concerning RPath have been clarified:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath</ref>
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 


The Guidelines concerning File and Directory ownership have been clarified:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Ownership</ref>
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>


The Emacs Packaging Guidelines have been changed:<ref>https://fedoraproject.org/wiki/Packaging:Emacs</ref>
"Greetings! (...or perhaps I should say.... bonjour!)


The PHP Packaging Guidelines have been changed:<ref>https://fedoraproject.org/wiki/Packaging:PHP</ref>
I'd like to share a few reminders and announcements regarding the
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.


The Fedora Packaging Guidelines now contain a section on dealing with Buildtime Macros in Source RPMS: <ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Source_RPM_Buildtime_Macros</ref>
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.


A clarification note has been added to the SourceURL section, reminding Fedora packagers to use "downloads.sourceforge.net": <ref>https://fedoraproject.org/wiki/Packaging:SourceURL#Sourceforge.net</ref>
To place a subsidy request, please follow these steps:


These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC) and ratified by FESCo.
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>


Many thanks to Pierre-Yves Chibon, Remi Collet, Mattias Ellert, Adam Jackson, Jussi Lehtola, David Malcolm, Till Maas, Bill Nottingham, Orcan Ogetbil, Rahul Sundaram, Alexey Torkhov, Jonathan Underwood, Ivana Varekova, Ian Weller, Chris Weyl and all of the members of the FPC and FESCo, for assisting in drafting, refining, and passing these guidelines.
Additionally, a few notes regarding the hotel in Paris:


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>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
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/>


====Build F-13 collection packages for all language translators====   
====Fedora Infrastructure announces status.fedoraproject.org====   
[[User:Noriko|Noriko Mizumoto]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000583.html</ref> to the Fedora package maintainers, "This is kind reminder asking you to rebuild your package with latest translation. Localization team has been translating for updated and/or newly added strings since the String is frozen (2010-02-09). To allow translators to review and correct their latest translation in UI, this is essential. This is different from 'Rebuild all translated packages for Beta', this is added entry since Fedora 12<ref>http://poelstra.fedorapeople.org/schedules/f-13/f-13-devel-tasks.html</ref>.
 
* 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.


"Build F-13 collection packages for all language translators" is expected between 2010-03-03 to 2010-03-05. Please make sure your build
The site auto reloads every minute, and also provides a rss feed at
is completed by 2010-03-05, so that a live image to be composed on 2010-03-05.
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.  


The packages to be built are:
If you run into a problem or issue that is not reflected at
* ABRT » master
status.fedoraproject.org, please do report it to us in #fedora-admin on
* anaconda » master
irc.freenode.net or via ticket at
* audit-viewer » tip
<ref>https://fedorahosted.org/fedora-infrastructure/newticket</ref>
* authconfig » tip
We update the site status information manually so we need to be aware
* chkconfig » master
of the issue in order to keep the site accurate.
* comps » HEAD
 
* desktop-backgrounds » HEAD
As with everything in Fedora Infrastructure, this application is open
* desktop-effects » master
source. Source is available from:
* firstboot » master
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
* im-chooser » trunk
and is released under a '''GPLv2+ license'''.
* initscripts » master
 
* iok » trunk
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
* kexec-tools » HEAD
issues with outages in our infrastructure affecting status reporting. "
* libuser » tip
* liveusb-creator » master
* mlocate » tip
* multimedia-menus » master
* newt » master
* passwd » tip
* policycoreutils » HEAD
* pykickstart » master
* python-meh » master
* readahead » master
* redhat-menus » HEAD
* setroubleshoot » tip-framework
* setroubleshoot » tip-plugins
* setuptool » master
* smolt » master
* smolt » master-smoon
* sos » trunk
* switchdesk » HEAD
* system-config-audit » tip
* system-config-bind » tip
* system-config-boot » master
* system-config-date » master-docs
* system-config-date » master
* system-config-date » master-timezones
* system-config-display » master
* system-config-firewall » master
* system-config-httpd » tip
* system-config-kdump » new
* system-config-keyboard » trunk
* system-config-kickstart » master
* system-config-language » trunk
* system-config-lvm » master
* system-config-netboot » trunk
* system-config-network » master
* system-config-nfs » master
* system-config-nfs » master-docs
* system-config-printer » master
* system-config-rootpassword » trunk
* system-config-samba » master
* system-config-samba » master-docs
* system-config-services » master
* system-config-services » master-docs
* system-config-users » master
* system-config-users » master-docs
* system-switch-java » tip
* system-switch-mail » HEAD
* usermode » tip"


<references/>
<references/>


====Fedora 13 Alpha Go/No-Go Meeting====
====Beats are open!====
=====Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 at 19:00 UTC (14:00 EST)===== 
 
[[User:Adamwill|Adam Williamson]] announced as an important note<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "...we are rescheduling the Go/No-Go meeting for Fedora 13 Alpha. Previously scheduled for 2010-02-25 01:00 UTC, it is now scheduled for 2010-02-25 19:00 UTC (14:00 EST, 11:00 PST). This delay is to give sufficient time for the QA team to test the expected RC3 build.
* 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>


The original announcement, with the new time, is reproduced below for reference.
As a reminder, the wiki drafts of beats are due on 12 September."


Join us on irc.freenode.net #fedora-meeting for this important meeting.
<references/>
Thursday, February 25, 2010 @ 19:00 UTC (14:00 EST).


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


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


For more details about this important meeting see: <ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


<references/>
<references/>


=====Feodra 13 Alpha slip by one week=====
====New bodhi release in production====
[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000581.html</ref> on the basis of the announcement<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "Today at the go / no-go meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-02-25/fedora-meeting.2010-02-25-18.59.log.html</ref> we decided to slip the Alpha by one week.  This slip is needed to verify blocker bug fixes and validate new builds of software necessary to fix those bugs.  We are confident that the fixes we have are valid, however we do not have enough time to prove them valid.  We will spend the next few days doing that validation.  In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be pushed unless they are fixing a release blocking issue.  Once we've validated all the fixes we will do more frequent pushes to 13 stable.
 
At this time we are not adjusting later milestone dates, as with no frozen rawhide we are not taking away any developer time." 
* 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
---------------------------------


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


=====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC (2010-03-03 @ 20:00 EST)===== 
Luke Macken (25):
[[User:Adamwill|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000582.html</ref>, "Join us on irc.freenode.net #fedora-meeting for this important meeting. This is Thursday, March 4, 2010 @ 01:00 UTC, which makes it '''WEDNESDAY EVENING''' in North America: 20:00 EST, 17:00 PST.
      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'


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


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


For more details about this important meeting see:<ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"
Till Maas (8):
      Add X-Bodhi mail headers
      Support e-mail threading in notification e-mails
      Mention age of updates in testing digest mails
      Use format string instead of string concatenation
      Import exceptions from sqlite3
      Remove files used by mercurial
      model.py: Change karma from Submitter to 0
      Fix notification on automatic status change"


<references/>
<references/>


=====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC Recap=====
====Build F-18 collection packages for all language translators====
[[/User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000585.html</ref> the meeting summary, "Representatives from Fedora QA, Rel-Eng and Development met on IRC to review determine whether the Fedora 13 Alpha release criteria<ref>https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria</ref> have been met.  The team agreed that the Alpha criteria have been met, and to proceed with releasing F-13-Alpha-RC4.  For additional details, please refer to the attached minutes.


* '''fedora-meeting: F-13-Alpha engineering readiness meeting'''
* 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>


Meeting started by jlaska at 01:00:03 UTC. The full logs are available at <ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-03-04/f-13-alpha-eng-readiness.2010-03-04-01.00.log.html</ref>.
"Hi Fedora package maintainers


'''Meeting summary'''
Please build and push your package with latest translation file (e.g.
* Waiting for critical mass . (jlaska, 01:00:25)
pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31.
* adamw representing QA  (jlaska, 01:03:02)
Your packages with latest translation will be composed into test live
* Oxf13 representing Rel-Eng  (jlaska, 01:03:07)
image on 3-Sep Monday. Then various language translators worldwide will
* Oxf13 wearing the notting mask, representing Devel  (jlaska,01:03:21)
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.


'''Why are we here?'''  (jlaska, 01:03:44)
Thank you so much.
* The purpose is to decide whether the alpha has met the release criteria  (jlaska, 01:03:49)
* LINK:<ref>https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria</ref>(jlaska, 01:03:54)


'''Go or No Go?'''  (jlaska, 01:04:57)
noriko
* all desktop and install validation tests for alpha point have been run  (jlaska, 01:08:36)
Fedora Localization Project"
* only bug blocking alpha is <ref>https://bugzilla.redhat.com/show_bug.cgi?id=567346</ref> - we have decided it's okay as it has a usable workaround, so we should take it off the list  (jlaska, 01:08:52)
* ACTION: Decided that bug#567346 can be removed from F13Alpha(jlaska, 01:13:10)
* LINK: <ref>https://fedoraproject.org/wiki/Common_F13_bugs#yum-langpacks</ref>(jlaska, 01:15:09)
* IDEA: should KDE Live image be respun to address kpackagekit issue?(jlaska, 01:16:44)
* source DVD is 5.0G  (Oxf13, 01:20:49)
* IDEA: need to determine how to handle source ISO's for F-13-Final(jlaska, 01:24:01)
* ACTION: several remaining CommonBugs? needing documentation(jlaska, 01:25:15)
* AGREED: QA + Rel-Eng + Devel* agreed to proceed with releasing F-13-Alpha-RC4 as the Alpha  (jlaska, 01:26:09)


'''What's next?'''  (jlaska, 01:26:38)
<references/>
* ACTION: adamw + jlaska to document remaining CommonBugs? issues(jlaska, 01:28:44)
* LINK: <ref>http://fedoraproject.org/wiki/Fedora_12_Alpha_Announcement</ref>   (Oxf13, 01:32:06)
* ACTION: jlaska - send out the meeting minutes to devel-announce@test-announce@ and logistics@  (jlaska, 01:33:34)
* expect to be fully staged for mirrors by tomorrow  (Oxf13, 01:34:16)


'''Open Discussion'''  (jlaska, 01:34:45)
====Fedora 18 Alpha to slip by another one week====


Meeting ended at 01:36:45 UTC.
* 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>


'''Action Items'''
"Today at Go/No-Go meeting it was decided to slip Fedora 18
* Decided that bug#567346 can be removed from F13Alpha
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
* several remaining CommonBugs? needing documentation
full log is at <ref>http://bit.ly/PC16PF</ref>.
* adamw + jlaska to document remaining CommonBugs? issues
* jlaska - send out the meeting minutes to devel-announce@test-announce@ and logistics@


'''Action Items, by person'''
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
* adamw
will be pushed out by one week.
  * adamw + jlaska to document remaining CommonBugs? issues
 
* jlaska
The next Go/No-Go meeting is on Thursday Sep 06, same place
  * adamw + jlaska to document remaining CommonBugs? issues
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
  * jlaska - send out the meeting minutes to devel-announce@
#fedora-meeting).
    test-announce@ and logistics@
 
* **UNASSIGNED**
If you have an accepted blocker bug, please try to fix it
  * Decided that bug#567346 can be removed from F13Alpha
as soon as possible to help us with Fedora 18 Alpha release!"
  * several remaining CommonBugs? needing documentation


'''People Present (lines said)'''
* jlaska (67)
* Oxf13 (41)
* adamw (32)
* juhp (10)
* poelcat (6)
* rhe (4)
* zodbot (4)
* skvidal (2)
<references/>
<references/>


===Fedora Events===
Fedora events are the source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!


====Upcoming Events (March 2010 to May 2010)====
=== Fedora Events ===
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29</ref>
 
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q4_.28March_2010_-_May_2010.29</ref>
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.
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_2</ref>
 
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_3</ref>
====Upcoming Events (September 2012 - November 2012)====
* '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref>
* '''Central & South America (LATAM)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29</ref>
* '''Europe, Middle East, and Africa (EMEA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2</ref>
* '''India, Asia, Australia (India/APJ)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3</ref>
 
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>


<references/>
<references/>
Line 273: Line 366:


====Additional information====
====Additional information====
* '''[[Reimbursements]] -- reimbursement guidelines.'''
* [[Reimbursements]] -- reimbursement guidelines.
* '''[[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).'''
* [[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).
* '''[[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.'''
* [[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.
* [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
* [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
* [[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

  • 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]

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

  • 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"

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"

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!"


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]

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