devel-announce April 2012

devel-announce@lists.fedoraproject.org

9 participants
14 discussions

Fedora 17 for Power Alpha Announcement
by David Aquilina 10 Apr '12

10 Apr '12

Time flies like the wind... As it's already time again for another Fedora release on Power, this time for Fedora 17 Alpha. We've hit a couple of bumps along the road to the Alpha, but at long last we're finally at a state where we're ready to release it to the public. Due to lack of developer time and hardware, Apple hardware support is at this point completely untested. Especially with the switch to grub2 we rely on community feedback and participation to make this work for this release. So if you have the hardware and want it to work, patches welcome! :) The bits are available from your closest mirror: https://mirrors.fedoraproject.org/publiclist/Fedora/17-Alpha/ppc64/ More details about this Alpha release can be found here: https://fedoraproject.org/wiki/Fedora_17_Alpha_PPC_release_notes One of our focuses in the lead up to the beta of Fedora 17 for Power will be addressing architecture-specific packaging issues in as many packages as possible. If you own a package in Fedora which has ExclusiveArch or ExcludeArch set, please take a moment to verify that the architectures you've excluded or are exclusive to are still correct and sane. I want to thank everyone involved in making this happen once more. Many Fedora packagers and contributors have again stepped up and helped fix issues that only appeared on Power hardware. Moreover the whole Fedora Secondary Arch team has been doing a fantastic job to get us to where we are now, especially considering that we had a complete switch of builders and hub hardware, mass rebuild and a hub failure along the way! As usual, you can reach the whole team on the #fedora-ppc IRC channel on FreeNode and via our email list: https://admin.fedoraproject.org/mailman/listinfo/ppc And we have our Secondary Arch wiki with (decently) updated information: http://fedoraproject.org/wiki/Architectures/PowerPC For Phil, Karsten, and the entire Fedora for Power team, Thanks & regards, David -- David Aquilina Release Engineer Red Hat, Inc.

1 0

Outage: fedorahosted.org - 2012-04-09 21:00 UTC
by Kevin Fenzi 09 Apr '12

09 Apr '12

Outage: fedorahosted.org - 2012-04-09 21:00 UTC There will be an outage starting at 2012-04-09 UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2012-04-09 21:00 UTC' Reason for outage: We are moving fedorahosted services to a new cluster backed by glusterfs. This should allow us to distribute load easier across nodes and provide better response time, as well as allowing us to reboot servers without downtime moving forward. Affected Services: Fedora Hosted - https://fedorahosted.org/ Unaffected Services: Ask Fedora - http://ask.fedoraproject.org/ BFO - http://boot.fedoraproject.org/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Insight - https://insight.fedoraproject.org/ Fedora People - http://fedorapeople.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ QA Services Secondary Architectures Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/3229 Contact Information: Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above.

1 1

F17 Beta to slip by an additional week.
by Robyn Bergeron 05 Apr '12

05 Apr '12

At the Go/No-Go meeting it was decided to slip the Beta by an additional week[1]. Minutes follow below. Though the QA team was able to get through all validation testing, it was found that preupgrade was not functioning at an acceptable level, thus becoming an additional blocker which prevents us from shipping RC3, and necessitating the creation of an RC4. As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week. Beta will now be looking at an expected release of 2012-04-17, and F17 GA is now scheduled for 2012-05-22. This is the second one-week slip of beta. Adjustments to the full F17 schedule have been completed and now reflect the above Beta and GA dates, and high-level milestones have been updated as well on the Schedule wiki page[3]. We will be meeting again next Wednesday for another Go/No-Go meeting (2012-04-11.) All hail our QA pals and the anacondanistas for their dedication (and many, many others as well). -Robyn [1] Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-05/gono-go_contin… Logs: http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-05/gono-go_contin… [2] http://fedoraproject.org/wiki/Current_Release_Blockers [3] http://fedoraproject.org/wiki/Schedule Minutes: ============================================================= #fedora-meeting-1: Go/No Go Continuation, Round Two, RC3, F17 ============================================================= Meeting started by rbergeron at 15:00:38 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-05/gono-go_contin… . Meeting summary --------------- * Who's up (rbergeron, 15:01:03) * Test Results (rbergeron, 15:11:31) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_17_Beta_RC3_Install (rbergeron, 15:11:37) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_17_Beta_RC3_Base (rbergeron, 15:12:11) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_17_Beta_RC3_Desktop (rbergeron, 15:12:22) * AGREED: we are okay with the level of test coverage as of now on RC3 (rbergeron, 15:16:31) * Blockers (rbergeron, 15:16:41) * https://bugzilla.redhat.com/show_bug.cgi?id=741594 (adamw, 15:18:19) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=741594#c14 (Martix, 15:18:54) * AGREED: 741594 does not hit any of the criteria and the cited scenarios are not significant enough to worry about delaying the beta (adamw, 15:29:18) * https://bugzilla.redhat.com/show_bug.cgi?id=810226 (adamw, 15:31:12) * LINK: http://patchwork.freedesktop.org/patch/9198/ (adamw, 15:40:55) * https://bugzilla.redhat.com/show_bug.cgi?id=810161 (adamw, 15:48:57) * AGREED: 810161 is rejected as a blocker because the impact is minor (it's essentially a cosmetic bug, desktop is still usable), also it only hits one specific virt configuration so it can at least be worked around. accepted as NTH and will be commonbugs'ed if we ship with it (adamw, 16:13:56) * https://bugzilla.redhat.com/show_bug.cgi?id=810289 (adamw, 16:14:24) * AGREED: #810289 is rejected as a blocker on the basis that we've never actually checked for low space on upgrade (and hence have implictly never considered it a blocking issue). anaconda will just try to upgrade and explode. so this isn't in fact a regression compared to earlier releases, and we don't have a specific requirement for a low space check in criteria or anywhere else. accepted as NTH (adamw, 16:31:38) * https://bugzilla.redhat.com/show_bug.cgi?id=810136 (adamw, 16:31:59) * AGREED: 810136 turns out to be a dupe of 810005, moving discussion (adamw, 19:45:37) * https://bugzilla.redhat.com/show_bug.cgi?id=810005 (adamw, 19:45:42) * AGREED: 810005 is accepted as a blocker per criterion "The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation (from any official install medium) of the previous stable Fedora release, either via preupgrade or by booting to the installer manually. The upgraded system must meet all release criteria". the known workaround has too many limitations to be considered 'good enough' (adamw, 19:53:23) * Go or no-go? (rbergeron, 19:54:12) * we have a blocker. (rbergeron, 19:54:27) * qa votes no-go, as do various others from engineering, fesco, pm (rbergeron, 19:55:18) * AGREED: we are no-go on F17 Beta RC3 sadly (adamw, 19:58:27) * ACTION: rbergeron to update schedule.... again (rbergeron, 19:58:55) * ACTION: rbergero to send slip mail (rbergeron, 20:00:19) * ACTION: tflink to do blocker meeting mail following slip notice (rbergeron, 20:00:38) * ACTION: qa heroes of awesome to get some rest plz (rbergeron, 20:03:09) * ACTION: adamw to get a hole in one (rbergeron, 20:03:23) * we will re-convene tomorrow or monday (adamw, 20:08:56) Meeting ended at 20:08:59 UTC. Action Items ------------ * rbergeron to update schedule.... again * rbergero to send slip mail * tflink to do blocker meeting mail following slip notice * qa heroes of awesome to get some rest plz * adamw to get a hole in one Action Items, by person ----------------------- * adamw * adamw to get a hole in one * rbergeron * rbergeron to update schedule.... again * tflink * tflink to do blocker meeting mail following slip notice * **UNASSIGNED** * rbergero to send slip mail * qa heroes of awesome to get some rest plz People Present (lines said) --------------------------- * adamw (360) EDITOR'S NOTE: Dude! It's like 360 degrees of adamw :) * wwoods (99) * rbergeron (91) * tflink (56) * bcl (54) * nirik (49) * Kevin_Kofler (37) * ajax (32) * Martix (19) * rdieter_work (8) * zodbot (6) * cpuobsessed (5) * pjones (5) * ianweller (4) * kalev (3) * spot (3) * satellit_laptop (1) * pschindl_ (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Fedora 17 Beta Go/No-Go Meeting, Wednesday, April 4, @17:00 Eastern
by Robyn Bergeron 02 Apr '12

02 Apr '12

Please join us on irc.freenode.net in #fedora-meeting-1 for this important meeting. This will be Round 2 of this meeting for the Beta release of F17. Wednesday, April 4, 2012 @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: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 17 Beta Blocker list: http://fedoraproject.org/wiki/Current_Release_Blockers Ongoing Beta RC test results can be seen here: https://fedoraproject.org/wiki/Category:Fedora_17_Beta_RC_Test_Results See you there, Wednesday, in #fedora-meeting-1 (1, 1, !!!111, make a note of it!) -Robyn

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce April 2012