From Fedora Project Wiki

< FWN‎ | Beats

Revision as of 17:53, 22 September 2010 by Rashadul (talk | contribs)

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Rashadul Islam

Fedora Announcement News

The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1]

FUDCon LATAM 2011 bids

Paul W. Frields[1] on Fri Sep 17 17:53:31 UTC 2010 announced[2],

"The bid period for the next Fedora Users and Developers Conference (FUDCon) in the LATAM region is open, and will remain open for a few more weeks. The bid process for FUDCon is outlined here: [3]

Two bids have already been received for FUDCon at this point, and the process will continue soon with an award, a budget, and an open and transparent planning process: [4] [5]

Bids will continue to be accepted until *September 30, 2010*. Bids must be published on the Fedora wiki, and a URL for the bid sent to the fudcon-planning list: [6]

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

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

FUDCon is held several times each year around the globe as part of Fedora's premier events strategy. You can read more about Fedora events here: [7]

Please remove 'announce-list' from any replies to this message, since they'll be removed from its moderation queue. Thank you!"

Fedora Development News

The fedora development news list is intended to be a low traffic announce-only list for Fedora development.[1]

  • 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

We have reached Fedora 14 Feature Complete

By John Poelstra

John Poelstra [1] on Wed Sep 15 22:46:50 UTC 2010 announced[2],

"Thank you to all the feature owners and developers for all their hard work to make Fedora 14 the best Fedora release yet. We are almost to the end!

As a follow-up to last week's reminder [3]

ALL feature pages are now expected to be at 100% completion. The following features are not listed at 100% complete and are being sent to FESCo ([4]) for re-evaluation for inclusion in the Fedora 14 feature list if they remain incomplete:

[5] (yes, a mere technicality at 99% done) [6] [7] [8] [9] [10] "

David Malcolm

To continue the thread, David Malcolm </ref>David Malcolm dmalcolm at redhat.comCite error: Closing </ref> missing for <ref> tag,

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

> https://fedoraproject.org/wiki/Features/MemoryDebuggingTools

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

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

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

Sorry about this (got bogged down in RHEL work)"


Fedora 14 Beta Change Deadline Reached 2010-09-14

John Poelstra[1] on Wed Sep 15 22:59:53 UTC 2010 announced[2],

"As a reminder, we have reached the Beta Change Deadline for Fedora 14.

"At the change deadlines for Alpha and Beta, pushes to the branched development repository (e.g. /pub/fedora/linux/development/14), are suspended until the Release Candidate has been successfully tested and staging has started to the mirrors."

More details are located here: [3]"

Fedora 14 Beta Release Date at Risk

John Poelstra[1] on Thu Sep 16 22:31:14 UTC 2010 announced[2],

"We have missed the Fedora 14 Beta RC compose scheduled today because of unresolved Fedora 14 Beta Blocker bugs.

[3](NEW or ASSIGNED)

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

bodhi v0.7.9 deployed

Luke Macken[1] on Mon Sep 20 18:19:06 UTC 2010 announced[2],

"A new version of bodhi has just hit production. This release contains a number of bugfixes and enhancements. [3]

Web UI Changes
  • Improved editing functionality
   - Only unpush edited updates when builds are altered
   - Make a note in the comments of which builds were added/removed
  • Allow people to revert their karma vote more than once
  • Add mouseover tooltips to the update status with more details
  • Prevent different versions of a package from being added to the same update
  • Handle more types of bugzilla auto-linking in comments (ex: rhbz#1234)
  • Link to the newer update in the obsoleted ones
  • Link to gitweb instead of viewvc
  • Set default (un)stable karma values if re-enabled
  • Anonymous karma has never effected karma, so we now mark them as being ignored in the interface to make it obvious
  • Get the 'suggest reboot' flag working again
  • Allow non-critpath updates to be pushed to stable after meeting our critpath requirements
  • Allow maintainers to request that their update be pushed to stable before the automatic approval job runs, if it already meets the time-in-testing requirements.
Client Changes
  • Add --stablekarma, --unstablekarma, and --disable-autokarma client arguments
  • Fix a bug in using bodhi --push-build= on multi-build updates
  • Add a --bodhi-url command-line option
  • Instead of requiring only one argument with a comma separated list of updates, support several builds as several arguments.
API Changes
  • Remove our API pagination query limit of 1000
  • Add a new 'author_group' field to each comment in our JSON API
Backend Changes
  • Add the new 'dist-fN-updates{-testing,}-pending' tags to builds so AutoQA can start testing them before they get pushed
  • List security & critpath testing updates in our updates-testing digest emails
  • Download and inject the pkgtags sqlite db into our repodata from the pkgdb (which will be utilized by yum search)
  • Email the proventesters about stale unapproved critical path updates
  • Update the bug titles for all security updates before pushing (since security bug titles frequently change after the update is submitted to reflect the CVE id)
  • Improved sanity checking in the masher when resuming pushes
  • Properly capture & log stderr from our mash subprocess
  • Improved metrics report generator (soon to be integrated into the web interface)
Bugs & RFEs

Please file and bug reports or enhancement requests here: [4]"

Fedora 14 Beta Go/No-Go Meeting Wednesday, September 22, 2010 @ 21:00 UTC

John Poelstra[1] on Tue Sep 21 18:59:05 UTC 2010 announced[2],

"Join us on irc.freenode.net #fedora-meeting for this important meeting.

Wednesday, September 22, 2010 @ 21:00 UTC (17:00 EDT/14:00 PDT)

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

"Verifying that the Release criteria are met is the responsibility of the QA Team."

For more details about this meeting see: [3]

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

[4] [5]"

Fedora Events

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 (Sept 2010 - November 2010)

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

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.