FWN/Beats/Announcements

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements, development announcements and Events.

Contributing Writer: Rashadul Islam

Fedora Announcement News

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

Fedora Development News

Fedora 14 Alpha Go/No-Go Meeting

Fedora 14 Alpha Go/No-Go Meeting August 19, 2010 @ 12:00 AM UTC

John Poelstra on Tue Aug 17 23:59:56 UTC 2010 announced,

Where

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

When

Thursday, August 19, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT--Wednesday, August 18, 2010* )

Details

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

Fedora 14 Alpha Blocker list

In the meantime keep an eye on the Fedora 14 Alpha Blocker list (which is currently EMPTY!) "

Fedora 14 Alpha Go/No-Go Meeting: 2010-08-12 @ 12:00 UTC Recap

Adam Williamson on Thu Aug 12 02:10:41 UTC 2010 announced,

"The first Fedora 14 Alpha Go/No-Go Meeting was held 2010-08-12 at 12:00 UTC (so evening of 2010-08-11 in North America). The outcome of the meeting was a decision to slip the Alpha release by one week due to one bug agreed to be a definite blocker:

"xdriver=vesa is not honored"

and one bug that is potentially a blocker, pending more data:

"hang at start of X11 on fresh install from DVD"

All other bugs considered were agreed not to be release blockers and removed from the list.

A slip announcement will be sent with more details on the slip specifically. We aim to build an RC4 tomorrow afternoon American time (2010-08-12) with the fix for 623129 (and possibly fixes for a couple of other bugs we decided were not blockers but would be nice to fix), and continue to research 596985 to decide if it is a blocker. If we decide it is, an RC5 build will be required.

The automated summary of the meeting can be found here:

The full log of the meeting can be found here:

Thanks to all for attending and providing input."

Want to help pick the F14 Release Slogan?

Robyn Bergeron Robyn on Wed Aug 11 20:40:12 UTC 2010 announced,

"We need a slogan for the F14 release. A release slogan is a short call-to-action that fits the artwork theme from Design, found at . (F13's slogan was "Rock it.")

If you are interested in suggesting ideas for the release slogan, please take a look at the Release Slogan SOP, and the criteria for selection, at . The slogan must be:

• short (1-3 words)
• a call to action
• positive

It should reinforce that Fedora helps the user achieve something great. It should also reflect some of ideas and themes found in the release artwork, and, if possible, also touch upon the Four Foundations ().

Please put your slogan ideas here:

The deadline for submissions is Tuesday, August 17, at 21:00 UTC, which is our next Marketing meeting(). We'll be discussing submissions there, and then the FPL, Mo Duffy, and the Marketing team lead (that's me!) will take that input and select the final slogan on Wednesday, August 18.

Let me know if you have any questions, comments, or concerns -- and let the wiki table know if you have any ideas!"

One week slip of Fedora 14 schedule

Jared K. Smith on Thu Aug 12 01:57:40 UTC 2010 announced,

"Today we held our readiness meeting for the Alpha release of Fedora 14. As you may know, this is a meeting with representatives from the Development, Release Engineering, and Quality Assurance teams. In these meetings, we evaluate the list of blocker bugs and give a "go" or "no go" signal on the state of the Fedora release.

You can read the minutes of the meeting here, but in short the decision was made that the release has not passed its release criteria. When this happens, the entire release schedule is slipped by a week, and we work to get things in better shape for the next meeting. We'll get the schedule updated in the next day or so, but in general this means that our general availability date for Fedora 14 has now gone from October 26th to November 2nd.

During composition of any further release candidates, the Fedora Release Engineering and Quality Assurance teams plan to be quite conservative in the updates they pull into the release candidates, so that we don't inadvertently create more blocker bugs. I'd also like to thank those who have really pushed hard to try to get the Alpha into shape. In particular, the Release Engineering team put in a lot of extra hours to compose our release candidates, and the QA team did a fantastic job of testing the release candidates and knocking out as many blocker bugs as possible.

While I regret the fact that the schedule has slipped, I'm confident it was the right decision to ensure that Fedora 14 is a rock-solid release."

155 more python packages need to be rebuilt for Python 2.7

Nils Philippsen on Wed Aug 11 19:26:56 UTC 2010 announced,

"a lot of packages were rebuilt for Python 2.7 recently, but unfortunately they've turned out to be not all that needed rebuilding. Essentially, all packages that contain .py files that aren't below /usr/lib(64)/python need to be rebuilt so that their respective pre-built .pyc/.pyo files are built with the new Python version.

If the packages aren't rebuilt, python will either attempt to rebuild the .pyc/.pyo files (and fail due to SELinux policy) during runtime (if run as root) or the program will take longer to startup because the python interpreter needs to parse the .py files everytime (and can't just use the respective .pyc/.pyo files since they're invalid).

The reason why this hasn't been noticed/why those packages haven't been covered in the mass rebuild is because they don't require "python(abi)" (which was used to find out which packages to rebuild) even though the contained .pyc/.pyo files clearly do. This is because the pythondeps.sh used by rpmbuild only adds that dependency to packages which have modules in the standard paths.

Thanks to Kalev Lember who wrote a script identifying the affected packages. Using its output, Dave Malcolm has just mass-filed bugs against the packages which we could identify and he's looking to get these rebuilt en-masse as well. Owners or comaintainers still would need to file update requests so the packages actually end up where the users can get them ;-). For this purpose, I've attached two lists to this mail: one listing the affected packages and their owners and comaintainers, the other listing the affected packages each person owns or comaintains.

Please file updates when your packages have been rebuilt and nag us if they don't get rebuilt in time, whatever that means.

Thanks for your help"

New bodhi release in production

Luke Macken on Thu Aug 12 21:57:28 UTC 2010 announced,

"A new version of bodhi has just hit production. This release contains a number of bugfixes and improvements, along with some important process changes.

ChangeLog

• Package update acceptance criteria compliance

      - Disable direct-to-stable pushes()

      - Minimum time-in-testing requirements

          - Every day bodhi will look for updates that have been in testing for N days (fedora: N=7, epel: N=14), and will add a comment notifying the maintainer that the update is now able to be pushed to stable.

          - When someone tries to push an update to stable, bodhi will look to see if it has the appropriate karma, or if it has been in testing for more than N days.

• Critical path update changes

  - Hide obsolete updates in our critpath view()

  - Disabled strict critical path procedures for EPEL
      - EPEL is back to the same process that it has always had

  - Add a new nagmail message for unapproved critical path updates

• RSS feed & grid of unapproved critical path updates
• RSS feed & grid of user-specific comments()

• Package-specific RSS feeds of updates()

• Add more links to the package-specific page

• Show 7 days worth of entries in our RSS feeds, as opposed to 20 entries ()
• Bodhi command-line client fixes

  - Output now goes to stdout, instead of stderr ()
    (Thanks to Till Maas)

  - Duplicate logging issue resolved()

  - Support using --critpath and --type with --testable

• Link to the submitter and release on the home page & testing list (Thanks to Till Maas)
• Made the suggest_reboot flag actually configurable

   ()

• Notify the security team when an update is edited and turned into a security update ()
• Only verify the autokarma thresholds if it is enabled (Thanks to Till Maas)
• Only touch bugs under the Fedora/EPEL Bugzilla products

   ()

• Prevent the masher from pushing obsolete updates
• Prevent obsolete updates from getting auto-promoted to stable
• Obsolete updates upon deletion, as opposed to destroying them.
• Added more unit tests (up to 122)
• Link up bug numbers and other URLs in the text of comments
• Document the newpackage update type in the bodhi-client commands

  ()

• Set bugs to MODIFIED upon submission

  ()

• Added a bodhi --push-request={stable,testing} command to improve our releng updates push workflow
• A new /updates/releases JSON API and python-fedora BodhiClient.get_releases() method for AutoQA
• Have the build auto-completion widget query candidate builds from koji, as opposed to looking in /mnt/koji/packages

   ()

Bugs & RFEs

Please file and bug reports or enhancement requests here:"

Outage: PHX2 network outage - 2010-08-15 01:00 UTC

Mike McGrath on Fri Aug 13 00:12:20 UTC 2010 announced,

"There will be an outage starting at 2010-08-15 01:00 UTC, which will last approximately 4 hours.

To convert UTC to your local time, take a look at or run: date -d '2010-08-15 01:00 UTC'

Reason for outage

Network work is being done in our primary hosting facility. Some services may be offline during this time. It is possible nothing will go offline.

Affected Services

• Bodhi -
• Buildsystem -
• CVS / Source Control
• Email system
• Fedora Account System -
• Fedora Community -
• Fedora Hosted -
• Fedora People -
• Fedora Talk -
• Mirror Manager -
• Package Database -
• Smolt -
• Translation Services -
• Wiki -

Unaffected Services

• BFO -
• DNS - ns1.fedoraproject.org, ns2.fedoraproject.org</ref>
• Docs -
• Main Website -
• Mirror List -
• Spins -
• Start -
• Torrent -

Ticket Link

The link is at

Contact Information

Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."

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 (June 2010 - August 2010)

• North America (NA)
• Central & South America (LATAM)
• Europe, Middle East, and Africa (EMEA)
• India, Asia, Australia (India/APJ)

Past Events

Archive of Past Fedora Events

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.