From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
 
(60 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:Pcalarco|Pascal Calarco]]
Contributing Writer: [[User:rashadul|Rashadul Islam]]


<references/>
<references/>


=== Fedora Announcements ===
===Breaking News of the Week and Month===


==== Outage: Server reboots - 2011-08-01 14:00 UTC ====
====[Guidelines Change] Changes to the Packaging Guidelines====  


Kevin Fenzi announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-July/002988.html</ref>:
* 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>


"There will be an outage starting at 2011-08-01 14:00 UTC, which will last
"A new section has been added to the SysV Initscripts section, discussing
approximately 2 hours.
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>


To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
---
or run:


date -d '2011-08-01 14:00 UTC'
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>


Reason for outage:
---


A number of servers are being upgraded and must be rebooted. Where possible,
The PHP Packaging guidelines have been updated to include guidance about
services should continue to be available during this outage, but users
when it is appropriate to have an explicit Requires on httpd & mod_php,
and maintainers may see short periods of instability or interruptions in some services.  
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>


===== Affected Services: =====
---


* Bodhi - https://admin.fedoraproject.org/updates/
A new section on Macros has been added to the Packaging Guidelines,
* Buildsystem - http://koji.fedoraproject.org/
covering Packaging of Additional RPM Macros.
* Docs - http://docs.fedoraproject.org/
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>
* Email system
* Fedora Account System - https://admin.fedoraproject.org/accounts/
* Fedora Community - https://admin.fedoraproject.org/community/
* Fedora Hosted - https://fedorahosted.org/
* Fedora People - http://fedorapeople.org/
* Main Website - http://fedoraproject.org/
* Package Database - https://admin.fedoraproject.org/pkgdb/
* Smolt - http://smolts.org/
* Spins - http://spins.fedoraproject.org/
* Start - http://start.fedoraproject.org/
* Torrent - http://torrent.fedoraproject.org/
* Wiki - http://fedoraproject.org/wiki/


===== Unaffected Services: =====
---


* BFO - http://boot.fedoraproject.org/
A new section on the Documentation= field in systemd unit files (F17+)
* GIT / Source Control
has been added.
* DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
* Fedora Insight - https://insight.fedoraproject.org/
* Mirror List - https://mirrors.fedoraproject.org/
* Mirror Manager - https://admin.fedoraproject.org/mirrormanager/


Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2900
---


===== Contact Information: =====
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>


Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above."
---


<references/>
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 15 for IBM System z 64bit official release ====
---


Dan Horák announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-July/002987.html</ref>:
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).


"It's been a longer time since the Fedora 15 release for the primary
'''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.'''
architectures than we expected, but here we are.  


As today, the Fedora IBM System z (s390x) Secondary Arch team proudly
As a reminder: The Fedora Packaging Guidelines are living documents! If
presents the Fedora 15 for IBM System z 64bit official release!
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>"


And without further ado, here the links to the actual release:
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>


http://secondary.fedoraproject.org/pub/fedora-secondary/releases/15/Fedora/s390x/
<references/>
http://secondary.fedoraproject.org/pub/fedora-secondary/releases/15/Everything/s390x/os/


and obviously on all mirrors that mirror the secondary arch content.
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 


The first directory contains the normal installation trees as well as
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
one DVD ISO with the complete release.
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>


Everything as usual contains, well, everything. :)
"Greetings! (...or perhaps I should say.... bonjour!)


For Fedora 14 we have collected a couple of example config files,
I'd like to share a few reminders and announcements regarding the
kickstart examples and a nice README here<ref>http://secondary.fedoraproject.org/pub/alt/spins/S390/</ref>
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.


beware that currently the content there is outdated, but most of the
If you are planning to attend FUDCon and need a travel subsidy to do so,
information should be still valid. We're working on fixing that over the
the ticketing system is now open for those requests.  Requests will be
next weeks.
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.


Additional information about know issues, the current progress and state
To place a subsidy request, please follow these steps:
for future release, where and how the team can be reached and just
anything else IBM System z on Fedora related can be found here<ref>http://fedoraproject.org/wiki/Architectures/s390x/15</ref> for architecture specific release notes and here<ref>http://fedoraproject.org/wiki/Architectures/s390x</ref> for more general s390x notes.


Thanks go out to everyone involved in making this happen!
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>


Your Fedora/s390x Maintainers
Additionally, a few notes regarding the hotel in Paris:


--
There are other events in Paris during this time period; most notably,
Dan Horák, RHCE
our first day of FUDCon will be taking place at the Open World Forum
Senior Software Engineer, BaseOS
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. :)


Red Hat Czech s.r.o., Purkyňova 99, 612 45 Brno"
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October.
However, this rate will expire at the end of August, and any remaining
rooms in our block will expire.


For instructions on booking your hotel, please read the Lodging/Hotel
section of the FUDCon: Paris wiki:
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
<references/>
<references/>


=== Fedora Development News ===
====Fedora Infrastructure announces status.fedoraproject.org==== 
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.
 
'''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/>


==== evolution-data-server soname version bump for rawhide/Fedora 16 next week ====
* 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>


Milan Crha announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000823.html</ref>:
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


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


I just want to let you know that evolution-data-server 3.1.5 release, which is about to happen the next week, on August 15th, +/-, changes
The site auto reloads every minute, and also provides a rss feed at
soname versions for almost everything it provides, namely libedataserver, libecal, libedatacal, libebook, libedatabook.
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.  


Anything depending on it would be rebuild on both branches against newer eds, when its update will be done. I will rebuild all to which I have
If you run into a problem or issue that is not reflected at
commit rights by the end of the week, after the release.
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.


Bye,
As with everything in Fedora Infrastructure, this application is open
source. Source is available from:
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
and is released under a '''GPLv2+ license'''.


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


==== Fedora 16 Alpha to slip by one week ====
====Beats are open!====


[[User:Rbergero|Robyn Bergeron]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000822.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>


"Today at the Go/No-Go meeting it was decided to slip the Alpha by one
"The Release Notes beats for Fedora 18 are now open:
week[1]. Minutes follow below.
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


There are numerous unresolved blocker bugs at this time[2], requiring
If you're looking for a way to dip your toes in the water, so to
the creation of an RC4 once these blockers are resolved.
speak, writing a beat is a great way to get started. If you're a
regular, don't forget about the checkBeat program:
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>


As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be
As a reminder, the wiki drafts of beats are due on 12 September."
pushed out by one week.


We will proceed with having the F16 Alpha readiness meeting tomorrow,
<references/>
2011-08-11, as previously announced on the Logistics mailing list.  We
will have another F16 Alpha Blocker Bug meeting this Friday.


The adjustments to the F16 schedule will be done (very late) tonight,
=== Fedora Development News ===
and published to the Schedule wiki page[3].
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.


Thanks for your patience. We will be meeting again next Wednesday for
'''Acceptable Types of Announcements'''
another Go/No-Go meeting.
* Policy or process changes that affect developers.
* Infrastructure changes that affect developers.
* Tools changes that affect developers.
* Schedule changes
* Freeze reminders


-Robyn
'''Unacceptable Types of Announcements'''
 
* Periodic automated reports (violates the INFREQUENT rule)
[1] Logs:
* Discussion
http://meetbot.fedoraproject.org/fedora-meeting/2011-08-10/f16_alpha_gono-go_meeting.2011-08-10-21.00.log.html
* Anything else not mentioned above
    Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2011-08-10/f16_alpha_gono-go_meeting.2011-08-10-21.00.html
 
[2] https://fedoraproject.org/wiki/Current_Release_Blockers
 
[3] https://fedoraproject.org/wiki/Releases/16/Schedule
 
 
<code>
===========================================
#fedora-meeting: F16 Alpha Go/No-Go Meeting
===========================================
 
Meeting started by rbergeron at 21:00:26 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2011-08-10/f16_alpha_gono-go_meeting.2011-08-10-21.00.log.html
 
 
Meeting summary
---------------
* present: spot, codeblock, dgilmore, pjones, athmane, cebbert,
  jsmith-mobile, adamw  (rbergeron, 21:03:42)
* Go/No-Go Meeting  (rbergeron, 21:04:07)
  * the Purpose of the Go/No-Go is to gather yay/nay's from Release
    Engineering, QA, and devel on whether or not what we have put
    together is ready for release and meets the release criteria.
    (rbergeron, 21:05:28)
  * LINK: https://fedoraproject.org/wiki/Go_No_Go_Meeting  (adamw,
    21:06:17)
  * LINK: https://fedoraproject.org/wiki/Current_Release_Blockers <--
    that one I know by heart, though.  (rbergeron, 21:06:42)
 
* Proposed Blockers  (rbergeron, 21:09:50)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=729563
    (rbergeron, 21:10:04)
  * clumens has an updates image (linked in BZ) for people to try out.
    (rbergeron, 21:12:33)
  * AGREED: : #729563, NTH Alpha, consider adding criterion for selinux
    must be enabled by default later.  (rbergeron, 21:14:39)
 
* http://bugzilla.redhat.com/show_bug.cgi?id=729500  (rbergeron,
  21:15:04)
  * Error while installing updates on Fedora 16 Alpha RC3  (rbergeron,
    21:15:20)
  * AGREED: revisit #729563 at Blocker meeting friday, try to get more
    testers. PLEASE TEST THIS ONE AND TRY TO DUPLICATE, FOLKS!
    (rbergeron, 21:17:34)
 
* https://bugzilla.redhat.com/show_bug.cgi?id=729528  (rbergeron,
  21:17:53)
  * #729528 - Unable to configure events in reporter to forward in
    anaconda for F-16-Alpha-RC3  (rbergeron, 21:18:09)
  * AGREED: #729528 Alpha Blocker, per criterion of installer must be
    able to report failures to BZ, wiht appropriate info included.
    (rbergeron, 21:22:19)
 
* http://bugzilla.redhat.com/show_bug.cgi?id=729537  (rbergeron,
  21:22:53)
  * 729537 - Anaconda cannot report crashes in text mode in F16 Alpha
    RC3 due to missing report-cli  (rbergeron, 21:23:14)
  * AGREED: 729537 Alpha Blocker, per criterion of installer must be
    able to report failures to BZ, with appropriate info included.
    (rbergeron, 21:25:32)
 
* https://bugzilla.redhat.com/show_bug.cgi?id=728707  (rbergeron,
  21:25:48)
  * 728707 - on package upgrade RPM is removing empty directories
    accidentally  (rbergeron, 21:26:02)
  * AGREED: 728707 is a blocker under 'must be able to install updates'
    criterion - this constitutes not installing updates properly
    (adamw, 21:33:36)
 
* https://bugzilla.redhat.com/show_bug.cgi?id=729600  (adamw, 21:37:37)
  * LINK:
   
http://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Guide/Making_USB_Media-UNIX_Linux.html
    (jlk, 21:47:30)
  * AGREED: 729600 not blocker or nth, installing from a dd'ed DVD iso
    is expected to require extra configuration. documentation should be
    improved to outline the steps required  (adamw, 21:56:27)
 
* https://bugzilla.redhat.com/show_bug.cgi?id=728863  (adamw, 21:57:30)
 
* go/no-go vote  (adamw, 22:00:30)
  * AGREED: Fedora 16 Alpha is no-go at this time  (adamw, 22:01:32)
  * ACTION: rbergeron will take care of updating the schedules  (adamw,
    22:02:04)
 
* open floor  (adamw, 22:03:40)
 
Meeting ended at 22:05:08 UTC.
 
Action Items
------------
* rbergeron will take care of updating the schedules
 
Action Items, by person
-----------------------
* rbergeron
  * rbergeron will take care of updating the schedules
* **UNASSIGNED**
  * (none)
 
 
People Present (lines said)
---------------------------
* adamw (167)
* rbergeron (73)
* pjones (66)
* jlk (49)
* dgilmore (36)
* Viking_Alpha (35)
* tflink (32)
* clumens (22)
* nirik (20)
* zodbot (6)
* spot (4)
* cebbert (3)
* athmane (2)
* CodeBlock (2)
* jsmith-mobile (1)
* tk009 (1)
* cwickert (1)
* jsmith (1)
 
Generated by `MeetBot`_ 0.1.4
 
.. _`MeetBot`: http://wiki.debian.org/MeetBot"
</code>


<references/>
<references/>


==== New hardened build support (coming) in F16 ====
====New bodhi release in production====


Adam Jackson announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000821.html</ref>:
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>


"tl;dr version: If you have a security-sensitive package, and wish to
"A new release of Bodhi has just been deployed to production.
enable some gcc-level hardening features with a modest performance
<ref>https://admin.fedoraproject.org/updates</ref>
impact, you will soon be able to enable them (nearly) automagically by
rebuilding with this line in your spec file:


<code>%define _hardened_build 1</code>
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>


Now for the details.
Major changes in bodhi 0.9.2
---------------------------------


* 1: what are we trying to do?
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)


There are three somewhat-overlapping build features in play here.  The
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
first one is called "relro", which instructs the linker to emit some
relocations in a special segment that can be marked read-only after
relocation processing is finished but before you call into main().  Or
in English: more things that you've asked to be const, will actually be
const.  This on its own is quite cheap, and so it has been enabled
globally as of redhat-rpm-config-9.1.0-13.fc16.


By default, not all symbols are resolved that early in program
* The submitter of an update can no longer effect the karma (Till Maas)
execution.  In particular, functions are resolved lazily the first time
they're called.  This makes startup faster, and since not all functions
are actually called in typical program execution, usually makes total
execution time faster.  However, if all symbols were resolved early, the
relro feature could do a better job, and virtually all relocations could
be made read-only.  The '-z now' flag to the linker makes this happen,
and an app so linked is said to be "Full RELRO" instead of "Partial RELRO".


Finally, applications may be built as position-independent executables,
* Fix duplicate status change email notifications. (Till Maas)
by passing -fPIC or -fPIE at build time and -pie at link time.  This
allows the runtime linker to randomize the placement of the executable
at runtime, which makes it more difficult for an attacker to guess the
address of writeable memory.


* 2: how do we go about doing it?
* Mention age of updates in testing digest mails (Till Maas)


The non-PIE parts of this are trivial, just pass the appropriate flags
* Support e-mail threading in notification e-mails (Till Maas)
to the linker and you're done.  PIE is more difficult, both at build
time and at link time.  Although both -fPIC and -fPIE produce
position-independent code at the assembly level, -fPIE will (at least on
amd64) produce relocation types that are only valid in an executable.
This means you can't just say -fPIE in CFLAGS: your libraries will fail
to link.  (PIC objects in a PIE executable are fine; PIE objects in a
PIC library are not.  When in doubt, -fPIC.)


Likewise, at link time, the -pie and -shared options are mutually
* Add X-Bodhi mail headers (Till Maas)
exclusive.  ld.gold will simply refuse to execute if you specify both.
ld.bfd will (afaict) let whichever one comes last win, and if that
happens to be -pie when you're building a shared library it will fail to
link because it won't be able to find a _start symbol.


All of this is only an issue because most build systems don't let you
* Gracefully handle private bugs (Cole Robinson)
say different CFLAGS or LDFLAGS for shared libraries and executables.  Sigh.


So instead, we'll teach gcc to figure it out.  To do this we'll use the
* Set the default request for new updates to 'testing' in the web form
-specs flag to pass some rewrite rules to the compiler driver.  At
compile time, if we don't see -fPIC or -fPIE on the command line, we'll
add -fPIC.  At link time, if we don't see -shared, we'll add -pie.  This
way we build relocatable objects that are always suitable for either
type of final link object, and we'll only attempt to build a PIE if we
know we're not building a shared library.  Victory!


* 3: what does this mean for you?
* 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.


The link-time bit of the last paragraph required a bit of gcc magic to
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
get right (previously specs rules could only add strings to the command
line of the program to invoke; they could not rewrite gcc's notion of
which flags had been passed in the first place).  Thanks to a patch from
Jakub Jelinek, this is now fixed in gcc-4.6.1-7.fc16, and will be in gcc
4.7 and later.  As a result, %defined _hardened_build 1 will not work
until that gcc update has gone through.


Once that's done (and redhat-rpm-config-9.1.0-15.fc16 has been gone
through updates), if you're using a %configure-style spec file, defining
the magic macro is all you have to do.  The rpm macros will notice the
macro, and put the right magic into CFLAGS and LDFLAGS, and everything
is great and wonderful.


If you're _not_ using %configure, then you have to do whatever is
Full list of changes since 0.8.7
conventional for your build system to get CFLAGS and LDFLAGS inherited
--------------------------------
properly.   For CFLAGS, this will be $RPM_OPT_FLAGS or %{optflags} as
before.  As of rpm-4.9.1-3.fc16, you will be able to say $RPM_LD_FLAGS
for the corresponding LDFLAGS values.  Until then, there is no such
shell variable, but you can get the same effect from
%{?__global_ldflags}.  Yes, that's ugly, sorry.


If you are the owner of one of the packages listed here<ref>https://fedoraproject.org/wiki/User:Kevin/DRAFT_When_to_use_PIE_compiler_flags</ref>
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579


Then I have locally built (though not extensively tested) your package
Luke Macken (25):
with the appropriate specfile modifications, and the results do indeed
      Convert our tags_url to a byte string before passing it to urlgrabber.
appear to be fully hardened.  If you would like to handle the rebuilds
      Add a script to detect when older builds become the 'latest' in stable
yourself, please let me know. Otherwise I will submit them myself once
      Update our test suite to reproduce ticket [ticket:683]
the relevant updates have gone through.
      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'


If you've made it to the end, congratulations.  Please let me know if
Mathieu Bridon (6):
there are any issues, or any questions I can answer.  In particular if
      Have bodhi-init create all the tables
the performance impact of these flags is excessive for you, there are
      masher: Fix the comparison
some ways it can be mitigated that are out of scope for this particular
      masher: Reuse variable
email.
      setup: Fix the Turbogears version requirement
 
      Don't version control auto-generated files
- ajax
      setup: Add missing dependencies


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


Till Maas (8):
      Add X-Bodhi mail headers
      Support e-mail threading in notification e-mails
      Mention age of updates in testing digest mails
      Use format string instead of string concatenation
      Import exceptions from sqlite3
      Remove files used by mercurial
      model.py: Change karma from Submitter to 0
      Fix notification on automatic status change"


<references/>
<references/>


==== Fedora 16 Alpha Go/No-Go Meeting, Wednesday, August 10 @ 17:00 EDT  ====
====Build F-18 collection packages for all language translators====


[[User:Rbergero|Bobyn Bergeron]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000819.html</ref>:
* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref>
* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref>


"Join us on irc.freenode.net #fedora-meeting for this important meeting.
"Hi Fedora package maintainers


Wednesday, August 10, 2011 @21:00 UTC (17:00 EDT/14:00 PDT)
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.


"Before each public release Development, QA and Release Engineering
Thank you so much.
meet to determine if the release criteria are met for a particular
release. This meeting is called the: Go/No-Go Meeting."


"Verifying that the Release criteria are met is the responsibility of
noriko
the QA Team."
Fedora Localization Project"
 
For more details about this meeting<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
 
In the meantime, keep an eye on the Fedora 16 Alpha Blocker list:
 
https://fedoraproject.org/wiki/Current_Release_Blockers
 
-Robyn"


<references/>
<references/>


==== FUDCon EMEA travel subsidies are open ====
====Fedora 18 Alpha to slip by another one week====
 
Christoph Wickert announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000818.html</ref>:
 
"Hi there,
 
If you are planning to attend FUDCon Milan 2011 and need travel subsidies, the ticket system is now open. If you need sponsoring, please


1. register<ref>https://fedoraproject.org/wiki/FUDCon:Milan_2011#Pre-registration</ref>
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
2. put an X in the $$$ column
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>
3. make a funding request in the the FUDCon ticket tracker<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>  
4. General instructions about sponsoring<ref>http://fedoraproject.org/wiki/Sponsoring_event_attendees</ref>  


Funding requests without a ticket will not be considered. We have a limited budget and will work hard to fund as many people as possible.
"Today at Go/No-Go meeting it was decided to slip Fedora 18
We'll use these answers to help figure out budgeting for the event. We are making arrangements for attendees from other geographic regions to
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
encourage specific initiatives such as future FUDCon events, but preference may otherwise be given to people in EMEA.
full log is at <ref>http://bit.ly/PC16PF</ref>.  


The next subsidy meeting will be held on Tuesday, August 16th at 15:00 UTC in #fudcon-planning. Please show up in case the event organizers
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
have questions about your request.
will be pushed out by one week.


Regards,
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).


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


<references/>
<references/>


==== String Freeze 2011-08-02 ====


[[User:noriko|Noriko Mizumoto]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-August/000817.html</ref>:
=== Fedora Events ===
 
"Fedora Packagers
 
It is String Freeze date on 2011-08-02.
Fedora Localization team will soon start translating latest packages via
Transifex. Our goal is Fedora software translation to be 100% completed
as many languages as possible.
 
Please make sure that your latest POT file has been uploaded to
Transifex for translators.
If you think that you need to break the string freeze, then you should
ask for approval from the Fedora Localization Team prior to breaking the
freeze. Software string freeze policy can be found at<ref>https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy</ref>
 
Thank you so much for your support in advance.
 
Regards,
 
noriko
Fedora L10N"
 
==== Changes to the Packaging Guidelines  ==== 
[[User:Spot|Tom Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-July/000815.html</ref>:
 
"Here are the latest changes to the Fedora Packaging Guidelines:
 
---
 
Some rpm versions pass pathnames to the automatic filtering macros, so a
section has been added to the guidelines to help packagers deal with it<ref>https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Pathnames</ref>
 
---
 
For a while, Fedora considered mono packages to be
architecture-specific, and installed assemblies to %{_libdir}. However,
after discussions with upstream, we now consider mono packages to be
architecture (and platform) independent. This means that mono packages
should be correctly installed into the GAC in /usr/lib or installed into
/usr/lib/PACKAGENAME.
 
As a notable exception, any ELF binary libraries generated in a mono
package must be correctly installed into %{_libdir}, because these files
are architecture-specific.
 
Also, even though we consider mono packages to be architecture
independent, they must not be marked as "noarch". Although the
assemblies are the same, the files may differ due to strings referring
to the build architecture.<ref>https://fedoraproject.org/wiki/Packaging:Mono#File_Locations</ref>
 
---
 
It was decided that gnome shell extension packages should have the
prefix gnome-shell-extension (with no "s" on the end).<ref>https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28gnome_shell_extensions.29</ref>
 
---
 
The section in the Fedora Packaging Guidelines concerning libexecdir has
been improved and expanded<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir</ref>
 
---
 
The Fedora Java Packaging Guidelines have been updated to reflect the
latest macros for Maven 3.<ref>https://fedoraproject.org/wiki/Packaging:Java</ref>
 
---
 
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
 
Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar,
Stanislav Ochotnicky, 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
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.
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>


Thanks,
====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>


~spot"
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>
 
<references/>
 
=== Fedora Events ===
 
The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning.
Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding.
In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
 
====Upcoming Events (June - August 2011)====
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29</ref>
* Central & South America (LATAM): <ref>http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_2</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_3</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_4</ref>


<references/>
<references/>
Line 577: 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"