Welcoming New Fedora Program Manager Robyn Bergeron
Jared Smith made an announcement in his blog [1] about some upcoming personnel changes in Fedora. I wanted to make a specific announcement to the Fedora lists as well. Through the end of 2010 and a little bit beyond, I will be working along side Robyn Bergeron to transition my official Fedora responsibilities to her. This will include getting the Fedora 15 team schedules into shape, feature wrangling, bugzilla maintenance, and any number of other things. Robyn and I are committed to making this transition as smooth, complete and timely as we can, and expect the transition to be completed before the Fedora 15 feature submission deadline. Said a different way, if you've already been working with me on something, I'll continue to help you with it. For all new topics, please contact Robyn directly and we will work together as necessary to get them done. One of the luxuries of my position was keeping tabs on most of the teams in Fedora via their mailing lists. I won't have as much time for this going forward so I'll be scaling back the number of mailing lists I watch and contribute to. If I posted to a list in the past, please don't assume I'll automatically see your message there in the future. Also please don't hesitate to contact me directly if you feel the need to do so. Fedora, it's been a great ride. We've made great progress in the past three years and I'm thankful you let me be a part of it. Here's to wishing only the best to Robyn in her new role serving the Fedora community! John p.s. I'm still looking forward to and rooting for an on time Fedora 15 release. :) [1] http://www.jaredsmith.net/2010/11/10/changing-of-the-seasons/ ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: bugzilla bugzappers?
Frank Murphy said the following on 11/05/2010 12:47 AM Pacific Time: > On 05/11/10 07:27, Alexander Kurtakov wrote: > >> So what if I got 100 bug reports and didn't answered 10 bugs you will want to >> orphan my package? >> Welcome to the world without gtk, openjdk, eclipse-platform, kdelibs > > I think maybe it is meant more as "You have 100 bugs, 80 are not > acknowledged. > >> >> I can't see why can't we just admit - This is our best feel free to join us >> and help ?? (someone should find better wording) > > Is this not where added manpower can help? > At least a group who can be put together (existing?), > to look at reproducing\unable to bugs, to help the maintainers. > We've been trying to do that and get it off the ground for several years. It hasn't exactly flourished. DISCLAIMER: I'm not a package maintainer, but I have been involved with bug triage and was around the original effort to get Fedora bugzilla under control. I've always believed our core need is more maintainers if the goal is *fixing* and *resolving* bugs. Triage and debugging help only goes so far. It took several posts to devel-announce, personal emails, and weekly meetings during the roll up to Alpha, Beta, and Final, just to get information and help with ~20 blocker bugs. Addressing ~12,000 other open bugs will require something different. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2010-10-26) NEW TIME!
Kevin Fenzi said the following on 10/26/2010 12:36 PM Pacific Time: > Following is the list of topics that will be discussed in the FESCo > meeting tomorrow at 18:30UTC (2:30pm EDT) in #fedora-meeting on > irc.freenode.net. > > = Followups = > > #topic Updates policy > > #351 Create a policy for updates - status report on implementation > https://fedorahosted.org/fesco/ticket/351 > #382 Implementing Stable Release Vision > https://fedorahosted.org/fesco/ticket/382 > > * Need work on stats to see trends with new policy. > * Need to investigate a 'new features' repo setup. > * Need to look at enforcement > > = New business = > > #416 Set EOL Date For Fedora 12 > https://fedorahosted.org/fesco/ticket/416 > > * Since F14 was pushed out a week, should we move EOL for F12 as well? > > Elections coming up. > > * Note that FESCo (and FAMSCo and Board) elections are coming up. > > = Fedora Engineering Services tickets = > > https://fedorahosted.org/fedora-engineering-services/report/6 > > = Open Floor = > > For more complete details, please visit each individual ticket. The > report of the agenda items can be found at > https://fedorahosted.org/fesco/report/9 > > If you would like to add something to this agenda, you can reply to > this e-mail, file a new ticket at https://fedorahosted.org/fesco, > e-mail me directly, or bring it up at the end of the meeting, during > the open floor topic. Note that added topics may be deferred until > the following meeting. > > kevin > We have some Fedora 15 features too. https://fedoraproject.org/wiki/Category:FeatureReadyForFesco John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Final Release Declared GOLD
At the Fedora 14 Final Go/No-Go meeting today, the Fedora 14 Final Release was declared GOLD and ready for release on November 2, 2010. Thank you to everyone who made this on-time release possible! A reminder that the Fedora 14 Release Wide Readiness Meeting will take place on Thursday at 19:00 UTC (3 PM Eastern/ 12 PM Pacific) at irc.freenode.net #fedora-meeting https://fedoraproject.org/wiki/Release_Readiness_Meetings #fedora-meeting: Fedora 14 Final Release Go/No-Go Meeting http://fedoraproject.org/wiki/Go_No_Go_Meeting Meeting started by poelcat at 20:59:48 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2010-10-26/fedora-meeting.2010-10-26-20.59.log.html . Meeting summary --- * attendees: jlaska Oxf13 adamw poelcat dcantrell (and anyone on #fedora-meeting) (poelcat, 21:03:40) * Why are here and what does it mean? (poelcat, 21:03:51) * LINK: http://fedoraproject.org/wiki/Go_No_Go_Meeting (poelcat, 21:04:02) * Testing Status (poelcat, 21:05:10) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_RC1_Desktop (jlaska, 21:06:54) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_14_Final_RC1_Install (jlaska, 21:07:07) * https://bugzilla.redhat.com/show_bug.cgi?id=646437 (jlaska, 21:13:14) * test matrices are clear (poelcat, 21:16:24) * Releng (poelcat, 21:18:12) * fesco/devel/etc (poelcat, 21:18:52) * the source DVD is 5gigs, but it was oversize last release too (poelcat, 21:19:27) * GOLD or Not? (poelcat, 21:32:48) * AGREED: Fedora 14 is declared GOLD (poelcat, 21:34:55) * ACTION: add DVD size issue to common bugs (poelcat, 21:35:06) * open discussion (poelcat, 21:35:55) * ACTION: poelcat to send GOLD email to the lists w/ reminder for release readiness meeting on Thursday (poelcat, 21:39:06) Meeting ended at 21:39:19 UTC. Action Items * add DVD size issue to common bugs * poelcat to send GOLD email to the lists w/ reminder for release readiness meeting on Thursday Action Items, by person --- * poelcat * poelcat to send GOLD email to the lists w/ reminder for release readiness meeting on Thursday * **UNASSIGNED** * add DVD size issue to common bugs People Present (lines said) --- * poelcat (57) * adamw (55) * jlaska (25) * Oxf13 (22) * fenris02 (15) * stickster (7) * brunowolff (5) * dcantrell (3) * bcl (2) * zodbot (2) * cyberpear (1) * rbergeron (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 FINAL Go/No-Go Meeting Tuesday, October 26, 2010 @ 21:00 UTC
Join us on irc.freenode.net #fedora-meeting for this important meeting. Tuesday October 26, 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: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime keep an eye on the Fedora 14 Final Blocker list and help us finish filling out the test result matrices. https://bugzilla.redhat.com/showdependencytree.cgi?id=F14Blocker&hide_resolved=1 http://fedoraproject.org/wiki/Category:Fedora_14_Final_RC_Test_Results John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Final Blocker Bug Review Meeting TODAY @ 16:00 UTC (12 PM EDT)
When: TODAY, 2010-10-22 @ 16:00 UTC (12 PM EDT/9 AM PDT) Where: #fedora-bugzappers on irc.freenode.net We need to keep testing and resolving blocker bugs before the "Go/No-Go Meeting" on Tuesday, October 26, 2010. Discuss the open blocker bugs: http://bit.ly/aBqOcu 645283 [NEW --- - medium - assigned to dh...@redhat.com -Target: --- -] livecd-tools should create a /etc/mdadm.conf so that Intel BIOS RAID arrays get auto started [See dependency tree for bug 645283] 645293 [NEW --- - medium - assigned to kernel-ma...@redhat.com -Target: --- - CommonBugs] kernel does not recognize the partitions on an mdraid array (Intel BIOS RAID) [See dependency tree for bug 645293] 645606 [NEW --- - urgent - assigned to mcla...@redhat.com -Target: --- -] Plain background used instead of Laughlin [See dependency tree for bug 645606] ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
ZERO Days Remain to Fix Fedora 14 Blocker Bugs
We've made great progress on open Fedora 14 blocker bugs since last week. Thank you package owners for all your hard work! The list of bugs below are currently blocking the creation of the final release candidate (RC). These bugs must be addressed as soon as possible so that a solid release candidate can be provided to QA for testing on or before Thursday, October 21, 2010. 643967 :: NEW :: anaconda :: anaconda-maint-l...@redhat.com :: LiveCD fails to use BIOS RAID, DVD works :: https://bugzilla.redhat.com/show_bug.cgi?id=643967 Next steps ... * Continue discussing resolution options. Expecting recommendation from maintainer ASAP * If this issues is specific to Live installs using BIOS RAID AND a reasonable workaround exists, adding to Common_F14_bugs could be a satisfactory resolution 637319 :: ASSIGNED :: anaconda :: dleh...@redhat.com :: Anaconda stops at "checking storage devices" during preupgrade :: https://bugzilla.redhat.com/show_bug.cgi?id=637319 Next steps ... * Involves preupgrade failures when ntfs partitions are present * Need feedback and a fix from maintainer ASAP 643951 :: MODIFIED :: glibc :: sch...@redhat.com :: CVE-2010-3847 glibc: ld.so insecure handling of $ORIGIN in LD_AUDIT for setuid/setgid programs [fedora-all] :: https://bugzilla.redhat.com/show_bug.cgi?id=643951 Next steps ... * https://admin.fedoraproject.org/updates/glibc-2.12.90-17 is available and awaiting testing ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Final Change Deadline Reached
As a reminder, we have reached the Final Change Deadline for Fedora 14. https://fedoraproject.org/wiki/Change_deadlines "After the change deadlines for the Final release no more updates are made to the branched development repository (e.g. /pub/fedora/linux/development/14). The only exceptions are accepted blocker and "nice to have" bugs: https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process https://fedoraproject.org/wiki/QA:SOP_nth_bug_process All updates after this time are considered zero day updates of the release, and are pushed to the updates repository which is available on the public availability date. For example, the repository for Fedora 14 is /pub/fedora/linux/updates/14." John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Mon 18-Oct Mon 18-Oct Final Change Deadline Mon 18-Oct Mon 18-Oct Final Blocker Meeting (f14blocker)--Blocks RC Compose Mon 18-Oct Mon 18-Oct Submit Installer Builds for Final RC Compose Tue 02-Nov Tue 02-Nov Final (GA) Release -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Final Blocker Bug Review Meeting 2010-10-15 @ 16:00 UTC (12 PM EDT)
Andre Robatino said the following on 10/14/2010 03:32 PM Pacific Time: > On 10/14/2010 06:25 PM, John Poelstra wrote: >> When: Friday, 2010-10-08 @ 16:00 UTC (12 PM EDT/9 AM PDT) >> Where: #fedora-bugzappers on irc.freenode.net > > You mean 2010-10-15? I have the identical message to test-announce > waiting for moderation - could you resubmit it with the correct date? > Thanks. > > My mistake. Yes, the meeting is tomorrow, 2010-10-15 @ 16:00 UTC (12 PM EDT/9 AM PDT) John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Fedora 14 Final Blocker Bug Review Meeting 2010-10-15 @ 16:00 UTC (12 PM EDT)
When: Friday, 2010-10-15 @ 16:00 UTC (12 PM EDT/9 AM PDT) Where: #fedora-bugzappers on irc.freenode.net Open blocker bugs are here: http://bit.ly/aBqOcu Details of the current unresolved blocker bugs are here: http://lists.fedoraproject.org/pipermail/devel-announce/2010-October/000707.html Please join us tomorrow for this important meeting. John ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Final Blocker Bug Review Meeting 2010-10-15 @ 16:00 UTC (12 PM EDT)
When: Friday, 2010-10-08 @ 16:00 UTC (12 PM EDT/9 AM PDT) Where: #fedora-bugzappers on irc.freenode.net Open blocker bugs are here: http://bit.ly/aBqOcu Details of the current unresolved blocker bugs are here: http://lists.fedoraproject.org/pipermail/devel-announce/2010-October/000707.html Please join us tomorrow for this important meeting. John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
TWO Days Remain to Fix Fedora 14 Blocker Bugs
Hello Fedora 14 Blocker Bug Owners (all copied on this message), The list of bugs below are currently blocking the final release of Fedora 14. Updates fixing these bugs MUST be ready on Monday, 2010-10-18 (Final Change Deadline) or Release Engineering will be unable to create the Final Release Candidate on time, resulting in the possibility of a delayed release. We need your help *NOW*. As a maintainer, here is how you can help ... 639146 :: NEW :: xorg-x11-drv-intel :: a...@redhat.com :: Blank display (backlight on) after KMS initialization :: https://bugzilla.redhat.com/show_bug.cgi?id=639146 * next steps ... 1) Need to make final decision that this is not a blocker--is there anyone that believes this is a blocker? 2) Document on Common_F14_Bugs? 642358 :: NEW :: anaconda :: akozu...@redhat.com :: Up arrow tries to run gnome-screenshot :: https://bugzilla.redhat.com/show_bug.cgi?id=642358 * next steps ... 1) Patches pending review on anaconda-devel-list (unclear whether proposed patches fix all issues) 2) Build new anaconda containing approved patches 641846 :: NEW :: compiz :: adel.gadl...@gmail.com :: Panel applets (clock, workspace switcher, window selector, ...) randomly disappear :: https://bugzilla.redhat.com/show_bug.cgi?id=641846 * next steps ... 1) Reassigned to compiz, currently thinking is it is not a blocker bug 2) Document on Common_F14_Bugs? 641474 :: ASSIGNED :: lvm2 :: a...@redhat.com :: libdm does not present method to assign UUID after map creation :: https://bugzilla.redhat.com/show_bug.cgi?id=641474 * next steps ... 1) Maintainer needs to complete patch 2) Build and submit update by tomorrow 584328 :: ASSIGNED :: python-pyblock :: dleh...@redhat.com :: AttributeError: 'NoneType' object has no attribute 'name' :: https://bugzilla.redhat.com/show_bug.cgi?id=584328 * next steps ... 1) Patches reviewed, update needed when 641474 and 641476 are resolved 2) Build and submit update ASAP 642765 :: ASSIGNED :: anaconda :: dleh...@redhat.com :: AttributeError: 'NoneType' object has no attribute 'addChild' :: https://bugzilla.redhat.com/show_bug.cgi?id=642765 * next steps ... 1) Reporter confirms that fix works 2) Include fix in next anaconda build+update 641338 :: ASSIGNED :: qemu :: jfor...@redhat.com :: f14 qemu-kvm KDE guests boot very slowly :: https://bugzilla.redhat.com/show_bug.cgi?id=641338 * next steps ... 1) Determine whether issue is a release blocker (still unclear who is working this issue) 641476 :: MODIFIED :: kernel :: a...@redhat.com :: devicemapper UUID field cannot be assigned after map creation :: https://bugzilla.redhat.com/show_bug.cgi?id=641476 * next steps ... 1) Update pending, will be available for test soon 2) Verify bug and provide positive bodhi karma 635778 :: MODIFIED :: anaconda :: b...@redhat.com :: IndexError: list index out of range :: https://bugzilla.redhat.com/show_bug.cgi?id=635778 * next steps ... 1) Patches reviewed, committed and tested, awaiting next anaconda build+update 642483 :: MODIFIED :: anaconda :: dleh...@redhat.com :: Remove the 'Pre-release Software' Warning Screen :: https://bugzilla.redhat.com/show_bug.cgi?id=642483 * next steps ... 1) Patches reviewed and committed, awaiting next anaconda build+update 642763 :: MODIFIED :: kde-settings :: rdie...@math.unl.edu :: new user = blank/black wallpaper :: https://bugzilla.redhat.com/show_bug.cgi?id=642763 * next steps ... 1) Updates pending ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
THREE Days Remain to Fix Fedora 14 Blocker Bugs
Hello Fedora 14 Blocker Bug Owners (all copied on this message), The list of bugs below are currently blocking the final release of Fedora 14. Updates fixing these bugs MUST be ready on Monday, 2010-10-18 (Final Change Deadline) or Release Engineering will be unable to create the Final Release Candidate on time, resulting in the possibility of a delayed release. We need your help *NOW*. As a maintainer, here is how you can help ... 639146 :: NEW :: xorg-x11-drv-intel :: a...@redhat.com :: Blank display (backlight on) after KMS initialization :: https://bugzilla.redhat.com/show_bug.cgi?id=639146 * next steps ... 1) We still really really need feedback from maintainer (no feedback yet) 2) Request additional help from FESCo 642358 :: NEW :: anaconda :: akozu...@redhat.com :: Up arrow tries to run gnome-screenshot :: https://bugzilla.redhat.com/show_bug.cgi?id=642358 * next steps ... 1) Maintainer and reporter work to identify scope and root cause 2) Please update comments with plan of attack and ETA for resolution 641846 :: NEW :: gnome-panel :: rstr...@redhat.com :: Panel applets (clock, workspace switcher, window selector, ...) randomly disappear :: https://bugzilla.redhat.com/show_bug.cgi?id=641846 * next steps ... 1) Still awaiting maintainer feedback 2) If we don't hear a response in the comments by tomorrow we will remove as a blocker bug 641474 :: ASSIGNED :: lvm2 :: a...@redhat.com :: libdm does not present method to assign UUID after map creation :: https://bugzilla.redhat.com/show_bug.cgi?id=641474 * next steps ... 1) Waiting for new build from maintainer 641476 :: ASSIGNED :: kernel :: a...@redhat.com :: devicemapper UUID field cannot be assigned after map creation :: https://bugzilla.redhat.com/show_bug.cgi?id=641476 * next steps ... 1) Waiting for new build from maintainer 635778 :: ASSIGNED :: anaconda :: b...@redhat.com :: IndexError: list index out of range :: https://bugzilla.redhat.com/show_bug.cgi?id=635778 * next steps ... 1) Need feedback from maintainer 584328 :: ASSIGNED :: python-pyblock :: dleh...@redhat.com :: AttributeError: 'NoneType' object has no attribute 'name' :: https://bugzilla.redhat.com/show_bug.cgi?id=584328 * next steps ... 1) Patches under review, build and submit update (dependent on bug#641476 and bug#641474) 641338 :: ASSIGNED :: qemu :: jfor...@redhat.com :: f14 qemu-kvm KDE guests boot very slowly :: https://bugzilla.redhat.com/show_bug.cgi?id=641338 * next steps ... 1) Feedback in bug comments indicate the bug occurs in a non-default configuration, need confirmation from KDE-SIG before removing from list 642557 :: ASSIGNED :: pungi :: jkeat...@redhat.com :: after a split-media install, system fails to boot :: https://bugzilla.redhat.com/show_bug.cgi?id=642557 * next steps ... 1) Needs feedback from pungi maintainer 640766 :: ASSIGNED :: kernel :: linvi...@redhat.com :: b43legacy wlan0 fails DHCP requests :: https://bugzilla.redhat.com/show_bug.cgi?id=640766 * next steps ... 1) Maintainer and reporter work to resolve issue and submit update as soon as possible--no feedback to previous request 620635 :: ASSIGNED :: antlr3 :: xja...@fi.muni.cz :: antlr3 needs to be rebuilt against python 2.7 in F14 and devel :: https://bugzilla.redhat.com/show_bug.cgi?id=620635 * next steps ... 1) Verify proposed fix 2) Maintainer submits bodhi update(s) to correct issue 625894 :: ASSIGNED :: mesa :: airl...@redhat.com :: kwin freezes when changing related settings in systemsettings while compositing is active :: https://bugzilla.redhat.com/show_bug.cgi?id=625894 * next steps ... 1) Waiting on new mesa build and status update from airlied 642483 :: MODIFIED :: anaconda :: dleh...@redhat.com :: Remove the 'Pre-release Software' Warning Screen :: https://bugzilla.redhat.com/show_bug.cgi?id=642483 * next steps ... 1) Waiting on new anaconda build 642617 :: MODIFIED :: dracut :: har...@redhat.com :: Add cryptsetup-luks to dracut requirements again :: https://bugzilla.redhat.com/show_bug.cgi?id=642617 * next steps ... 1) Verify issue is fixed by proposed bodhi update (https://admin.fedoraproject.org/updates/dracut-006-3.fc14) ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Four Days to Fix Remaining Fedora 14 Blocker Bugs
Hello Fedora 14 Blocker Bug Owners (all copied on this message), The list of bugs below are currently blocking the final release of Fedora 14. These bugs MUST be fixed by this coming Monday, 2010-10-18 (Final Change Deadline) or Release Engineering will be unable to create the Final Release Candidate on time, resulting in the possibility of a delayed release. We need your help *NOW*. As a maintainer, here is how you can help ... --If you are the OWNER of one of these bugs, PLEASE add a comment to the bug ... 1) letting us know how things are going 2) what you are planning to do next 3) when you expect to complete the work--the sooner the better --If your bug is in MODIFIED, please make sure ... 1) a build and bodhi update have been submitted. 2) the bug status is set to ON_QA (bodhi should do this for you, but if not set it manually) 639146 :: NEW :: xorg-x11-drv-intel :: a...@redhat.com :: Blank display (backlight on) after KMS initialization :: https://bugzilla.redhat.com/show_bug.cgi?id=639146 * next steps ... 1) Really really need feedback from maintainer 629192 :: NEW :: pino :: rosset.fil...@gmail.com :: Twitter isn't functioning :: https://bugzilla.redhat.com/show_bug.cgi?id=629192 * next steps ... 1) add release note documenting the change (Fedora docs team), then ... 2) confirm release note and remove from F14Blocker list (anyone) 641846 :: NEW :: gnome-panel :: rstr...@redhat.com :: Panel applets (clock, workspace switcher, window selector, ...) randomly disappear :: https://bugzilla.redhat.com/show_bug.cgi?id=641846 * next steps ... 1) Decide whether bug meets the release criteria, early indications are "no" 2) Feedback from reporter and maintainer would be helpful 641474 :: ASSIGNED :: lvm2 :: a...@redhat.com :: libdm does not present method to assign UUID after map creation :: https://bugzilla.redhat.com/show_bug.cgi?id=641474 * next steps ... 1) Maintainer resolve issue and submit update as soon as possible 641476 :: ASSIGNED :: kernel :: a...@redhat.com :: devicemapper UUID field cannot be assigned after map creation :: https://bugzilla.redhat.com/show_bug.cgi?id=641476 * next steps ... 1) Maintainer resolve issue and submit update as soon as possible 641991 :: ASSIGNED :: xorg-x11-server :: a...@redhat.com :: Fedora 14 xorg qxl drv does not work with a RHEV-2.2 virtual machine :: https://bugzilla.redhat.com/show_bug.cgi?id=641991 * next steps ... 1) No release criteria impacting RHEV, will be removed from list 2) Feedback from reporter and maintainer would be helpful 641338 :: ASSIGNED :: qemu :: jfor...@redhat.com :: f14 qemu-kvm guests boot very slowly :: https://bugzilla.redhat.com/show_bug.cgi?id=641338 * next steps ... 1) Are KDE-only bugs considered a release blockers? If not, remove from list 2) Feedback from reporter and maintainer would be helpful 640766 :: ASSIGNED :: kernel :: linvi...@redhat.com :: b43legacy wlan0 fails DHCP requests :: https://bugzilla.redhat.com/show_bug.cgi?id=640766 * next steps ... 1) Maintainer and reporter work to resolve issue and submit update as soon as possible 584328 :: ASSIGNED :: python-pyblock :: pjo...@redhat.com :: AttributeError: 'NoneType' object has no attribute 'name' :: https://bugzilla.redhat.com/show_bug.cgi?id=584328 * next steps ... 1) Maintainer resolve issue and submit update as soon as possible 620635 :: ASSIGNED :: antlr3 :: xja...@fi.muni.cz :: antlr3 needs to be rebuilt against python 2.7 in F14 and devel :: https://bugzilla.redhat.com/show_bug.cgi?id=620635 * next steps ... 1) Need communication from maintainer OR a proven packager needs to take action ASAP 625894 :: MODIFIED :: mesa :: a...@redhat.com :: kwin freezes when changing related settings in systemsettings while compositing is active :: https://bugzilla.redhat.com/show_bug.cgi?id=625894 * next steps ... 1) Build new package and and make sure bodhi submission has been completed. 2) Change the bug status to ON_QA (bodhi should do this for you, but if not set it manually) ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Mon 11-Oct Mon 11-Oct Submit Installer Builds for Final TC Compose Mon 11-Oct Fri 15-Oct Daily Review & Notification of Open Final Blocker Bugs Fri 15-Oct Fri 15-Oct Final Blocker Meeting (f14blocker) #4 Mon 18-Oct Mon 18-Oct Final Change Deadline Mon 18-Oct Mon 18-Oct Final Blocker Meeting (f14blocker)--Blocks RC Compose Mon 18-Oct Mon 18-Oct Submit Installer Builds for Final RC Compose -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Review request: Nice-to-have bug process documentation proposal
Adam Williamson said the following on 10/07/2010 01:24 PM Pacific Time: >>> https://fedoraproject.org/wiki/User:Adamwill/QA:SOP_nth_process_nth_draft >>> is a proposed new page which covers the whole nice-to-have review process >>> much as the above proposed page covers the blocker review process. Thanks for doing all this Adam. The "Nice-to-have bug principles" guidelines feels a little mushy and subjective to me, though after thinking about it for a while I can't propose anything better--you've done a good job putting some structure around what they might be. And since they can't block the release they won't be able to cause that many problems. I suppose if NTH bugs were to ever become a big distraction from addressing blocker bugs we could re-evaluate. On the other hand it has taken us a *long* time to get to the place where we are today where churn in RC has been reduced to a bare minimum. I still subscribe to the theory (realizing some in Fedora don't) that every additional change adds a level of risk of delaying the release. So my hope is that by formalizing the NTH we aren't encouraging an increased amount of churn. I DO think this is an important section in the guidelines that will help cover this concern: "In general, nice-to-have bugs are usually bugs for which an update is not an optimal solution, and for which the fix is reasonably small and testable (this consideration becomes progressively more important as a release nears, so bugs may be downgraded from nice-to-have status late in the release process if it transpires that the fix is complex and hard to test)." Would it be overkill to put more explicit testing sign-off around NTH bugs? John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Blocker Bugs + Review Meeting 2010-10-08 @ 16:00 UTC (12 PM EST)
When: Friday, 2010-10-08 @ 16:00 UTC (12 PM EST) Where: #fedora-bugzappers on irc.freenode.net Here are the current bugs listed as blocking the final release of Fedora 14. We'll be discussing all of these to determine if they meet the criteria, should stay on the list, and are getting the attention they need. --If you are the OWNER of one of these bugs, PLEASE add a comment to the bug letting us know how things are going and what you are planning to do next. I --If your bug is in MODIFIED, please make sure a build and bodhi update have been submitted. If that's already happened, please change the bug to ON_QA so we can start test verificaiton. Thank you, John 599873 :: NEW :: valide :: bioinfornat...@gmail.com :: FTBFS valide-0.6.1-0.22.20103003svn511.fc14 :: https://bugzilla.redhat.com/show_bug.cgi?id=599873 635821 :: NEW :: anaconda :: anaconda-maint-l...@redhat.com :: Attempting to submit (scp or bugzilla) an exception report fails if networking not active :: https://bugzilla.redhat.com/show_bug.cgi?id=635821 640271 :: NEW :: install-guide :: da...@gnsa.us :: Fedora 14 installation guide references "RHEL" in examples :: https://bugzilla.redhat.com/show_bug.cgi?id=640271 640309 :: NEW :: install-guide :: da...@gnsa.us :: F-14 installation guide documents unsupported 'telnet' method :: https://bugzilla.redhat.com/show_bug.cgi?id=640309 635333 :: NEW :: libgdl :: debarshi@gmail.com :: libgdl needs to be downgraded to 2.30.x :: https://bugzilla.redhat.com/show_bug.cgi?id=635333 584328 :: NEW :: anaconda :: dleh...@redhat.com :: AttributeError: 'NoneType' object has no attribute 'name' :: https://bugzilla.redhat.com/show_bug.cgi?id=584328 639985 :: NEW :: python :: dmalc...@redhat.com :: Firefox crashes with xulrunner-python installed :: https://bugzilla.redhat.com/show_bug.cgi?id=639985 639393 :: NEW :: qtgpsc :: fab...@bernewireless.net :: Broken dependency: qtgpsc-0.2.3-6.fc12.x86_64 requires libgps.so.18()(64bit) :: https://bugzilla.redhat.com/show_bug.cgi?id=639393 617284 :: NEW :: distribution :: jfor...@redhat.com :: Fedora 14 Virtualization Target Blocker :: https://bugzilla.redhat.com/show_bug.cgi?id=617284 639395 :: NEW :: intellij-idea :: lkund...@v3.sk :: Broken dependency: intellij-idea-9.0.1.94.399-11.fc14.x86_64 requires jna-examples :: https://bugzilla.redhat.com/show_bug.cgi?id=639395 627388 :: NEW :: anaconda :: msi...@redhat.com :: VNC install ignores password :: https://bugzilla.redhat.com/show_bug.cgi?id=627388 639391 :: NEW :: spacewalk-certs-tools :: msu...@redhat.com :: Broken dependency: spacewalk-certs-tools-1.1.1-2.1.fc14.noarch requires spacewalk-backend-libs >= 0:0.8.28 :: https://bugzilla.redhat.com/show_bug.cgi?id=639391 628528 :: NEW :: xorg-x11-server :: peter.hutte...@redhat.com :: Emulating middle button doesn't work anymore. :: https://bugzilla.redhat.com/show_bug.cgi?id=628528 633298 :: NEW :: kde-settings :: rdie...@math.unl.edu :: Fedora 14 Blocker KDE Tracker :: https://bugzilla.redhat.com/show_bug.cgi?id=633298 629192 :: NEW :: pino :: rosset.fil...@gmail.com :: Twitter isn't functioning :: https://bugzilla.redhat.com/show_bug.cgi?id=629192 528022 :: ASSIGNED :: vbetool :: a...@redhat.com :: setroubleshoot: SELinux is preventing /usr/sbin/vbetool "mmap_zero" access on. :: https://bugzilla.redhat.com/show_bug.cgi?id=528022 620635 :: ASSIGNED :: antlr3 :: xja...@fi.muni.cz :: antlr3 needs to be rebuilt against python 2.7 in F14 and devel :: https://bugzilla.redhat.com/show_bug.cgi?id=620635 635778 :: MODIFIED :: anaconda :: b...@redhat.com :: IndexError: list index out of range :: https://bugzilla.redhat.com/show_bug.cgi?id=635778 627789 :: MODIFIED :: anaconda :: b...@redhat.com :: Error setting up repository - 16, Device busy :: https://bugzilla.redhat.com/show_bug.cgi?id=627789 637339 :: MODIFIED :: empathy :: bdpep...@gmail.com :: empathy 2.31.90-2 blocked by SELinux :: https://bugzilla.redhat.com/show_bug.cgi?id=637339 639730 :: MODIFIED :: empathy :: bdpep...@gmail.com :: Empathy fails to connect to Google Talk :: https://bugzilla.redhat.com/show_bug.cgi?id=639730 ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Review request: Nice-to-have bug process documentation proposal
Adam Williamson said the following on 10/06/2010 01:32 PM Pacific Time: > On Thu, 2010-09-23 at 12:58 +0100, Adam Williamson wrote: >> Hi, everyone. So we partly used the proposed new nice-to-have bug >> tracking system during the F14 Beta process, and it seemed to go well. >> In a quick burst of airport productivity, I've quickly written up a >> bunch of proposed new wiki pages and modifications to existing ones to >> document the nice-to-have process (and, incidentally, extend >> documentation of the blocker process, since we don't seem to have much >> of it beyond the blocker meeting SOP right now). All the pages can be >> found here: >> >> https://fedoraproject.org/wiki/Category:NTH_adjustment_drafts > > Thanks to James for his feedback on this. I haven't had much feedback > from anyone else. However, given that in practice everyone involved in > the release review process has been happy using the NTH system drafted > here so far, I intend to make the draft changes final (with > modifications to reflect James' feedback) by the end of the week, so if > you have any feedback you've been sitting on, now would be the perfect > time to send it :) Thanks everyone! Can you be more specific as to which page we are actually giving feedback on? There are five of them there and they almost all look the same. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Fri 08-Oct Fri 08-Oct Final Blocker Meeting (f14blocker) #3 Mon 11-Oct Mon 11-Oct Submit Installer Builds for Final TC Compose Mon 11-Oct Fri 15-Oct Daily Review & Notification of Open Final Blocker Bugs Fri 15-Oct Fri 15-Oct Final Blocker Meeting (f14blocker) #4 Mon 18-Oct Mon 18-Oct Submit Installer Builds for Final RC Compose Mon 18-Oct Mon 18-Oct Final Blocker Meeting (f14blocker)--Blocks RC Compose Mon 18-Oct Mon 18-Oct Final Change Deadline How has schedule worked out for your team during Fedora 14? The schedule is only as good as the information I receive so if you've noticed things that would work better for Fedora 15, please add them to https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Blocker Bug Meeting 2010-10-01 @ 16:00 UTC
When: Friday, 2010-10-01 @ 16:00 UTC (12 PM EDT) Where: #fedora-bugzappers on irc.freenode.net After a short break from getting the Beta release out the door, it is now time to start focusing on bugs that could block the final release. We can ship the final release of Fedora 14 on time if we remain vigilant and start knocking these bugs down now. Join us on Friday to starting reviewing what we've got. If you are the owner of these bugs, kindly update the comments with your feedback as to whether you believe it is a blocker and what your plans for fixing the bug are. If the bug is fixed and in MODIFIED, please make sure a Bodhi update has been submitted which should automatically transition the bug to ON_QA Do you have an issue you believe should be fixed before the Fedora 14 Alpha ships? Please consider the following criteria when escalating an issue: https://fedoraproject.org/wiki/Fedora_14_Final_Release_Criteria To promote a bug for consideration as a blocker, simply add 'F14blocker' to the "Blocks" field of the bug you are concerned about. Thank you! John 603386 :: NEW :: xorg-x11-drv-intel :: Adam Jackson :: Login screen no longer cross-fades from final plymouth screen on Intel graphics :: https://bugzilla.redhat.com/show_bug.cgi?id=603386 623956 :: NEW :: xorg-x11-drv-vesa :: Adam Jackson :: VESA driver fails in qemu/kvm machines, system hangs at X init :: https://bugzilla.redhat.com/show_bug.cgi?id=623956 636621 :: NEW :: anaconda :: Ales Kozumplik :: Anaconda netinstall fails with missing 'storage' module :: https://bugzilla.redhat.com/show_bug.cgi?id=636621 584328 :: NEW :: anaconda :: Anaconda Maintenance Team :: AttributeError: 'NoneType' object has no attribute 'name' :: https://bugzilla.redhat.com/show_bug.cgi?id=584328 623824 :: NEW :: gnome-settings-daemon :: Bastien Nocera :: Won't display on VGA-connected monitor :: https://bugzilla.redhat.com/show_bug.cgi?id=623824 629192 :: NEW :: pino :: Filipe Rosset :: Twitter isn't functioning :: https://bugzilla.redhat.com/show_bug.cgi?id=629192 635821 :: NEW :: report :: Gavin Romig-Koch :: Attempting to submit (scp or bugzilla) an exception report fails if networking not active :: https://bugzilla.redhat.com/show_bug.cgi?id=635821 617284 :: NEW :: distribution :: Justin M. Forbes :: Fedora 14 Virtualization Target Blocker :: https://bugzilla.redhat.com/show_bug.cgi?id=617284 627388 :: NEW :: anaconda :: Martin Sivák :: VNC install ignores password :: https://bugzilla.redhat.com/show_bug.cgi?id=627388 625367 :: NEW :: kdebase-workspace :: Ngo Than :: SELinux is preventing /usr/libexec/kde4/kdm_greet "write" access on /usr/libexec/kde4/lnusertemp :: https://bugzilla.redhat.com/show_bug.cgi?id=625367 626205 :: NEW :: kdebase-workspace :: Ngo Than :: Unable to unlock screen :: https://bugzilla.redhat.com/show_bug.cgi?id=626205 636585 :: NEW :: kdebase-workspace :: Ngo Than :: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault :: https://bugzilla.redhat.com/show_bug.cgi?id=636585 637405 :: NEW :: telepathy-haze :: Peter Gordon :: [abrt] telepathy-haze-0.4.0-1.fc14: media_channel_request_streams: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV) :: https://bugzilla.redhat.com/show_bug.cgi?id=637405 636118 :: NEW :: gnome-games :: Ray Strode [halfline] :: Swell Foop fails to run in F14 Beta RC3 Desktop live install :: https://bugzilla.redhat.com/show_bug.cgi?id=636118 633298 :: NEW :: kde-settings :: Rex Dieter :: Fedora 14 Blocker KDE Tracker :: https://bugzilla.redhat.com/show_bug.cgi?id=633298 626108 :: NEW :: nautilus :: Tomáš Bžatek :: nautilus-2.31.90-1.fc14.i686 not responding :: https://bugzilla.redhat.com/show_bug.cgi?id=626108 628528 :: NEW :: xorg-x11-drv-mouse :: X/OpenGL Maintenance List :: Emulating middle button doesn't work anymore. :: https://bugzilla.redhat.com/show_bug.cgi?id=628528 631987 :: NEW :: brasero :: Xavier Lamien :: [abrt] brasero-2.31.91-1.fc14: g_variant_is_trusted: Process /usr/bin/brasero was killed by signal 11 (SIGSEGV) :: https://bugzilla.redhat.com/show_bug.cgi?id=631987 626026 :: ASSIGNED :: kernel :: Kernel Maintainer List :: INFO: suspicious rcu_dereference_check() usage - kernel/sched.c:618 invoked rcu_dereference_check() without protection! :: https://bugzilla.redhat.com/show_bug.cgi?id=626026 635778 :: MODIFIED :: anaconda :: Brian C. Lane :: IndexError: list index out of range :: https://bugzilla.redhat.com/show_bug.cgi?id=635778 627789 :: MODIFIED :: anaconda :: Brian C. Lane :: Error setting up repository - 16, Device busy :: https://bugzilla.redhat.com/show_bug.cgi?id=627789 630226 :: MODIFIED :: mdadm :: Doug Ledford :: SELinux AVCs for mdadm :: https://bugzilla.redhat.com/show_bug.cgi?id=630226 ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing l
Upcoming Fedora 14 Tasks
Start End Name Tue 28-Sep Tue 28-Sep Beta Release Public Availability Fri 01-Oct Fri 01-Oct Final Blocker Meeting (f14blocker) #2 Fri 08-Oct Fri 08-Oct Final Blocker Meeting (f14blocker) #3 Mon 11-Oct Mon 11-Oct Submit Installer Builds for Final TC Compose Mon 11-Oct Fri 15-Oct Daily Review & Notification of Open Final Blocker Bugs -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Beta Declared GOLD
At the Fedora 14 Beta Go/No-Go meeting today, the Fedora 14 Beta was declared GOLD and ready for release on September 28, 2010. Thank you to everyone who made this on-time release possible! === #fedora-meeting: Fedora 14 Beta Go/No-Go Meeting Minutes and Logs === Meeting started by poelcat at 21:01:35 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2010-09-22/fedora-meeting.2010-09-22-21.01.log.html . Meeting summary --- * attendees rbergeron jsmith fenris02 SMParrish stickster jlaska adamw brunowolff (poelcat, 21:03:17) * http://fedoraproject.org/wiki/Engineering_Readiness_Meetings (poelcat, 21:03:42) * review of release criteria and open bugs (poelcat, 21:05:24) * adamw and jlaska here for qa (poelcat, 21:07:18) * SMParrish here for devel/FESCo (poelcat, 21:07:28) * dgilmore representing releng (poelcat, 21:07:38) * brunowolff is here for Spins SIG (brunowolff, 21:08:00) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_14_Beta_RC3_Install <--- install test matrix (adamw, 21:08:11) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_14_Beta_RC3_Desktop <--- desktop test matrix (adamw, 21:08:25) * LINK: https://bugzilla.redhat.com/showdependencytree.cgi?id=611991&hide_resolved=1 <--- beta blocker list (adamw, 21:08:49) * AGREED: 627789 is not a beta blocker (adamw, 21:12:54) * IDEA: create release criteria asserting some level of functionality of livecd-tools (jlaska, 21:13:03) * AGREED: move https://bugzilla.redhat.com/show_bug.cgi?id=627789 to f14blocker (poelcat, 21:15:00) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_RC3_Install (adamw, 21:19:50) * AGREED: publishing a documented updates.img with a fix for 635887 is an acceptable workaround, move 635887 to be a final blocker (adamw, 21:25:48) * AGREED: 542255 is not a regression, is of minor impact, and the question of non-default-spin bugs blocking releases requires further discussion and clarification, so we will not block the beta for this bug (adamw, 21:45:26) * ACTION: there being no unresolved blocking issues or unmet release criteria, Fedora 14 Beta is declared GOLD (poelcat, 21:55:34) * open discussion (poelcat, 21:55:37) Meeting ended at 21:58:31 UTC. Action Items * there being no unresolved blocking issues or unmet release criteria, Fedora 14 Beta is declared GOLD Action Items, by person --- * **UNASSIGNED** * there being no unresolved blocking issues or unmet release criteria, Fedora 14 Beta is declared GOLD People Present (lines said) --- * adamw (106) * poelcat (51) * jlaska (45) * dgilmore (27) * jsmith (22) * brunowolff (9) * fenris02 (9) * maxamillion (8) * stickster (7) * bcl (6) * mjg59 (5) * SMParrish (4) * zodbot (4) * rbergeron (4) * kalev (3) * mmcgrath (2) * skvidal (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Beta Go/No-Go Meeting Wednesday, September 22, 2010 @ 21:00 UTC
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: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime keep an eye on the Fedora 14 Beta Blocker list and help us get the testing matrix completed by testing. https://bugzilla.redhat.com/showdependencytree.cgi?id=F14Beta&hide_resolved=1 http://fedoraproject.org/wiki/Category:Fedora_14_Beta_RC_Test_Results John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Tue 14-Sep Tue 28-Sep Beta Infrastructure Change Freeze Wed 22-Sep Wed 22-Sep Fedora 14 Beta Go/No-Go Meeting (17:00 EST) Thu 23-Sep Thu 23-Sep Start Stage & Sync Beta to Mirrors Thu 23-Sep Thu 23-Sep Fedora 14 Beta Release Readiness Meeting Thu 23-Sep Tue 28-Sep Stage & Sync Beta to Mirrors Fri 24-Sep Fri 24-Sep Final Blocker Meeting (f14blocker) #1 Fri 24-Sep Fri 24-Sep Beta Export Control Reporting Tue 28-Sep Tue 28-Sep Beta Release Public Availability Thu 30-Sep Thu 30-Sep File All Release Engineering Tickets for Fedora 14 GA Fri 01-Oct Fri 01-Oct Final Blocker Meeting (f14blocker) #2 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Beta Release Date at Risk
We have missed the Fedora 14 Beta RC compose scheduled today because of unresolved Fedora 14 Beta Blocker bugs. https://bugzilla.redhat.com/showdependencytree.cgi?id=611991&hide_resolved=1 (NEW or ASSIGNED) As soon as these bugs are resolved with new packages we will request an RC compose from Release Engineering. John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Beta Change Deadline Reached 2010-09-14
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: https://fedoraproject.org/wiki/Change_deadlines John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
We have reached Fedora 14 Feature Complete
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/D_Programming (yes, a mere technicality at 99% done) https://fedoraproject.org/wiki/Features/GdbIndex https://fedoraproject.org/wiki/Features/GNUstep https://fedoraproject.org/wiki/Features/MemoryDebuggingTools https://fedoraproject.org/wiki/Features/Python_2.7 https://fedoraproject.org/wiki/Features/Spice Thank you, John p.s. Individual feature owners have been cc'd on this message. ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: 15 or rawhide?
Nils Philippsen said the following on 09/15/2010 03:28 AM Pacific Time: > On Tue, 2010-09-14 at 17:13 -0700, John Poelstra wrote: >> Shouldn't ABRT be looking to a file like /etc/fedora-release to >> determine the release version? > > r...@rawhide:~> cat /etc/fedora-release > Fedora release 15 (Finian) > > What you say ;-)? > > Nils I guess I'd say, there's a bug in /etc/fedora-release :-) John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: refining the feature process
Matthew Miller said the following on 09/15/2010 07:57 AM Pacific Time: > On Wed, Sep 15, 2010 at 03:37:55PM +0100, Adam Williamson wrote: >> I'm a bit confused. You spend the rest of the mail talking about when >> the feature freeze is for F15, but I'm not sure why. As long as F15 is >> open and it's not frozen (which it obviously isn't, yet) you can start >> doing development in it. As John P said, we've already started approving >> features for F15. So right now you can submit a feature for F15, have it >> approved, and start committing it. What is it that makes you say it's >> 'not the current feature process'? > > The current process says you *can* start now, but the Feature Submission > Deadline isn't until two weeks before Feature Freeze, which is in turn right > before the Alpha. > I don't recall any situation where someone submitted a feature at the deadline without having done anything and then scrambling for two weeks to finish by feature freeze. > One *can* start developing features at any time, but there's nothing in the > process that says one *should* do it earlier, and in fact, the late > deadlines imply a defacto standard last-minute approach. This isn't helped > by the description of the Feature Submission Deadline as not being really a > deadline at all: "FESCo will consider features proposed after this deadline > on an exception basis." > Exceptions have been few and far between, and only granted, to my knowledge, for features that were 100% complete. Those deadlines are set in such a way as to put as much development time as possible into a release schedule. From a release engineering perspective (the team proposing the schedules for approval by FESCo) it was determined that this was the highest value. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Meeting summary/minutes from today's FESCo meeting (2010-09-14)
Thorsten Leemhuis said the following on 09/15/2010 12:09 AM Pacific Time: > Toshio Kuratomi wrote on 15.09.2010 04:54: >> On Tue, Sep 14, 2010 at 07:02:33PM -0600, Kevin Fenzi wrote: >>> On Tue, 14 Sep 2010 20:48:13 -0400 >>> Máirín Duffy wrote: Only 5 of the 9 FESCo members voted on this issue. If all 9 had voted, even with the current 3 for / 2 against vote, systemd could easily have enough votes for inclusion in F14. I have a couple of questions for you, FESCo, since I honestly don't know and maybe would feel more comfortable knowing: >>> ok. >>> - Has there been any consideration for formalizing the acceptable of absentee votes? >>> no, but perhaps there should be? > > Just a side note: That has problems of its own, as those votes might > happen before new aspects come up in the IRC discussion that normally > precedes the votes in IRC meetings... > - How many members must be present at a meeting for a voting decision to be considered valid? >>> My understanding: A quorum (ie, 5 of 9). >> Note, in the distant past, FESCo's rule was majority of the folks present >> with an attempt made at unanimity by the present members by resolving (as >> much as possible) their differences in opinion. This was actually stated in >> meetings but I don't think that it made it to the wiki -- thl might know as >> that was during his tenure as chair. >> >> However, I don't believe this rule has been followed in a *long* time so >> it might just be a historical footnote to this conversation. > > Yes, back then we afaics tried a whole lot harder to make everyone > happy. That included even non-FESCo members that tried to raise options > on a particular topic on the list or in IRC meeting; we even let those > non-FESCo-members share a (mostly "unofficial") vote on IRC, as those > votes often influenced how FESCo member voted (which IMHO was a good thing). Maybe I'm reading more than you intended into what you said. I don't believe it is part of FESCo's charter or any other Fedora leadership group to "make everyone happy." That is an impossible job. My expectation of the leadership bodies in Fedora is that they oversee the current work and future direction of Fedora and do what is best for Fedora's success and future--even if there isn't unanimous happiness or agreement in the community. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Today is the LAST DAY to fix bugs for the Fedora 14 Beta
The Fedora 14 Beta RC compose is scheduled for tomorrow.
ALL open bugs on Fedora 14 Blocker list (http://bit.ly/cZKo9K) MUST BE
FIXED TODAY or we risk delaying the release. In other words we are very
short on time to address the remaining bugs.
Here is the current state of things based on the comments in each bug:
629719 :: NEW :: anaconda :: Anaconda Maintenance Team ::
FormatCreateError: ('invalid device specification', '/dev/md127p3') ::
https://bugzilla.redhat.com/show_bug.cgi?id=629719
Need to make a decision as to whether this bug should remain a blocker
based on testing feedback
634205 :: NEW :: bluez :: Bastien Nocera :: Bluetooth always disabled on
startup. :: https://bugzilla.redhat.com/show_bug.cgi?id=634205
New bug. Need assessment and a fix (if applicable) from maintainer ASAP
628239 :: NEW :: anaconda :: Brian C. Lane :: Fedora 14 Alpha "reduced
graphics" creates vesa-using xorg.conf but doesn't blacklist nouveau ::
https://bugzilla.redhat.com/show_bug.cgi?id=628239
Need additional confirmation that this bug still exists, but most likely
will be dropped.
633234 :: NEW :: anaconda :: Brian C. Lane :: Previous grub entry is not
overwritten after upgrade with creating new bootloader ::
https://bugzilla.redhat.com/show_bug.cgi?id=633234
Being researched by anacconda team. Could someone from the anaconda
team add a current status to the comments of the bug?
633315 :: NEW :: NetworkManager :: Dan Williams :: Connections not
editable in nm-c-e in anaconda ::
https://bugzilla.redhat.com/show_bug.cgi?id=633315
New bug. Need assessment and a fix (if applicable) from maintainer ASAP
632510 :: MODIFIED :: anaconda :: Chris Lumens :: Installer exited
abnormally when starting network in rescue mode ::
https://bugzilla.redhat.com/show_bug.cgi?id=632510
Need update submitted to Bodhi ASAP so this bug can change to ON_QA
632489 :: MODIFIED :: anaconda :: Radek Vykydal :: Fail to read package
metadata after specifying repo= ::
https://bugzilla.redhat.com/show_bug.cgi?id=632489
Need update submitted to Bodhi ASAP so this bug can change to ON_QA
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Meeting summary/minutes from today's FESCo meeting (2010-09-14)
Mike McGrath said the following on 09/15/2010 07:14 AM Pacific Time: > On Wed, 15 Sep 2010, Adam Williamson wrote: > >> On Wed, 2010-09-15 at 14:27 +0200, Tomasz Torcz wrote: >> >>>Personally, I'm very sad because of deferring systemd to F15. It may >>> cause slipping of SysV-free Fedora to F16, full year wait from now. And >>> integration as session daemon in DEs even further. >> >> There's no reason it should. Remember, F15 is open *now*, Rawhide is >> F15. All this work can be done right now, if there's the will to do it. >> > > For people wanting to make big changes to F15.. Do it *now*! F15 is in > its infancy. It's taking shape. If you want your feature to be a > defining feature of F15. Get it in *now*. > > -Mike And we are already reviewing and accepting features for Fedora 15. The process never stops. https://fedoraproject.org/wiki/Features/Policy John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: 15 or rawhide?
Jon Masters said the following on 09/14/2010 03:17 PM Pacific Time: > Folks, > > I was going to file an automated bug report, but it wants to file > against "15", which doesn't exist, rather than Rawhide (which obviously > does). I can email and ask for a version 15 to be added to Bugzilla, > etc. but is that the solution, or should ABRT be always realizing to use > rawhide and it's just a bug in that tool? > > Jon. > > No, please do not create version 15. Shouldn't ABRT be looking to a file like /etc/fedora-release to determine the release version? Rawhide is the repo where the packages and the version the bug was found in are until the repo branches and becomes 15, at which time version 15 will be created and the open rawhide bugs that aren't features will be changed to 15. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Blocker Bug Meeting Recap 2010-09-14
A last minute blocker bug meeting was held in #fedora-bugzappers to review the state of the open Fedora 14 Beta Blocker bugs. In order to create the Fedora 14 Beta Release Candidate on Thursday (2010-09-16), test, and release on time, this list MUST be empty by 2010-09-15 (tomorrow)! https://bugzilla.redhat.com/showdependencytree.cgi?id=611991&hide_resolved=1 YOU can help by re-testing bugs in MODIFIED or helping to debug bugs yet to be fixed. == #fedora-bugzappers: interim beta blocker bug review meeting 2010-09-14 == Meeting started by adamw at 18:05:56 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-bugzappers/2010-09-14/fedora-bugzappers.2010-09-14-18.05.log.html . Meeting summary --- * intro (adamw, 18:06:07) * https://bugzilla.redhat.com/show_bug.cgi?id=608992 (adamw, 18:07:23) * AGREED: 633827 adamw will test bcl's proposed fix and feed back to him (adamw, 18:13:53) * ACTION: adamw to test bcl fix for 633827 (adamw, 18:14:04) * https://bugzilla.redhat.com/show_bug.cgi?id=621027 (adamw, 18:14:49) * AGREED: 621027 fix is in but problem with live image bootloader background, jlaska to test potential fix from mizmo (adamw, 18:19:08) * ACTION: jlaska to test 621027 fixes from mizmo (adamw, 18:19:16) * https://bugzilla.redhat.com/show_bug.cgi?id=622927 (adamw, 18:21:12) * AGREED: 622927 ask tester to verify fix in TC1 and close the bug (adamw, 18:24:01) * https://bugzilla.redhat.com/show_bug.cgi?id=627014 (adamw, 18:24:33) * AGREED: 627014 looks like major issues are fixed, we can drop it from blocker list or close it when 10-1+ is accepted (adamw, 18:30:15) * https://bugzilla.redhat.com/show_bug.cgi?id=627401 (adamw, 18:30:32) * AGREED: 627401 is fixed in anaconda 14.17.1-1, anaconda team need to submit that or a later build to bodhi (adamw, 18:34:02) * https://bugzilla.redhat.com/show_bug.cgi?id=628239 (adamw, 18:34:26) * AGREED: 628239 does not appear to be valid as described, waiting on more info from reporter, but unless we learn something new, looks like this isn't a blocker (adamw, 18:38:34) * https://bugzilla.redhat.com/show_bug.cgi?id=628241 (adamw, 18:39:38) * LINK: https://admin.fedoraproject.org/updates/firstboot-1.113-1.fc14 - i posted a comment asking mgracik to push it (adamw, 18:41:31) * AGREED: 628241 is fixed in firstboot-1.113-1, needs to be pushed stable (adamw, 18:44:17) * ACTION: mgracik or notting to push firstboot-1.113-1 stable (adamw, 18:44:30) * https://bugzilla.redhat.com/show_bug.cgi?id=629719 (adamw, 18:44:40) * AGREED: 629719: we suspect reporter malfeasance, plan is to try and replicate in office, send out ml call to see if anyone else can, and ask reporter to try once more; if we get no more info on this bug will demote it (adamw, 19:06:20) * ACTION: adamw or jlaska to send out ml testing call for 629719 (adamw, 19:06:33) * https://bugzilla.redhat.com/show_bug.cgi?id=630490 (adamw, 19:07:00) * AGREED: 630490 testing indicates this is fixed in systemd-10, can be closed when that goes stable (adamw, 19:09:50) * https://bugzilla.redhat.com/show_bug.cgi?id=630952 (adamw, 19:10:32) * AGREED: testing indicates 630952 fix is good, bug can be closed when systemd/initscripts update goes stable (adamw, 19:12:35) * https://bugzilla.redhat.com/show_bug.cgi?id=631620 (adamw, 19:12:58) * AGREED: 631620 fix looks good in all important respects, can be closed when hal update is pushed (adamw, 19:18:26) * https://bugzilla.redhat.com/show_bug.cgi?id=632321 (adamw, 19:18:45) * AGREED: 632321 is fixed in systemd 10, can be closed when it goes stable (adamw, 19:29:40) * https://bugzilla.redhat.com/show_bug.cgi?id=632489 (adamw, 19:29:51) * AGREED: 632489 fix has been tested in updates.img, next anaconda build will include it (adamw, 19:32:20) * https://bugzilla.redhat.com/show_bug.cgi?id=632510 (adamw, 19:32:40) * AGREED: 632510 fix is in, needs a new build to test it; can either be a quick test boot.iso or we can test it in rc1 (adamw, 19:37:56) * https://bugzilla.redhat.com/show_bug.cgi?id=633234 (adamw, 19:38:05) * AGREED: 633234 is a blocker, top priority for anaconda team, it seems reproducible by at least two testers (adamw, 19:47:29) * ACTION: anaconda team to try and investigate and fix 633234 (adamw, 19:47:37) * https://bugzilla.redhat.com/show_bug.cgi?id=633315 (adamw, 19:48:19) * AGREED: 633315 doesn't seem like a blocker, we will reject it for now and ask radek to re-propose if he has a reason for it to be one (adamw, 20:02:24) * https://bugzilla.redhat.com/show_bug.cgi?id=633523 (adamw, 20:06:45) * AGREED: 633523 is an accepted blocker, we cc m
Open Fedora 14 Blocker Bugs Need to be fixed ASAP
Here are the current open Fedora 14 Beta Blocker bugs.
We need built packages and submitted to Bodhi that address each of these
bugs in order to start the Fedora 14 Beta Release Candidate compose on
2010-09-16.
If we are unable to start the RC compose on 2010-09-16 it could further
delay the Fedora 14 Beta and the final release.
629719 :: NEW :: anaconda :: anaconda-maint-l...@redhat.com ::
FormatCreateError: ('invalid device specification', '/dev/md127p3') ::
https://bugzilla.redhat.com/show_bug.cgi?id=629719
--Need more feedback from reporter
628239 :: NEW :: anaconda :: b...@redhat.com :: Fedora 14 Alpha "reduced
graphics" creates vesa-using xorg.conf but doesn't blacklist nouveau ::
https://bugzilla.redhat.com/show_bug.cgi?id=628239
--Need more feedback from reporter
633234 :: NEW :: anaconda :: b...@redhat.com :: Previous grub entry is
not overwritten after upgrade with creating new bootloader ::
https://bugzilla.redhat.com/show_bug.cgi?id=633234
--Need feedback from maintainer
633523 :: NEW :: empathy :: bdpep...@gmail.com :: Dependency issue block
empathy installs in F14 ::
https://bugzilla.redhat.com/show_bug.cgi?id=633523
--Need feedback from maintainer
632489 :: NEW :: anaconda :: rvyky...@redhat.com :: Fail to read package
metadata after specifying repo= ::
https://bugzilla.redhat.com/show_bug.cgi?id=632489
--Still debugging. Fix needed soon.
630490 :: ASSIGNED :: systemd :: lpoet...@redhat.com :: disabled units
still get bus activated ::
https://bugzilla.redhat.com/show_bug.cgi?id=630490
627401 :: MODIFIED :: anaconda :: clum...@redhat.com :: please create
systemd default.target symlink pointing to
/lib/systemd/system/runlevelX.target instead of
/etc/systemd/system/runlevelX.target ::
https://bugzilla.redhat.com/show_bug.cgi?id=627401
--Packages need to be submitted to Bodhi so status changes to ON_QA
632510 :: MODIFIED :: anaconda :: clum...@redhat.com :: Installer exited
abnormally when starting network in rescue mode ::
https://bugzilla.redhat.com/show_bug.cgi?id=632510
--Packages need to be submitted to Bodhi so status changes to ON_QA
608992 :: MODIFIED :: livecd-tools :: dh...@redhat.com :: Add "Boot
system with basic video driver" option at the initial screen ::
https://bugzilla.redhat.com/show_bug.cgi?id=608992
--Packages need to be submitted to Bodhi so status changes to ON_QA
627014 :: MODIFIED :: systemd :: lpoet...@redhat.com :: systemd provided
telinit does not work as advertised ::
https://bugzilla.redhat.com/show_bug.cgi?id=627014
--Packages need to be submitted to Bodhi so status changes to ON_QA
631620 :: MODIFIED :: systemd :: lpoet...@redhat.com :: ordering cycles
exist (+ breaking them deletes wrong services) ::
https://bugzilla.redhat.com/show_bug.cgi?id=631620
--Packages need to be submitted to Bodhi so status changes to ON_QA
622927 :: MODIFIED :: anaconda :: rvyky...@redhat.com :: F14 Alpha RC2 -
/etc/resolv.conf gets corrupted, cannot download packages ::
https://bugzilla.redhat.com/show_bug.cgi?id=622927
--Packages need to be submitted to Bodhi so status changes to ON_QA
621027 :: MODIFIED :: fedora-logos :: tcall...@redhat.com :: Graphical
screen in anaconda shows F-13 ::
https://bugzilla.redhat.com/show_bug.cgi?id=621027
--Packages need to be submitted to Bodhi so status changes to ON_QA
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Beta Blocker Meeting :: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)
John Poelstra said the following on 09/09/2010 05:19 PM Pacific Time: > When: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT) > Where: #fedora-bugzappers on irc.freenode.net > > Without these bugs fixed we can't compose the Fedora 14 Beta Release > Candidate on 2010-09-16. > == #fedora-bugzappers: Fedora 14 Beta Blocker Meeting == Meeting started by poelcat at 16:02:33 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-bugzappers/2010-09-10/fedora-bugzappers.2010-09-10-16.02.log.html . Meeting summary --- * roll call (poelcat, 16:02:51) * attendees nirik adamw jlaska poelcat jsmith (poelcat, 16:05:37) * https://bugzilla.redhat.com/show_bug.cgi?id=608992 (poelcat, 16:05:45) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=608992 waiting for a new build, needs to happen soon (poelcat, 16:07:25) * https://bugzilla.redhat.com/show_bug.cgi?id=621027 (poelcat, 16:07:34) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=621027 asking mizmo to update the bug and remind design team of change deadline on 2010-09-14 (poelcat, 16:12:53) * https://bugzilla.redhat.com/show_bug.cgi?id=628239 (poelcat, 16:13:08) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=628239 need to continue debugging before we can figure out where it needs to be fixed (poelcat, 16:20:05) * https://bugzilla.redhat.com/show_bug.cgi?id=629719 (poelcat, 16:20:22) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=629719 attempting to reproduce. If we cannot do so with TC1 testing will close INSUFFICIENT_DATA (poelcat, 16:28:36) * https://bugzilla.redhat.com/show_bug.cgi?id=630490 (poelcat, 16:28:41) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=630490 fix is in hand, maintainer expects to build new package tonight (poelcat, 16:45:36) * https://bugzilla.redhat.com/show_bug.cgi?id=630781 (poelcat, 16:45:48) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=630781 really need more information from reporter; if no further information or similiar reports by next week, will consider dropping (poelcat, 16:53:24) * https://bugzilla.redhat.com/show_bug.cgi?id=631620 (poelcat, 16:53:32) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=631620 fix and new packages anticipated this weekend, needs testing by kde, xfce and other desktops depending on HAL (poelcat, 17:05:05) * https://bugzilla.redhat.com/show_bug.cgi?id=632489 (poelcat, 17:05:25) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=632489 accepted as a blocker, fixed needed no later than 2010-09-14 (poelcat, 17:14:11) * https://bugzilla.redhat.com/show_bug.cgi?id=632510 (poelcat, 17:14:18) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=632510 accepted blocker; need to ammend blocker criteria to be more specific, devel believes it's an easy fix they expect to make soon (poelcat, 17:25:40) * open discussion (poelcat, 17:25:44) * ACTION: jlaska to propose adjusting beta release criteria to accomodate rescue-mode + networking (see 632510) (jlaska, 17:26:18) Meeting ended at 17:31:28 UTC. Action Items * https://bugzilla.redhat.com/show_bug.cgi?id=608992 waiting for a new build, needs to happen soon * https://bugzilla.redhat.com/show_bug.cgi?id=621027 asking mizmo to update the bug and remind design team of change deadline on 2010-09-14 * https://bugzilla.redhat.com/show_bug.cgi?id=628239 need to continue debugging before we can figure out where it needs to be fixed * https://bugzilla.redhat.com/show_bug.cgi?id=629719 attempting to reproduce. If we cannot do so with TC1 testing will close INSUFFICIENT_DATA * https://bugzilla.redhat.com/show_bug.cgi?id=630490 fix is in hand, maintainer expects to build new package tonight * https://bugzilla.redhat.com/show_bug.cgi?id=630781 really need more information from reporter; if no further information or similiar reports by next week, will consider dropping * https://bugzilla.redhat.com/show_bug.cgi?id=631620 fix and new packages anticipated this weekend, needs testing by kde, xfce and other desktops depending on HAL * https://bugzilla.redhat.com/show_bug.cgi?id=632489 accepted as a blocker, fixed needed no later than 2010-09-14 * https://bugzilla.redhat.com/show_bug.cgi?id=632510 accepted blocker; need to ammend blocker criteria to be more specific, devel believes it's an easy fix they expect to make soon * jlaska to propose adjusting beta release criteria to accomodate rescue-mode + networking (see 632510) Action Items, by person --- * jlaska * jlaska to propose adjusting beta release criteria to accomodate rescue-mode + networking (see 632510) * **UNASSIGNED** * https://bu
Upcoming Fedora 14 Tasks
Start End Name Tue 07-Sep Tue 14-Sep Software: Rebuild all translated packages Tue 14-Sep Tue 14-Sep Beta Change Deadline Tue 14-Sep Tue 14-Sep Features 100% Complete Deadline Tue 14-Sep Tue 28-Sep Beta Infrastructure Change Freeze Thu 16-Sep Thu 16-Sep Compose Beta Candidate Fri 17-Sep Fri 17-Sep Beta Blocker Meeting (f14beta) #4 Wed 22-Sep Wed 22-Sep Fedora 14 Beta Go/No-Go Meeting (17:00 EST) Thu 23-Sep Thu 23-Sep Fedora 14 Beta Release Readiness Meeting Thu 23-Sep Thu 23-Sep Start Stage & Sync Beta to Mirrors Thu 23-Sep Tue 28-Sep Stage & Sync Beta to Mirrors Fri 24-Sep Fri 24-Sep Beta Export Control Reporting Fri 24-Sep Fri 24-Sep Final Blocker Meeting (f14blocker) #1 Tue 28-Sep Tue 28-Sep Beta Release Public Availability -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Beta Blocker Meeting :: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)
When: Friday, 2010-09-10 @ 16:00 UTC (12 PM EDT)
Where: #fedora-bugzappers on irc.freenode.net
Without these bugs fixed we can't compose the Fedora 14 Beta Release
Candidate on 2010-09-16.
We'll be discussing these bugs to determine if they meet the criteria,
should stay on the list, and are getting the attention they need:
629719 :: NEW :: anaconda :: Anaconda Maintenance Team ::
FormatCreateError: ('invalid device specification', '/dev/md127p3') ::
https://bugzilla.redhat.com/show_bug.cgi?id=629719
628239 :: NEW :: anaconda :: Anaconda Maintenance Team :: Fedora 14
Alpha "reduced graphics" creates vesa-using xorg.conf but doesn't
blacklist nouveau :: https://bugzilla.redhat.com/show_bug.cgi?id=628239
608992 :: NEW :: livecd-tools :: David Huff :: Add "Boot system with
basic video driver" option at the initial screen ::
https://bugzilla.redhat.com/show_bug.cgi?id=608992
630781 :: NEW :: systemd :: Kernel Maintainer List :: systemd hangs on
"Clocksource tsc unstable" error and causes the system to freeze after
cpu-scaling detection :: https://bugzilla.redhat.com/show_bug.cgi?id=630781
630490 :: NEW :: systemd :: Lennart Poettering :: disabled units still
get bus activated :: https://bugzilla.redhat.com/show_bug.cgi?id=630490
631620 :: NEW :: systemd :: Lennart Poettering :: ordering cycles exist
(+ breaking them deletes wrong services) ::
https://bugzilla.redhat.com/show_bug.cgi?id=631620
621027 :: NEW :: fedora-logos :: Tom "spot" Callaway :: Graphical screen
in anaconda shows F-13 :: https://bugzilla.redhat.com/show_bug.cgi?id=621027
If you are the owner of any of these bugs, kindly update the comments
with your feedback as to whether you believe it is a blocker and what
your plans for fixing the bug are.
Do you have an issue you believe should be fixed before the Fedora 14
Beta ships? Please consider the following criteria when escalating an
issue: https://fedoraproject.org/wiki/Fedora_14_Beta_Release_Criteria
John
The command used to generate the list of bugs above is:
$ bugzilla query --blocked=611991 \
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
\
--outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
%{assigned_to} :: %{summary} :: %{url}"
NOTE: It this command doesn't work on Fedora 14.
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Unresolved Fedora 14 Beta Blocker Bugs
It's that time again! The Fedora 14 Release Candidate is scheduled for
creation one week from this Thursday on 2010-09-16. That task cannot be
completed if we have open blocker bugs (listed below). The sooner we
address these bugs the greater the likelihood we have of having time to
fix last minute bugs closer to the RC and ship the Fedora 14 Beta one time.
If you are the owner of any of the bugs listed below, your prompt
attention and feedback with your assessment and plans in the bugzilla
comments would be most helpful.
John
629719 :: NEW :: anaconda :: Anaconda Maintenance Team ::
FormatCreateError: ('invalid device specification', '/dev/md127p3') ::
https://bugzilla.redhat.com/show_bug.cgi?id=629719
623524 :: NEW :: anaconda :: Anaconda Maintenance Team :: Err during
filesystem check after upgrading bootloader ::
https://bugzilla.redhat.com/show_bug.cgi?id=623524
628239 :: NEW :: anaconda :: Anaconda Maintenance Team :: Fedora 14
Alpha "reduced graphics" creates vesa-using xorg.conf but doesn't
blacklist nouveau :: https://bugzilla.redhat.com/show_bug.cgi?id=628239
608992 :: NEW :: livecd-tools :: David Huff :: Add "Boot system with
basic video driver" option at the initial screen ::
https://bugzilla.redhat.com/show_bug.cgi?id=608992
630781 :: NEW :: systemd :: Kernel Maintainer List :: systemd hangs on
"Clocksource tsc unstable" error and causes the system to freeze after
cpu-scaling detection :: https://bugzilla.redhat.com/show_bug.cgi?id=630781
630490 :: NEW :: systemd :: Lennart Poettering :: disabled units still
get bus activated :: https://bugzilla.redhat.com/show_bug.cgi?id=630490
631620 :: NEW :: systemd :: Lennart Poettering :: systemd is not
starting haldaemon for KDE ::
https://bugzilla.redhat.com/show_bug.cgi?id=631620
628241 :: NEW :: firstboot :: Martin Gracik :: Fedora 14 Alpha, post
reboot installation steps not working ::
https://bugzilla.redhat.com/show_bug.cgi?id=628241
621027 :: NEW :: fedora-logos :: Tom "spot" Callaway :: Graphical screen
in anaconda shows F-13 :: https://bugzilla.redhat.com/show_bug.cgi?id=621027
627014 :: ASSIGNED :: systemd :: Lennart Poettering :: systemd provided
telinit does not work as advertised ::
https://bugzilla.redhat.com/show_bug.cgi?id=627014
___
devel-announce mailing list
devel-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Beta Change Deadline 2010-09-14
In addition, to next Tuesday (2010-09-14) being the Feature Complete deadline for Fedora 14, it is also the Beta Change Deadline. "At the change deadline, pushes to the branched development repository are suspended until the release candidate is accepted." More about what this means is here: https://fedoraproject.org/wiki/Change_deadlines John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
All Features 100% Complete by 2010-09-14
Hello Feature People, According to our schedule, seven days from today is Feature Complete for Fedora 14. https://fedoraproject.org/wiki/Releases/14/Schedule On September 14, 2010, all features must be 100% complete (not including bug fixes). Features that are not 100% complete will be sent to FESCo for further review. Please take time now to update your feature page to reflect all of the work completed for Fedora 14. Unfinished items can be rolled forward to a new page for Fedora 15. A friendly reminder that the feature pages list below are not at 100% complete: https://fedoraproject.org/wiki/Features/F14Boost144 https://fedoraproject.org/wiki/Features/D_Programming https://fedoraproject.org/wiki/Features/F14EclipseHelios https://fedoraproject.org/wiki/Features/GdbIndex https://fedoraproject.org/wiki/Features/GNUstep https://fedoraproject.org/wiki/Features/KDE45 https://fedoraproject.org/wiki/Features/MeeGo_1.0 https://fedoraproject.org/wiki/Features/OpenSCAP https://fedoraproject.org/wiki/Features/Python_2.7 https://fedoraproject.org/wiki/Features/Rakudo_Star https://fedoraproject.org/wiki/Features/Spice https://fedoraproject.org/wiki/Features/Sugar_0.90 Thank you, John p.s. All feature owners for the features listed above have been bcc'd on this email. ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Mon 06-Sep Fri 10-Sep Daily Review & Notification of Open Beta Blocker Bugs Tue 07-Sep Tue 07-Sep Software: Start Rebuild all translated packages Tue 07-Sep Tue 14-Sep Software: Rebuild all translated packages Thu 09-Sep Thu 09-Sep Create Beta Test Compose (TC) Fri 10-Sep Fri 10-Sep Beta Blocker Meeting (f14beta) #3 Tue 14-Sep Tue 14-Sep Features 100% Complete Deadline Tue 14-Sep Tue 14-Sep Beta Change Deadline Tue 14-Sep Tue 28-Sep Beta Infrastructure Change Freeze Thu 16-Sep Thu 16-Sep Compose Beta Candidate Fri 17-Sep Fri 17-Sep Beta Blocker Meeting (f14beta) #4 Have you found something that is working really well in your schedule? Or maybe you've found something you believe would work better in the future? Update the schedule retrospective page now to capture all of the important details as they happen: https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Blocker Bug Review Meeting 2010-09-03 @ 16:00 UTC (12 PM EST)
John Poelstra said the following on 09/02/2010 03:51 PM Pacific Time:
>> When: Friday, 2010-09-03 @ 16:00 UTC (12 PM EST)
>> Where: #fedora-bugzappers on irc.freenode.net
>>
>> Here are the current bugs listed as blocking the Beta release. We'll be
>> discussing all of these to determine if they meet the criteria, should
>> stay on the list, and are getting the attention they need:
>>
>> 629719 :: NEW :: anaconda :: Anaconda Maintenance Team ::
>> FormatCreateError: ('invalid device specification', '/dev/md127p3') ::
>> https://bugzilla.redhat.com/show_bug.cgi?id=629719
>>
>> 623524 :: NEW :: anaconda :: Anaconda Maintenance Team :: Err during
>> filesystem check after upgrading bootloader ::
>> https://bugzilla.redhat.com/show_bug.cgi?id=623524
>>
>> 624971 :: NEW :: anaconda :: Anaconda Maintenance Team :: Kernel
>> argument with "UUID=" is not honored ::
>> https://bugzilla.redhat.com/show_bug.cgi?id=624971
>>
>> 628239 :: NEW :: anaconda :: Anaconda Maintenance Team :: Fedora 14
>> Alpha "reduced graphics" creates vesa-using xorg.conf but doesn't
>> blacklist nouveau :: https://bugzilla.redhat.com/show_bug.cgi?id=628239
>>
>> 618504 :: NEW :: xmlrpc-c :: Enrico Scholz :: Cannot submit abrt bugs ::
>> https://bugzilla.redhat.com/show_bug.cgi?id=618504
>>
>> 621027 :: NEW :: fedora-logos :: Tom "spot" Callaway :: Graphical screen
>> in anaconda shows F-13 :: https://bugzilla.redhat.com/show_bug.cgi?id=621027
>>
>> 565323 :: ASSIGNED :: selinux-policy :: Daniel Walsh :: SELinux is
>> preventing /usr/bin/python "write" access on sysctl.conf. ::
>> https://bugzilla.redhat.com/show_bug.cgi?id=565323
>>
>> 622927 :: MODIFIED :: anaconda :: Radek Vykydal :: F14 Alpha RC2 -
>> /etc/resolv.conf gets corrupted, cannot download packages ::
>> https://bugzilla.redhat.com/show_bug.cgi?id=622927
>>
Meeting summary
---
* attendees: jlaska adamw skvidal poelcat (poelcat, 16:03:16)
* https://bugzilla.redhat.com/show_bug.cgi?id=621825 (poelcat,
16:03:39)
* https://bugzilla.redhat.com/show_bug.cgi?id=565323 (poelcat,
16:05:49)
* AGREED: https://bugzilla.redhat.com/show_bug.cgi?id=565323 move to
f14target because it does not meet explicit blocker criteria
(poelcat, 16:15:52)
* https://bugzilla.redhat.com/show_bug.cgi?id=618504 (poelcat,
16:16:10)
* ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=618504 no
feedback from reporter, wait one more week and drop at next meeting
if no feedback (poelcat, 16:21:08)
* https://bugzilla.redhat.com/show_bug.cgi?id=621027 (poelcat,
16:21:19)
* AGREED: tentatively accept #621027 as a beta blocker under mizmo's
outlined plan (adamw, 16:32:23)
* ACTION: jlaska to draft release criteria based on mizmo's outline
(adamw, 16:32:34)
* https://bugzilla.redhat.com/show_bug.cgi?id=623524 (poelcat,
16:33:33)
* ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=623524
conintuing to wait for more info (poelcat, 16:38:00)
* https://bugzilla.redhat.com/show_bug.cgi?id=624971 (poelcat,
16:38:12)
* LINK: https://admin.fedoraproject.org/updates/anaconda-14.17-1.fc14
(jlaska, 16:39:01)
* ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=624971 accepted
blocker hopefully resolved by new package (poelcat, 16:40:55)
* https://bugzilla.redhat.com/show_bug.cgi?id=627401 (poelcat,
16:41:08)
* AGREED: https://bugzilla.redhat.com/show_bug.cgi?id=627401 definite
blocker, added as accepted blocker (poelcat, 16:47:07)
* https://bugzilla.redhat.com/show_bug.cgi?id=628239 (poelcat,
16:47:16)
* ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=628239 propose
update to criteria and then re-evaluate bug in light of critiera at
next meeting (poelcat, 16:53:09)
* https://bugzilla.redhat.com/show_bug.cgi?id=629719 (poelcat,
16:53:22)
* ACTION: adamw to update alpha criterion covering vesa driver to
cover installed system as well as installer (adamw, 16:54:24)
* ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=629719 accept as
blocker (poelcat, 16:56:09)
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-09-03/fedora-bugzappers.2010-09-03-16.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-09-03/fedora-bugzappers.2010-09-03-16.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-09-03/fedora-bugzappers.2010-09-03-16.00.log.html
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Blocker Bug Review Meeting 2010-09-03 @ 16:00 UTC (12 PM EST)
CORRECTION Friday, 2010-09-03
> When: Friday, 2010-09-02 @ 16:00 UTC (12 PM EST)
> Where: #fedora-bugzappers on irc.freenode.net
>
> Here are the current bugs listed as blocking the Beta release. We'll be
> discussing all of these to determine if they meet the criteria, should
> stay on the list, and are getting the attention they need:
>
> 629719 :: NEW :: anaconda :: Anaconda Maintenance Team ::
> FormatCreateError: ('invalid device specification', '/dev/md127p3') ::
> https://bugzilla.redhat.com/show_bug.cgi?id=629719
>
> 623524 :: NEW :: anaconda :: Anaconda Maintenance Team :: Err during
> filesystem check after upgrading bootloader ::
> https://bugzilla.redhat.com/show_bug.cgi?id=623524
>
> 624971 :: NEW :: anaconda :: Anaconda Maintenance Team :: Kernel
> argument with "UUID=" is not honored ::
> https://bugzilla.redhat.com/show_bug.cgi?id=624971
>
> 628239 :: NEW :: anaconda :: Anaconda Maintenance Team :: Fedora 14
> Alpha "reduced graphics" creates vesa-using xorg.conf but doesn't
> blacklist nouveau :: https://bugzilla.redhat.com/show_bug.cgi?id=628239
>
> 618504 :: NEW :: xmlrpc-c :: Enrico Scholz :: Cannot submit abrt bugs ::
> https://bugzilla.redhat.com/show_bug.cgi?id=618504
>
> 621027 :: NEW :: fedora-logos :: Tom "spot" Callaway :: Graphical screen
> in anaconda shows F-13 :: https://bugzilla.redhat.com/show_bug.cgi?id=621027
>
> 565323 :: ASSIGNED :: selinux-policy :: Daniel Walsh :: SELinux is
> preventing /usr/bin/python "write" access on sysctl.conf. ::
> https://bugzilla.redhat.com/show_bug.cgi?id=565323
>
> 622927 :: MODIFIED :: anaconda :: Radek Vykydal :: F14 Alpha RC2 -
> /etc/resolv.conf gets corrupted, cannot download packages ::
> https://bugzilla.redhat.com/show_bug.cgi?id=622927
>
>
> If you are the owner of any of these bugs, kindly update the comments
> with your feedback as to whether you believe it is a blocker and what
> your plans for fixing the bug are.
>
> Do you have an issue you believe should be fixed before the Fedora 14
> Beta ships? Please consider the following criteria when escalating an
> issue: https://fedoraproject.org/wiki/Fedora_14_Beta_Release_Criteria
>
> Hope to see everyone tomorrow.
>
> John
>
> The command used to generate the list of bugs above is:
>
> $ bugzilla query --blocked=611991 \
>
> --bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
> \
> --outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
> %{assigned_to} :: %{summary} :: %{url}"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Blocker Bug Review Meeting 2010-09-02 @ 16:00 UTC (12 PM EST)
When: Friday, 2010-09-02 @ 16:00 UTC (12 PM EST)
Where: #fedora-bugzappers on irc.freenode.net
Here are the current bugs listed as blocking the Beta release. We'll be
discussing all of these to determine if they meet the criteria, should
stay on the list, and are getting the attention they need:
629719 :: NEW :: anaconda :: Anaconda Maintenance Team ::
FormatCreateError: ('invalid device specification', '/dev/md127p3') ::
https://bugzilla.redhat.com/show_bug.cgi?id=629719
623524 :: NEW :: anaconda :: Anaconda Maintenance Team :: Err during
filesystem check after upgrading bootloader ::
https://bugzilla.redhat.com/show_bug.cgi?id=623524
624971 :: NEW :: anaconda :: Anaconda Maintenance Team :: Kernel
argument with "UUID=" is not honored ::
https://bugzilla.redhat.com/show_bug.cgi?id=624971
628239 :: NEW :: anaconda :: Anaconda Maintenance Team :: Fedora 14
Alpha "reduced graphics" creates vesa-using xorg.conf but doesn't
blacklist nouveau :: https://bugzilla.redhat.com/show_bug.cgi?id=628239
618504 :: NEW :: xmlrpc-c :: Enrico Scholz :: Cannot submit abrt bugs ::
https://bugzilla.redhat.com/show_bug.cgi?id=618504
621027 :: NEW :: fedora-logos :: Tom "spot" Callaway :: Graphical screen
in anaconda shows F-13 :: https://bugzilla.redhat.com/show_bug.cgi?id=621027
565323 :: ASSIGNED :: selinux-policy :: Daniel Walsh :: SELinux is
preventing /usr/bin/python "write" access on sysctl.conf. ::
https://bugzilla.redhat.com/show_bug.cgi?id=565323
622927 :: MODIFIED :: anaconda :: Radek Vykydal :: F14 Alpha RC2 -
/etc/resolv.conf gets corrupted, cannot download packages ::
https://bugzilla.redhat.com/show_bug.cgi?id=622927
If you are the owner of any of these bugs, kindly update the comments
with your feedback as to whether you believe it is a blocker and what
your plans for fixing the bug are.
Do you have an issue you believe should be fixed before the Fedora 14
Beta ships? Please consider the following criteria when escalating an
issue: https://fedoraproject.org/wiki/Fedora_14_Beta_Release_Criteria
Hope to see everyone tomorrow.
John
The command used to generate the list of bugs above is:
$ bugzilla query --blocked=611991 \
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
\
--outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
%{assigned_to} :: %{summary} :: %{url}"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Schedule Tasks
Start End Name Fri 03-Sep Fri 03-Sep Beta Blocker Meeting (f14beta) #2 Mon 06-Sep Fri 10-Sep Daily Review & Notification of Open Beta Blocker Bugs Tue 07-Sep Tue 07-Sep Software: Start Rebuild all translated packages Tue 07-Sep Tue 14-Sep Software: Rebuild all translated packages Thu 09-Sep Thu 09-Sep Create Beta Test Compose (TC) Fri 10-Sep Fri 10-Sep Beta Blocker Meeting (f14beta) #3 Tue 14-Sep Tue 14-Sep Beta Change Deadline Tue 14-Sep Tue 14-Sep Features 100% Complete Deadline Tue 14-Sep Tue 28-Sep Beta Infrastructure Change Freeze Thu 16-Sep Thu 16-Sep Compose Beta Candidate Have you found something that is working really well in your schedule? Or maybe you've found something you believe would work better in the future? Update the schedule retrospective page now to capture all of the important details as they happen: https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Thu 19-Aug Tue 24-Aug Stage & Sync Alpha to Mirrors Tue 24-Aug Tue 24-Aug Alpha Public Availability Thu 26-Aug Thu 26-Aug File All Release Engineering Tickets for Fedora 14 Beta Fri 27-Aug Fri 27-Aug Build F-14 collection packages for all language translators Fri 27-Aug Fri 27-Aug Beta Blocker Meeting (f14beta) #1 Fri 27-Aug Fri 27-Aug Compose of image of Software Review UI for Translation Fri 03-Sep Fri 03-Sep Beta Blocker Meeting (f14beta) #2 Mon 06-Sep Fri 10-Sep Daily Review & Notification of Open Beta Blocker Bugs Tue 07-Sep Tue 07-Sep Software: Start Rebuild all translated packages Tue 07-Sep Tue 14-Sep Software: Rebuild all translated packages -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Declared GOLD
At the Go/No-Go meeting a few minutes ago the Fedora 14 Alpha release was declared GOLD. Thank you to everyone who contributed to making it happen! All the details of the meeting can be found here: Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2010-08-19/fedora-meeting.2010-08-19-00.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2010-08-19/fedora-meeting.2010-08-19-00.00.txt Log: http://meetbot.fedoraproject.org/fedora-meeting/2010-08-19/fedora-meeting.2010-08-19-00.00.log.html ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Upcoming Fedora 14 Tasks
Orion Poplawski said the following on 08/16/2010 08:39 PM Pacific Time: > Perhaps it makes sense to be posting F-15 tasks as well? > What would the Fedora 15 tasks be besides, "Do awesome stuff in the 'rawhide' branch?" :-) I can certainly draft a Fedora 15 version of the schedule if people are already curious where the dates will land. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Go/No-Go Meeting August 19, 2010 @ 12:00 AM UTC
Join us on irc.freenode.net #fedora-meeting for this important meeting. Thursday, August 19, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT-- Wednesday, August 18, 2010* ) "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 14 Alpha Blocker list (which is currently EMPTY!) https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1 ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The slip down memory lane
Peter Jones said the following on 08/16/2010 11:50 AM Pacific Time: > On 08/16/2010 02:06 PM, Mike McGrath wrote: >> On Mon, 16 Aug 2010, Peter Jones wrote: >> >>> On 08/12/2010 02:39 PM, Mike McGrath wrote: On Thu, 12 Aug 2010, Jason L Tibbitts III wrote: >> "BN" == Bill Nottingham writes: > > BN> I can't help but note that the slips have become more frequent as we > BN> started to actually *have* release criteria to test against. We > BN> didn't slip nearly as much when we weren't testing it. > > To me this implies that we should begin testing earlier (or, perhaps, > never stop testing) and treat any new failure as an event of > significance. It's tough to meet a six month cycle if we spend half of > it telling people to expect everything to be broken. > Possibly also stop changing earlier? >>> >>> The window for changes is already far too short. >>> >> >> How long is that window anyway? > > Depends on how you count. If we count development start to feature freeze: > > F12: 48 days (including july 4th) > F13: 53 days (including christmas and the US thanksgiving holiday) > F14: 63 days (including july 4th) > > Or maybe development start to alpha freeze: > > F12: 76 days (including july 4th) > F13: 84 days (including christmas and the US thanksgiving holiday) > F14: 70 days (including july 4th) > > Of course, some people would like to count from the previous "Final > Development > Freeze" (or even earlier) to, say, feature freeze, even though this is wildly > unrealistic for many of us: > > F12: 105 days (including july 4th) > F13: 133 days (including christmas and the US thanksgiving holiday) > F14: 115 days (including july 4th) > > this basically assumes nobody has to do any work on the previous release after > the final development freeze, which isn't really true. > > (I realize there are other important holidays in other countries, but I figure > this is a reasonable enough sample for exemplary purposes) > > Actually, from computing these numbers I think the best lesson is that our > schedules have been so completely volatile that it's very difficult to claim > they support any reasonable conclusions. > I agree. Here's the historical data I've tracked: http://poelstra.fedorapeople.org/schedules/f-14/f9-f14-schedule-analysis-v4.ods Because we are date-based and it has historically been that assumed people love Fedora so much they don't stop working on it over holidays, we've never considered the impact of holidays. Our schedules have changed a lot up until Fedora 13 and 14. This was the first time we did not "try something new" (after feature freeze) with the schedule. I agree it will take a few release cycles to figure out what is working and what isn't. This was my primary reason for arguing it was time to stop "trying something new" each release with the schedule. Because of our current scheduling methodology the development length varies between releases, but for Fedora 13 and 14 the freezes and testing durations are set the same (except for the week slip of the Fedora 13 Alpha that we absorbed which I believe contributed to slipping the Beta and Final). http://fedoraproject.org/wiki/Releases/Schedule (scheduling methodology) John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The slip down memory lane
Mike McGrath said the following on 08/16/2010 12:18 PM Pacific Time: > On Mon, 16 Aug 2010, Peter Jones wrote: > >> On 08/16/2010 02:06 PM, Mike McGrath wrote: >>> On Mon, 16 Aug 2010, Peter Jones wrote: >>> On 08/12/2010 02:39 PM, Mike McGrath wrote: > On Thu, 12 Aug 2010, Jason L Tibbitts III wrote: > >>> "BN" == Bill Nottingham writes: >> >> BN> I can't help but note that the slips have become more frequent as we >> BN> started to actually *have* release criteria to test against. We >> BN> didn't slip nearly as much when we weren't testing it. >> >> To me this implies that we should begin testing earlier (or, perhaps, >> never stop testing) and treat any new failure as an event of >> significance. It's tough to meet a six month cycle if we spend half of >> it telling people to expect everything to be broken. >> > > Possibly also stop changing earlier? The window for changes is already far too short. >>> >>> How long is that window anyway? >> >> Depends on how you count. If we count development start to feature freeze: >> >> F12: 48 days (including july 4th) >> F13: 53 days (including christmas and the US thanksgiving holiday) >> F14: 63 days (including july 4th) >> >> Or maybe development start to alpha freeze: >> >> F12: 76 days (including july 4th) >> F13: 84 days (including christmas and the US thanksgiving holiday) >> F14: 70 days (including july 4th) >> >> Of course, some people would like to count from the previous "Final >> Development >> Freeze" (or even earlier) to, say, feature freeze, even though this is wildly >> unrealistic for many of us: >> >> F12: 105 days (including july 4th) >> F13: 133 days (including christmas and the US thanksgiving holiday) >> F14: 115 days (including july 4th) >> >> this basically assumes nobody has to do any work on the previous release >> after >> the final development freeze, which isn't really true. >> >> (I realize there are other important holidays in other countries, but I >> figure >> this is a reasonable enough sample for exemplary purposes) >> >> Actually, from computing these numbers I think the best lesson is that our >> schedules have been so completely volatile that it's very difficult to claim >> they support any reasonable conclusions. >> > > I think this is worth further discussion. If the number is towards the > 48-63 days level and that's what window people are actually doing > development that may be a problem because it is an extremely short time > period. > > It's also interesting that with all the freezes, deadlines, etc we have > firm explicit set dates. While active development is implicit. it might > be worth it to set active deployment as an explicit time period just as > another reminder to everyone about when major changes are going on vs when > they aren't. > > -Mike It is implicit here: https://fedoraproject.org/wiki/Releases/14/Schedule It is more explicit here: http://poelstra.fedorapeople.org/schedules/f-14/f-14-devel-tasks.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The slip down memory lane
Till Maas said the following on 08/16/2010 11:41 AM Pacific Time: > On Mon, Aug 16, 2010 at 01:06:46PM -0500, Mike McGrath wrote: >> On Mon, 16 Aug 2010, Peter Jones wrote: >> >>> On 08/12/2010 02:39 PM, Mike McGrath wrote: On Thu, 12 Aug 2010, Jason L Tibbitts III wrote: >> "BN" == Bill Nottingham writes: > > BN> I can't help but note that the slips have become more frequent as we > BN> started to actually *have* release criteria to test against. We > BN> didn't slip nearly as much when we weren't testing it. > > To me this implies that we should begin testing earlier (or, perhaps, > never stop testing) and treat any new failure as an event of > significance. It's tough to meet a six month cycle if we spend half of > it telling people to expect everything to be broken. > Possibly also stop changing earlier? >>> >>> The window for changes is already far too short. >>> >> >> How long is that window anyway? > > It should be about 6 months, but from F13 branch to F14 branch it was only 5 > months and one week. Two of these months were after the F13 final release. F15 > is not yet scheduled afaics, so it is unknown how long the window for F15 will > stay open. > > References: > https://fedoraproject.org/wiki/Releases/13/Schedule > https://fedoraproject.org/wiki/Releases/14/Schedule > https://fedoraproject.org/wiki/Releases/15/Schedule > This is because if the previous release is late it takes time (in theory) from the next release. Some would argue that no times is taken from the subsequent release because rawhide is always available and can be committed to. Fedora 13 was originally scheduled two weeks later than its original anchor of May 1st so as not to collide with the Ubuntu release. Then it slipped two more weeks on its own. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: The slip down memory lane
Adam Williamson said the following on 08/13/2010 05:21 PM Pacific Time: > On Thu, 2010-08-12 at 16:11 -0600, Linuxguy123 wrote: > >> On the data side, it would be very interesting to go back to each one of >> those slips and identify the component(s) that caused the slip and then >> question the individuals behind them to find out what happened. Then >> take that information (share it with the list ?) and see what can be >> concluded (as a group ?) > > This would be incomplete data. > > For instance, the bug we decided to slip Alpha for was the 'basic video > driver' menu entry in the installer not working. But that's not > necessarily the entire cause of the slip. If the entire release process > had run on time, and we'd had really testable candidate images earlier > than we did, it's entirely possible this bug would have been identified > and fixed in time for the Alpha to be shipped. > > Just looking at the specific bugs that end up blocking the release does > not give a complete picture of why the release slipped. Well put. All the incremental steps along the road are documented here for Fedora 14. https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective Each piece adds up to the point were we just can't finish in the allotted time. Anecdotally, what happened in this release is not unusual. Each release we have these "this shouldn't ever happen again" items and while they have different names the reasons are almost always the same--landing changes to packages or infrastructure right on the deadline or not budgeting enough time to recover before the deadline if something goes wrong. It would be great to get more entries from other people on this wiki page. Please don't send them to the list, but put them on the wiki page. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Wed 18-Aug Wed 18-Aug Fedora 14 Alpha Go/No-Go Meeting (17:00 EST) Wed 18-Aug Fri 20-Aug Build F-14 collection packages for all language translators Thu 19-Aug Thu 19-Aug Start Stage & Sync Alpha to Mirrors Thu 19-Aug Tue 24-Aug Stage & Sync Alpha to Mirrors Fri 20-Aug Fri 20-Aug Compose of image of Software Review UI for Translation Fri 20-Aug Fri 20-Aug Alpha Export Control Reporting Tue 24-Aug Tue 24-Aug Alpha Public Availability Thu 26-Aug Thu 26-Aug File All Release Engineering Tickets for Fedora 14 Beta Fri 27-Aug Fri 27-Aug Beta Blocker Meeting (f14beta) #1 This schedule reflects the delay of the Fedora 14 Alpha Release by one week and extension of the remaining dates on the schedule. Please let me know if any of the dates look wrong or do not reflect the wishes of your team. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Blocker Bug Review Meeting 2010-08-13 @ 16:00 UTC (12 PM EST)
Subject: Fedora 14 Blocker Bug Review Meeting 2010-08-13 @ 16:00 UTC (12
PM EST)
When: Friday, 2010-08-13 @ 16:00 UTC (12 PM EST)
Where: #fedora-bugzappers on irc.freenode.net
Here are the current bugs listed as blocking the Alpha release. We'll be
discussing all of these to determine if they meet the criteria, should
stay on the list, and are getting the attention they need:
596985 :: NEW :: xorg-x11-drv-ati :: Jerome Glisse :: hang at start of
X11 on fresh install from DVD ::
https://bugzilla.redhat.com/show_bug.cgi?id=596985
We will also start looking at the Beta blocker bugs as we change our
mindframe to start focusing on the criteria for the beta:
623126 :: NEW :: anaconda :: Anaconda Maintenance Team :: F14 Alpha RC3
CD install fails :: https://bugzilla.redhat.com/show_bug.cgi?id=623126
618504 :: NEW :: xmlrpc-c :: Enrico Scholz :: Can not submit abrt bugs
:: https://bugzilla.redhat.com/show_bug.cgi?id=618504
621027 :: NEW :: fedora-logos :: Tom "spot" Callaway :: Graphical screen
in anaconda shows F-13 :: https://bugzilla.redhat.com/show_bug.cgi?id=621027
615386 :: ASSIGNED :: autofs :: Ian Kent :: automount[3035]:
open_lookup:90: cannot open lookup module ldap
(/usr/lib64/autofs/lookup_ldap.so: undefined symbol:
krb5_get_init_creds_keytab) ::
https://bugzilla.redhat.com/show_bug.cgi?id=615386
623257 :: ASSIGNED :: polkit-gnome :: David Zeuthen :: Authentication
agent does not work :: https://bugzilla.redhat.com/show_bug.cgi?id=623257
621685 :: MODIFIED :: anaconda :: Brian C. Lane :: TypeError: sequence
item 0: expected string, NoneType found ::
https://bugzilla.redhat.com/show_bug.cgi?id=621685
If you are the owner of any of these bugs, kindly update the comments
with your feedback as to whether you believe it is a blocker and what
your plans for fixing the bug are.
Do you have an issue you believe should be fixed before the Fedora 14
Beta ships? Please consider the following criteria when escalating an
issue: https://fedoraproject.org/wiki/Fedora_14_Beta_Release_Criteria
Hope to see everyone tomorrow.
John
The command used to generate the list of bugs above is:
$ bugzilla query --blocked=611991 \
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
\
--outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
%{assigned_to} :: %{summary} :: %{url}"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 14 Alpha RC3 Available Now!
Jared K. Smith said the following on 08/11/2010 06:15 AM Pacific Time: > On Wed, Aug 11, 2010 at 1:01 AM, Adam Williamson wrote: >> Thanks, Andre! Everyone please note we have the go/no-go meeting for >> Alpha release tomorrow afternoon at 5pm Eastern time, so we really >> *really* need as much testing as possible by then. > > I have the Go/No-Go meeting in my calendar as Thursday, August 12, > 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT, > Wednesday, August 11, 2010* ). I just want to make sure we're all on > the same schedule here. > > -- > Jared Smith > Fedora Project Leader The correct time for this meeting is: Thursday, August 12, 2010, @ 12:00 AM UTC In other words, if you are in the USA, it will happen TODAY at: 20:00 Eastern or 17:00 Pacific John p.s. Sorry for the confusion as realize this contradicts the time that was on the detailed schedule. Hopefully the three extra hours helps :) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Reminder: Bugzilla UPGRADE to 3.6 on August 13th 9:00 p.m.EDT [01:00 UTC]
Sending on behalf of Dave Lawrence. This will affect Fedora too. REMINDER: Red Hat Bugzilla (bugzilla.redhat.com) will be unavailable on August 13th starting at 9:00 p.m. EDT [01:00 UTC] to perform an upgrade from Bugzilla 3.4 to Bugzilla 3.6. We are hoping to be complete in no more than 5 hours barring any problems. Any services relying on bugzilla.redhat.com may not work properly during this time. Please be aware in case you need use of those services during the outage. Also *PLEASE* make sure any scripts or other external applications that rely on bugzilla.redhat.com are tested against our test server before the upgrade if you have not done so already (see original email below). Let the Bugzilla Team know immediately of any issues found by reporting the bug in bugzilla.redhat.com against the Bugzilla product, version 3.6. --- Greetings, The Red Hat Bugzilla team is happy to announce another public beta release of the next version of Red Hat Bugzilla based on the upstream 3.6 code base. Please test drive at: https://partner-bugzilla.redhat.com Over the years Red Hat has made substantial customizations to Bugzilla to fit into the Engineering tool chain. Over time the upstream has incorporated some of these customizations or solved them in different ways. Upgrading reduces our customization footprint (and thus maintenance) while bringing many bug fixes & enhancements. The main area of focus for our public betas is stability. Functionality that currently works in our 3.4 code base should continue to work as expected in the new 3.6 release. These include various ajax optimizations, needinfo actor support, frontpage.cgi, product browser, several various UI enhancements, and of course the XMLRPC API. Please feel free to point your various scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly. There are numerous other changes behind the scenes that we haven't listed. The goal is to make sure that functionality that people have come to expect in 3.4 is possible in the new system. There are also numerous new features/fixes that are part of the upstream 3.6 release. For more detailed information on what has changed since the last release, check out the release notes page at https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html . The database is a recent snapshot of the live database so should be useful for testing to make sure the information is displayed properly and changeable. Also with a full snapshot it is possible to test for any performance related issues. Email has been disabled so that unnecessary spam is not sent out. So feel free to make changes to bugs to verify proper working order. We are asking for everyone to get involved as much as possible with testing and feedback on the beta releases to help us make this the most robust and stable release possible. Please file any enhancement requests or bug reports in our current Bugzilla system at https://bugzilla.redhat.com . File them under the Bugzilla product and relevant component with the version 3.6. With everyone's help we can make this a great release. Thanks The Red Hat Bugzilla Team ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Reminder: Bugzilla UPGRADE to 3.6 on August 13th 9:00 p.m.EDT [01:00 UTC]
Sending on behalf of Dave Lawrence. This will affect Fedora too. REMINDER: Red Hat Bugzilla (bugzilla.redhat.com) will be unavailable on August 13th starting at 9:00 p.m. EDT [01:00 UTC] to perform an upgrade from Bugzilla 3.4 to Bugzilla 3.6. We are hoping to be complete in no more than 5 hours barring any problems. Any services relying on bugzilla.redhat.com may not work properly during this time. Please be aware in case you need use of those services during the outage. Also *PLEASE* make sure any scripts or other external applications that rely on bugzilla.redhat.com are tested against our test server before the upgrade if you have not done so already (see original email below). Let the Bugzilla Team know immediately of any issues found by reporting the bug in bugzilla.redhat.com against the Bugzilla product, version 3.6. --- Greetings, The Red Hat Bugzilla team is happy to announce another public beta release of the next version of Red Hat Bugzilla based on the upstream 3.6 code base. Please test drive at: https://partner-bugzilla.redhat.com Over the years Red Hat has made substantial customizations to Bugzilla to fit into the Engineering tool chain. Over time the upstream has incorporated some of these customizations or solved them in different ways. Upgrading reduces our customization footprint (and thus maintenance) while bringing many bug fixes & enhancements. The main area of focus for our public betas is stability. Functionality that currently works in our 3.4 code base should continue to work as expected in the new 3.6 release. These include various ajax optimizations, needinfo actor support, frontpage.cgi, product browser, several various UI enhancements, and of course the XMLRPC API. Please feel free to point your various scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly. There are numerous other changes behind the scenes that we haven't listed. The goal is to make sure that functionality that people have come to expect in 3.4 is possible in the new system. There are also numerous new features/fixes that are part of the upstream 3.6 release. For more detailed information on what has changed since the last release, check out the release notes page at https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html . The database is a recent snapshot of the live database so should be useful for testing to make sure the information is displayed properly and changeable. Also with a full snapshot it is possible to test for any performance related issues. Email has been disabled so that unnecessary spam is not sent out. So feel free to make changes to bugs to verify proper working order. We are asking for everyone to get involved as much as possible with testing and feedback on the beta releases to help us make this the most robust and stable release possible. Please file any enhancement requests or bug reports in our current Bugzilla system at https://bugzilla.redhat.com . File them under the Bugzilla product and relevant component with the version 3.6. With everyone's help we can make this a great release. Thanks The Red Hat Bugzilla Team ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Go/No-Go Meeting August 12, 2010 @ 12:00 AM UTC
Join us on irc.freenode.net #fedora-meeting for this important meeting. Thursday, August 12, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT, Wednesday, August 11, 2010* ) "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 14 Alpha Blocker list and help us test! https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1 http://fedoraproject.org/wiki/Category:Fedora_14_Alpha_RC_Test_Results John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F14 update pushes
Rahul Sundaram said the following on 08/09/2010 10:47 PM Pacific Time: > More documentation of the process, perhaps via a SOP is needed then. > > Rahul > It's here: https://fedoraproject.org/wiki/Change_deadlines John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Wed 11-Aug Wed 11-Aug Fedora 14 Alpha Go/No-Go Meeting (17:00 EST) Thu 12-Aug Thu 12-Aug Fedora 14 Alpha Release Readiness Meeting Thu 12-Aug Thu 12-Aug Start Stage & Sync Alpha to Mirrors Thu 12-Aug Tue 17-Aug Stage & Sync Alpha to Mirrors Fri 13-Aug Fri 13-Aug Alpha Export Control Reporting Tue 17-Aug Tue 17-Aug Alpha Public Availability Wed 18-Aug Fri 20-Aug Build F-14 collection packages for all language translators Thu 19-Aug Thu 19-Aug File All Release Engineering Tickets for Fedora 14 Beta Fri 20-Aug Fri 20-Aug Beta Blocker Meeting (f14beta) #1 Fri 20-Aug Fri 20-Aug Compose of image of Software Review UI for Translation -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Alpha Blocker Bug Review Meeting 2010-08-06 @ 16:00 UTC (12 PM EST/9 AM PST)
John Poelstra said the following on 08/05/2010 08:35 PM Pacific Time: > Meeting at our regular time and location! > > When: 16:00 UTC (12 PM EST/9 AM PST) > Where: irc.freenode.net #fedora-bugzappers > > Please join us. Here are the bugs we'll look at and discuss: > > 621102 :: NEW :: udev :: Harald Hoyer :: The installer doesn't use > packages repository in DVD as default :: > https://bugzilla.redhat.com/show_bug.cgi?id=621102 > > > 621200 :: ASSIGNED :: systemd :: Lennart Poettering :: [abrt] > systemd-units-5-2.fc15: selabel_lookup_common: Process /bin/systemctl > was killed by signal 11 (SIGSEGV) :: > https://bugzilla.redhat.com/show_bug.cgi?id=621200 > > == #fedora-bugzappers: Fedora 14 Alpha Blocker Review == Meeting started by poelcat at 16:01:13 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-bugzappers/2010-08-06/fedora_14_alpha_blocker_review.2010-08-06-16.01.log.html . Meeting summary --- * attendees: fcami nirik jlaska adamw damNageHack (poelcat, 16:05:09) * https://bugzilla.redhat.com/show_bug.cgi?id=620211 (poelcat, 16:05:52) * LINK: http://koji.fedoraproject.org/koji/getfile?taskID=2371327&name=build.log&offset=-4000 (adamw, 16:08:21) * Options to resolve include 1) Either remove the python-psyco package from i386 DVD, or 2) Correct py-2.7 build issues and rebuild python-psyco (jlaska, 16:11:01) * LINK: http://hg.python.org/cpython/rev/da03d23e29b9 (adamw, 16:19:35) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=620211 adamw has the ball right now ... attempting a rebuild ... will pull in others if that fails adamw to try rebuilding based on http://hg.python.org/cpython/rev/da03d23e29b9 + set to accepted blocker + adamw to update bug comments (poelcat, 16:22:21) * https://bugzilla.redhat.com/show_bug.cgi?id=621102 (poelcat, 16:22:40) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=621102 does not meet alpha criteria, however does meet beta criteria + set as accepted blocker for beta + add to common bugs page; adamw to document all (poelcat, 16:37:21) * https://bugzilla.redhat.com/show_bug.cgi?id=621775 (poelcat, 16:37:35) * ACTION: : https://bugzilla.redhat.com/show_bug.cgi?id=621775 dgilmore is trying to identify root cause, believed to be a compose issue; accepted alpha blocker, stickster will update the bug (poelcat, 16:51:58) * https://bugzilla.redhat.com/show_bug.cgi?id=621864 (poelcat, 16:52:11) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=621864 NOT accepted as an alpha blocker, move to target, fcami check it out and re-propose it if something bad shows up; fcami will update bug appropriately (poelcat, 16:58:29) * open discussion (poelcat, 16:58:39) * https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=609049 (poelcat, 16:59:48) * ACTION: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=609049 new udev package has been built for udev; need to retest (poelcat, 17:01:01) * Where are the next steps towards getting another F14 Alpha RC? (poelcat, 17:03:10) * we'll watch for status in https://fedorahosted.org/rel-eng/ticket/3860 (poelcat, 17:06:25) * ACTION: add bugs discussed today to trac ticket, get them fixed and built, wait for new compose that hopefully can be ready tonight (poelcat, 17:12:10) * xorg vmware (poelcat, 17:12:38) * F14 can't bring Xorg when running as a vmware guest (poelcat, 17:14:46) * ACTION: file a bug and throw it on f14beta (poelcat, 17:14:55) * Open discussion (poelcat, 17:15:03) Meeting ended at 17:17:09 UTC. Action Items * https://bugzilla.redhat.com/show_bug.cgi?id=620211 adamw has the ball right now ... attempting a rebuild ... will pull in others if that fails adamw to try rebuilding based on http://hg.python.org/cpython/rev/da03d23e29b9 + set to accepted blocker + adamw to update bug comments * https://bugzilla.redhat.com/show_bug.cgi?id=621102 does not meet alpha criteria, however does meet beta criteria + set as accepted blocker for beta + add to common bugs page; adamw to document all * : https://bugzilla.redhat.com/show_bug.cgi?id=621775 dgilmore is trying to identify root cause, believed to be a compose issue; accepted alpha blocker, stickster will update the bug * https://bugzilla.redhat.com/show_bug.cgi?id=621864 NOT accepted as an alpha blocker, move to target, fcami check it out and re-propose it if something bad shows up; fcami will update bug appropriately * https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=609049 new udev package has been built for udev; need to retest * add bugs discussed today to trac ticket, get them fixed and built, wai
Fedora 14 Alpha Blocker Bug Review Meeting 2010-08-06 @ 16:00 UTC (12 PM EST/9 AM PST)
Meeting at our regular time and location! When: 16:00 UTC (12 PM EST/9 AM PST) Where: irc.freenode.net #fedora-bugzappers Please join us. Here are the bugs we'll look at and discuss: 621102 :: NEW :: udev :: Harald Hoyer :: The installer doesn't use packages repository in DVD as default :: https://bugzilla.redhat.com/show_bug.cgi?id=621102 621200 :: ASSIGNED :: systemd :: Lennart Poettering :: [abrt] systemd-units-5-2.fc15: selabel_lookup_common: Process /bin/systemctl was killed by signal 11 (SIGSEGV) :: https://bugzilla.redhat.com/show_bug.cgi?id=621200 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Alpha Can Still Ship on Time IF these bugs get attention TODAY
David Malcolm said the following on 08/05/2010 11:55 AM Pacific Time: > On Thu, 2010-08-05 at 11:46 -0700, John Poelstra wrote: >> Tom "spot" Callaway said the following on 08/05/2010 10:08 AM Pacific Time: >>> On 08/05/2010 12:59 PM, John Poelstra wrote: >>>> 597858 [NEW - high - dwa...@redhat.com - --- -] "SELinux is preventing >>>> firefox from making its memory writable and executable." crashes rawhide >>>> firefox start >>> >>> The update to fix this one out is here: >>> >>> https://admin.fedoraproject.org/updates/selinux-policy-3.8.8-10.fc14 >>> >>> ~spot >> >> That's excellent information to put in the bug. > > Bodhi does this automatically if you add the bug number to the update > when you create it [1]; not sure if it does it when adding a bug to an > already-created update. The biggest time consumer for me (and several people behind the scenes) this release (actually it probably happens every release, but I haven't taken this active a role before) has been pinging bugs where there is not enough information tell what is going on. There has to be a better way. If each person took a minute or two to add a comment of "what the next step is" or what they are waiting for, we'd have a much clearer picture of where the release stands. The alternatives are to do nothing and miss our dates or spam the list and ping bugs until we get to the finish line. Flags, better tooling, or more blocker meetings aren't the solution--people communicating proactively is. Are there any other things I can do to help make this go more smoothly? Are there any other people willing to formally step up and help me do this? John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Alpha Can Still Ship on Time IF these bugs get attention TODAY
Thomas Spura said the following on 08/05/2010 11:22 AM Pacific Time: > Am Thu, 05 Aug 2010 09:59:52 -0700 > schrieb John Poelstra: > >> John Poelstra said the following on 08/04/2010 10:48 AM Pacific Time: >> Here are the unfixed bugs we are waiting for more information on: >> >> 583731 [NEW - high - m...@romal.de - --- -] man-pages-de has file >> conflicts with man-db [See dependency tree for bug 583731] > [snip] > > This should be fixed in: > https://admin.fedoraproject.org/updates/man-pages-de-0.5-4.fc14 > > Thomas Please put that information in the bug. Thanks, John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Alpha Can Still Ship on Time IF these bugs get attention TODAY
Tom "spot" Callaway said the following on 08/05/2010 10:08 AM Pacific Time: > On 08/05/2010 12:59 PM, John Poelstra wrote: >> 597858 [NEW - high - dwa...@redhat.com - --- -] "SELinux is preventing >> firefox from making its memory writable and executable." crashes rawhide >> firefox start > > The update to fix this one out is here: > > https://admin.fedoraproject.org/updates/selinux-policy-3.8.8-10.fc14 > > ~spot That's excellent information to put in the bug. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Alpha Can Still Ship on Time IF these bugs get attention TODAY
John Poelstra said the following on 08/04/2010 10:48 AM Pacific Time: > > In order for Release Engineering to create the Fedora 14 Alpha RC, all > of the bugs below must be in a state of CLOSED or ON_QA by > tomorrow--Bodhi updates have been submitted and the packages are in > updates-testing. And, no new blocker bugs are identified before then. > > If there are other bugs that are of concern that you believe meet the > release criteria, add 'f14alpha' as a blocker or ask for help on #fedora-qa. > Going solely by the bugzilla comments which is where the latest information should be, it is very unclear (I would suggest unlikely) that we will be able to request a Release Candidate compose for the Fedora 14 Alpha from Release Engineering today. I know folks are busy with lots of different things. Without more information about what is happening or planned to happen next we don't have any other options. The result will be late release. John Here are the unfixed bugs we are waiting for more information on: 583731 [NEW - high - m...@romal.de - --- -] man-pages-de has file conflicts with man-db [See dependency tree for bug 583731] 596985 [NEW - urgent - jgli...@redhat.com - --- - Triaged] hang at start of X11 on fresh install from DVD [See dependency tree for bug 596985] 597858 [NEW - high - dwa...@redhat.com - --- -] "SELinux is preventing firefox from making its memory writable and executable." crashes rawhide firefox start 512845 [ASSIGNED - high - stran...@redhat.com - --- - Reopened, Security, SELinux, Triaged] setroubleshoot: SELinux is preventing firefox from changing a writable memory segment executable. 620623 [ASSIGNED - medium - nott...@redhat.com - --- -] Packages with unresolved dependencies [See dependency tree for bug 620623] 620949 [ASSIGNED - medium - rstr...@redhat.com - --- -] [abrt] gnome-panel-2.31.4-3.fc14: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV) 621030 [ASSIGNED - medium - wwo...@redhat.com - --- -] Fail to save traceback to bugzilla ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Can Still Ship on Time IF these bugs get attention TODAY
It's been an exciting ride so far and we're embracing the peaks and valleys of the Fedora release process in real time. Even with all the recent changes and bugs we still have a shot at creating the Fedora 14 Release Candidate on schedule TOMORROW. Failure to successfully build the RC tomorrow could put the Fedora 14 Alpha at risk and push out the rest the schedule. In order for Release Engineering to create the Fedora 14 Alpha RC, all of the bugs below must be in a state of CLOSED or ON_QA by tomorrow--Bodhi updates have been submitted and the packages are in updates-testing. And, no new blocker bugs are identified before then. If there are other bugs that are of concern that you believe meet the release criteria, add 'f14alpha' as a blocker or ask for help on #fedora-qa. Thank you package maintainers and testers for all that you do! John 597858 :: NEW :: xdg-utils :: Rex Dieter :: "SELinux is preventing firefox from making its memory writable and executable." crashes rawhide firefox start :: https://bugzilla.redhat.com/show_bug.cgi?id=597858 --waiting to confirm availability of new selinux-policy 620623 :: ASSIGNED :: distribution :: Bill Nottingham :: Packages with unresolved dependencies :: https://bugzilla.redhat.com/show_bug.cgi?id=620623 --need rebuilt dependencies: https://bugzilla.redhat.com/show_bug.cgi?id=620944 --need rebuilt dependencies: https://bugzilla.redhat.com/show_bug.cgi?id=621286 620949 :: ASSIGNED :: gnome-panel :: Ray Strode [halfline] :: [abrt] gnome-panel-2.31.4-3.fc14: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV) :: https://bugzilla.redhat.com/show_bug.cgi?id=620949 --waiting for new build and submission to Bodhi 619889 :: ASSIGNED :: xorg-x11 :: X/OpenGL Maintenance List :: X.org pegged at 100% CPU usage after booting with systemd :: https://bugzilla.redhat.com/show_bug.cgi?id=619889 --waiting for new build and submission to Bodhi 615443 :: MODIFIED :: livecd-tools :: Bruno Wolff III :: booting live images from nightly fails (can't mount root filesystem) :: https://bugzilla.redhat.com/show_bug.cgi?id=615443 --appears to be fixed? Has packaged moved to updates-testing? 620900 :: MODIFIED :: anaconda :: Anaconda Maintenance Team :: traceback on install of F14 Alpha Test Compose #2 :: https://bugzilla.redhat.com/show_bug.cgi?id=620900 --should be fixed, need a new compose 617115 :: ON_QA :: livecd-tools :: Bruno Wolff III :: rawhide live spins showing black screen instead of syslinux boot menu :: https://bugzilla.redhat.com/show_bug.cgi?id=617115 --Needs Bodhi feedback ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Plan for tomorrow's FESCo meeting (2010-08-03)
Kevin Fenzi said the following on 08/02/2010 12:58 PM Pacific Time: > Following is the list of topics that will be discussed in the FESCo > meeting tomorrow at 19:30UTC (3:30pm EDT) in #fedora-meeting on > irc.freenode.net. > > = Followups = > > #topic #351 Create a policy for updates - status report on implementation > https://fedorahosted.org/fesco/ticket/351 > > #topic #382 Implementing Stable Release Vision > https://fedorahosted.org/fesco/ticket/382 > > = New business = > > #topic #440 Improve updates process to avoid "windows of doom" > https://fedorahosted.org/fesco/ticket/440 > > = New business = > > #topic #443 Proven packager request: Adam Williamson > https://fedorahosted.org/fesco/ticket/443 > > = Fedora Engineering Services tickets = > > https://fedorahosted.org/fedora-engineering-services/report/6 > > = Open Floor = > > For more complete details, please visit each individual ticket. The > report of the agenda items can be found at > https://fedorahosted.org/fesco/report/9 > > If you would like to add something to this agenda, you can reply to > this e-mail, file a new ticket at https://fedorahosted.org/fesco, > e-mail me directly, or bring it up at the end of the meeting, during > the open floor topic. > > kevin > Please include this ticket as well: #444: Review Stale & Incomplete Fedora 14 Features -+-- Reporter: poelstra |Owner: Type: task | Status: new Priority: major | Resolution: Keywords: meeting | -+-- Comment (by poelstra): * https://fedoraproject.org/wiki/Features/CryptographyInKernel * https://fedoraproject.org/wiki/Features/Go_Programming * https://fedoraproject.org/wiki/Features/Gnome3 * https://fedoraproject.org/wiki/Features/DebugPythonStacks * https://fedoraproject.org/wiki/Features/systemd * https://fedoraproject.org/wiki/Features/MultipathInstall (February 2010) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha RC Compose is At Risk
Tomorrow is the Alpha Deadline
Chances of composing the release candidate for the Fedora 14 Alpha on
Thursday are not looking good, but a little time remains. Release
Engineering cannot spin a Fedora 14 Release Candidate until this Fedora
14 Alpha Blocker is clear.
If you have any additional information about these bugs, PLEASE add it
as a comment to the bug.
https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1
615443 :: NEW :: livecd-tools :: Bruno Wolff III :: booting live images
from nightly fails (can't mount root filesystem) ::
https://bugzilla.redhat.com/show_bug.cgi?id=615443
--looks like it could be a bug in squashfs
--a fix appears to be in hand for the dependent bug:
https://bugzilla.redhat.com/show_bug.cgi?id=619020, but new packages
need to be built
597858 :: NEW :: firefox :: Gecko Maintainer :: "SELinux is preventing
firefox from making its memory writable and executable." crashes rawhide
firefox start :: https://bugzilla.redhat.com/show_bug.cgi?id=597858
--This bug has been open for over two months and has been on the blocker
list since 2010-07-22.
--Still NO feedback from the package maintainers. Recently added
caillon and martin to the CC in hopes someone will respond.
619238 :: NEW :: selinux-policy :: Daniel Walsh :: can't login to normal
F14 install - avc: denied { entrypoint } for comm="login"
path="/bin/bash" :: https://bugzilla.redhat.com/show_bug.cgi?id=619238
--Need feedback from the package maintainer. Can you drop as a line Dan?
619889 :: NEW :: xorg-x11 :: X/OpenGL Maintenance List :: X.org pegged
at 100% CPU usage after booting with systemd ::
https://bugzilla.redhat.com/show_bug.cgi?id=619889
--lpoetter is working on it.
620274 :: MODIFIED :: anaconda :: Anaconda Maintenance Team ::
pyconfig-32.h is missing, anaconda fails ::
https://bugzilla.redhat.com/show_bug.cgi?id=620274
--Need a new test compose to verify.
619947 :: MODIFIED :: gnote :: Rahul Sundaram :: gnote needs to be
rebuilt against Boost 1.44 in F14 and devel ::
https://bugzilla.redhat.com/show_bug.cgi?id=619947
617115 :: ON_QA :: livecd-tools :: Bruno Wolff III :: rawhide live spins
showing black screen instead of syslinux boot menu ::
https://bugzilla.redhat.com/show_bug.cgi?id=617115
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 has been branched!
Jesse Keating said the following on 07/30/2010 10:00 AM Pacific Time: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 07/30/2010 06:00 AM, John Poelstra wrote: >> Jesse Keating said the following on 07/29/2010 09:03 PM Pacific Time: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> https://fedoraproject.org/wiki/Branch_Freeze_Policy >>> >>> I know it's been a rough couple of days here, python-2.7 and boost >>> rebuilds creating build havoc, systemd creating some interesting >>> confusion, and dist-git to top it all off. But we'll work through it as >>> best as we can, as we always do. Onward into the future! >>> >> >> We didn't have this *freeze* reflected in the Fedora 14 schedule. Is >> this the same as the task "Branch Fedora 14 from Rawhide?" >> >> In "normal" circumstances, how long would you expect the freeze to last? >> >> John > > Well perhaps the page name is misleading, but this is the "freeze" of > being branched and using bodhi for everything. It's exactly what we did > last release, the first release of no frozen rawhide. We are "frozen" > in that if you do a build in the f14 branch, the build won't > automatically show up, you have to do a bodhi action. > Okay. I was going off an earlier conversation that I'd understood to be "we have no more 'freezes,' period, in Fedora." John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Wed 26-May Tue 03-Aug Packaging and Development (precedes Alpha) Tue 03-Aug Tue 03-Aug Alpha Change Deadline Tue 03-Aug Tue 03-Aug Software String Freeze Thu 05-Aug Thu 05-Aug Compose Alpha Candidate Fri 06-Aug Fri 06-Aug Alpha Blocker Meeting (f14alpha) #4 Wed 11-Aug Wed 11-Aug Fedora 14 Alpha Go/No-Go Meeting (17:00 EST) Thu 12-Aug Thu 12-Aug Start Stage & Sync Alpha to Mirrors Thu 12-Aug Thu 12-Aug Fedora 14 Alpha Release Readiness Meeting Thu 12-Aug Tue 17-Aug Stage & Sync Alpha to Mirrors Fri 13-Aug Fri 13-Aug Alpha Export Control Reporting Tue 17-Aug Tue 17-Aug Alpha Public Availability Have you found something that is working really well in your schedule? Or maybe you've found something you believe would work better in the future? Update the schedule retrospective page now to capture all of the important details as they happen: https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
State of the Fedora 14 Alpha Blockers + Meeting summary
REMINDER: This list must be clear by Tuesday (2010-08-03) to compose the
Fedora 14 Alpha Release Candidate on Thursday (2010-08-05). If blocker
bugs remain open our chances of release on time decrease rapidly.
Here's the latest!
615443 :: NEW :: livecd-tools :: Bruno Wolff III :: booting live images
from nightly fails (can't mount root filesystem) ::
https://bugzilla.redhat.com/show_bug.cgi?id=615443
597858 :: NEW :: firefox :: Gecko Maintainer :: "SELinux is preventing
firefox from making its memory writable and executable." crashes rawhide
firefox start :: https://bugzilla.redhat.com/show_bug.cgi?id=597858
619238 :: NEW :: selinux-policy :: Daniel Walsh :: can't login to normal
rawhide install :: https://bugzilla.redhat.com/show_bug.cgi?id=619238
618791 :: NEW :: totem :: Bastien Nocera :: totem does not build against
libpeas-devel-0.5.3-2.fc14: missing symbols:
peas_plugin_info_{s|g}et_visible ::
https://bugzilla.redhat.com/show_bug.cgi?id=618791
619913 :: NEW :: python :: Dave Malcolm :: Tracker: packages requiring
rebuild for python 2.7 :: https://bugzilla.redhat.com/show_bug.cgi?id=619913
618504 :: NEW :: xmlrpc-c :: Enrico Scholz :: Can not submit abrt bugs
:: https://bugzilla.redhat.com/show_bug.cgi?id=618504
619889 :: NEW :: systemd :: Lennart Poettering :: X.org pegged at 100%
CPU usage after booting with systemd ::
https://bugzilla.redhat.com/show_bug.cgi?id=619889
617115 :: ON_QA :: livecd-tools :: David Huff :: rawhide live spins
showing black screen instead of syslinux boot menu ::
https://bugzilla.redhat.com/show_bug.cgi?id=617115
We had a great meeting today, the summary follows:
Meeting summary
---
* attendees adamw cyberpear fcami poelcat (poelcat, 16:02:55)
* attendees adamw cyberpear fcami poelcat nirik (poelcat, 16:03:11)
* https://bugzilla.redhat.com/show_bug.cgi?id=597858 (poelcat,
16:03:57)
* ACTION: we're waiting for upstream and fesco + add a note in the bug
that we need a decision by Tuesday to compose RC on time on Thurs
(poelcat, 16:05:58)
* ACTION: we're waiting for upstream and fesco + add a note in the bug
that we need a decision by Tuesday to compose RC on time on Thurs
https://bugzilla.redhat.com/show_bug.cgi?id=597858 (poelcat,
16:06:10)
* https://bugzilla.redhat.com/show_bug.cgi?id=615443 (poelcat,
16:07:19)
* LINK:
http://wiki.sugarlabs.org/go/Talk:Features/Soas_V4/Install_Test_Table#Test_results
tests for soas (satellit__, 16:09:46)
* ACTION: : test older squashfs. squashfs maintainer will investigate
further with e2fstools maintainer helping + add reminder to bugs
that this must be resolved by Tuesday
https://bugzilla.redhat.com/show_bug.cgi?id=615443 (poelcat,
16:20:13)
* ACTION: test older squashfs. squashfs maintainer will investigate
further with e2fstools maintainer helping + add reminder to bugs
that this must be resolved by Tuesday
https://bugzilla.redhat.com/show_bug.cgi?id=615443 (poelcat,
16:20:27)
* https://bugzilla.redhat.com/show_bug.cgi?id=619020 (poelcat,
16:21:25)
* ACTION: test older squashfs. squashfs maintainer will investigate
further with e2fstools maintainer helping + add reminder to bugs
that this must be resolved by Tuesday unless there is a work around
for builds https://bugzilla.redhat.com/show_bug.cgi?id=619020
(poelcat, 16:22:01)
* https://bugzilla.redhat.com/show_bug.cgi?id=618504 (poelcat,
16:22:15)
* ACTION: this bug does not qualify as a release blocker under the
release criteria. remove f14alpha block
https://bugzilla.redhat.com/show_bug.cgi?id=618504 + add
RejectedBlocker whiteboard field (poelcat, 16:29:15)
* https://bugzilla.redhat.com/show_bug.cgi?id=619238 (poelcat,
16:30:46)
* ACTION: add as accepted F14alpha blocker "In most cases, the
installed system must boot to a functional graphical environment
without user intervention" + change component to "selinux-policy" +
try to reproduce w/ latest compose (poelcat, 16:35:56)
* https://bugzilla.redhat.com/show_bug.cgi?id=617115 (poelcat,
16:36:11)
* ACTION: need another bump + f14/rawhide build because of python 2.7
branch merge + confirm this bug is fixed and then move to
VERIFIED/CLOSED https://bugzilla.redhat.com/show_bug.cgi?id=617115
(poelcat, 16:42:51)
* open discussion (poelcat, 16:43:14)
* ACTION: need to track unfinished python rebuilds: adamw will add
totem, gnome-dvb-daemon, gnumeric, blueman, wireshark, and gnote to
'f14alpha' so we make sure they get done in time (poelcat,
16:52:10)
Minutes:
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-30/blocker-review.2010-07-30-16.00.html
Minutes (text):
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-30/blocker-review.2010-07-30-16.00.txt
Log:
http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-30/blocker-review.2010-07-30-16.00.log.html
Re: Fedora 14 has been branched!
Jesse Keating said the following on 07/29/2010 09:03 PM Pacific Time: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > https://fedoraproject.org/wiki/Branch_Freeze_Policy > > I know it's been a rough couple of days here, python-2.7 and boost > rebuilds creating build havoc, systemd creating some interesting > confusion, and dist-git to top it all off. But we'll work through it as > best as we can, as we always do. Onward into the future! > We didn't have this *freeze* reflected in the Fedora 14 schedule. Is this the same as the task "Branch Fedora 14 from Rawhide?" In "normal" circumstances, how long would you expect the freeze to last? John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Alpha Blocker Meeting #3 Friday @ 16:00 UTC
Kevin Fenzi said the following on 07/28/2010 10:08 PM Pacific Time: > On Wed, 28 Jul 2010 19:33:46 -0700 >> John Poelstra wrote: >> 597858 :: NEW :: firefox :: Gecko Maintainer :: "SELinux is >> preventing firefox from making its memory writable and executable." >> crashes rawhide firefox start :: >> https://bugzilla.redhat.com/show_bug.cgi?id=597858 --It's unclear if >> this should remain a blocker bug. FESCo discussed it briefly at >> their meeting on Tuesday and most people seemed ambivalent about the >> issue. Need a clear position statement from the maintainer or FESCo. > > I think FESCo would like to allow more time for us to convince upstream > to accept the patch or for us to come up with one they will accept. > Perhaps we could see about getting Dan Walsh to chime in upstream and > help answer questions they have. Any talk about dropping firefox > trademarks or the like is IMHO way premature. > > kevin We need a clear answer by next Tuesday, Alpha Change Deadline or we'll be blocked on creating the release candidate on Aug 5. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Blocker Meeting #3 Friday @ 16:00 UTC
Open Fedora 14 Alpha Blocker Bugs = 6 Days until Release Candidate Compose = 8 Here's the run down on the current open Fedora 14 Alpha Blocker bugs 615443 :: NEW :: livecd-tools :: David Huff :: booting live images from nightly fails (can't mount root filesystem) :: https://bugzilla.redhat.com/show_bug.cgi?id=615443 --This bug was reported on July 16, 2010, coming up on two weeks ago. Still no comments from the maintainer. 597858 :: NEW :: firefox :: Gecko Maintainer :: "SELinux is preventing firefox from making its memory writable and executable." crashes rawhide firefox start :: https://bugzilla.redhat.com/show_bug.cgi?id=597858 --It's unclear if this should remain a blocker bug. FESCo discussed it briefly at their meeting on Tuesday and most people seemed ambivalent about the issue. Need a clear position statement from the maintainer or FESCo. 617166 :: NEW :: rpm :: Panu Matilainen :: find-debuginfo.sh change for gdb index :: https://bugzilla.redhat.com/show_bug.cgi?id=617166 --It's unclear if this bug should be considered a blocker for releasing. It allegedly blocks the completion of a feature. We do not have current release criteria that addresses that scenario. 619238 :: NEW :: distribution :: Bill Nottingham :: can't login to normal rawhide install :: https://bugzilla.redhat.com/show_bug.cgi?id=619238 --Reported yesterday. Need input from maintainer. 618504 :: NEW :: xmlrpc-c :: Enrico Scholz :: Can not submit abrt bugs :: https://bugzilla.redhat.com/show_bug.cgi?id=618504 --Discussion in the comments if this is a blocker bug or not. Would be good to get some feedback from the maintainer and QA before Friday's blocker review meeting. 617115 :: ON_QA :: livecd-tools :: David Huff :: rawhide live spins showing black screen instead of syslinux boot menu :: https://bugzilla.redhat.com/show_bug.cgi?id=617115 --A fix has been submitted and testing is in process -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 Milestone Reached: Feature Freeze-2010-07-27
Jonathan MERCIER said the following on 07/28/2010 06:37 PM Pacific Time: > For D Programming Feature: > ldc is in stable repo > tango is in review https://bugzilla.redhat.com/show_bug.cgi?id=608069 by > Chen Lei. > > For guideline i do a draft and ticket is open for review: > https://fedorahosted.org/fpc/ticket/7#comment:2 > > Extra Feature: > I work for add an environnemnt for D programmer: > - i package derelict for create D application using OpenGl > * https://bugzilla.redhat.com/show_bug.cgi?id=618668 > * if someone want take this review feel free > - I try to patch DWT2 is SWT port to D, but developper will be away for > a few weeks, so i think this package will come for september (i hope > before) > - after DWT i will package poseidon an IDE using DWT > > For me D Programming Feature is done i waiting review for guideline and > tango. Some extra Feature will come later. > > best regards If the packages aren't reviewed and in rawhide by now this feature will need to wait until Fedora 15. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Milestone Reached: Feature Freeze-2010-07-27
Yesterday, July 27, 2010, we reached Feature Freeze for Fedora 14 As previously noted, at Feature Freeze it is expected that all features are *significantly* "feature complete" and ready for testing: https://fedoraproject.org/wiki/Feature_Freeze_Policy. A review of the status section on the following feature pages shows that the following feature pages have not had a recent update OR the feature does not appear to be "feature complete" based on the information provided. https://fedoraproject.org/wiki/Features/CryptographyInKernel https://fedoraproject.org/wiki/Features/MultipathInstall (last updated in February) https://fedoraproject.org/wiki/Features/D_Programming https://fedoraproject.org/wiki/Features/MeeGo_1.0 (is this really feature complete if packages still need to be reviewed?) https://fedoraproject.org/wiki/Features/Erlang_R14 https://fedoraproject.org/wiki/Features/Gnome3 (listed at 55% done) https://fedoraproject.org/wiki/Features/Spice https://fedoraproject.org/wiki/Features/Go_Programming https://fedoraproject.org/wiki/Features/EC2 https://fedoraproject.org/wiki/Features/systemd Feature owners, please update your feature page as soon as possible so that we have the most current information possible going into our first test release. Feature pages which are not updated or show the feature as significantly complete or testable by 2010-08-02 will be sent to FESCo for reconsideration. Thank you, John p.s. all feature owners have been bcc'd on this email ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Unresolved Blocker Bug Count = 3
It's "reminder guy" again with a public service announcement about the upcoming Fedora 12 Alpha Release. Some may recall that I declared my own "feature" for the Fedora 14 release (shipping Alpha, Beta, and Final on time) [1], even though I am not a package maintainer. In order for that feature to be implemented I need your help. :-) Starting today and up until the Fedora 14 Alpha blocker bug (http://bit.ly/d0weX3) has no bugs, I'll be sending out period reminders with a list of the bugs that aren't getting any love or attention. If you're interested in helping me in this effort (and it would be much appreciated), please contact me off list. Here's what we've got for today: 597858 :: NEW :: firefox :: Gecko Maintainer :: "SELinux is preventing firefox from making its memory writable and executable." crashes rawhide firefox start :: https://bugzilla.redhat.com/show_bug.cgi?id=597858 --Need some feedback from the package maintainer. No ETA when an estimated fix will be ready. 615443 :: NEW :: livecd-tools :: David Huff :: boot from liveusb fails (can't mount root filesystem) :: https://bugzilla.redhat.com/show_bug.cgi?id=615443 --Need some feedback from the package maintainer. No ETA when an estimated fix will be ready. 617115 :: ASSIGNED :: livecd-tools :: David Huff :: rawhide live spins showing black screen instead of syslinux boot menu :: https://bugzilla.redhat.com/show_bug.cgi?id=617115 --Really need some feedback from the package maintainer. No ETA when an estimated fix will be ready. If the Fedora 14 Alpha Blocker list is not clear by 2010-08-05, Release Engineering will not create a release candidate for the alpha, thus potentially delaying the release. John [1] http://poelcat.wordpress.com/2010/06/30/shipping-on-time-is-a-feature-for-fedora-14/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Feature Freeze is tomorrow (2010-07-27)
A friendly reminder that tomorrow, Tuesday, July 27, 2010, is Feature Freeze for Fedora 14. Feature Freeze means that all accepted features for Fedora 14 must be *significantly* "feature complete", ready for testing, and have a current status. https://fedoraproject.org/wiki/Feature_Freeze_Policy. https://fedoraproject.org/wiki/Features/Policy/Milestones#Feature_Freeze If you have a feature that will not be feature complete by tomorrow that is okay. Simply change the wiki page category to Category:FeatureReadyForWrangler (edit text at the very bottom of the page) and include the reason and your plans in the commit comment. I'll see that your feature is targeted for Fedora 15 instead. Thank you, John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Upcoming Fedora 14 Tasks
Start End Name Mon 26-Jul Fri 30-Jul Daily Review & Notification of Open Alpha Blocker Bugs Tue 27-Jul Tue 27-Jul Spins Freeze--All Fedora 14 Spins Identified Tue 27-Jul Tue 27-Jul Branch Fedora 14 from Rawhide Tue 27-Jul Tue 27-Jul Feature Freeze (Testable|Complete) Tue 27-Jul Tue 27-Jul Orphan Rawhide Packages Thu 29-Jul Thu 29-Jul Create Alpha Test Compose (TC) Fri 30-Jul Fri 30-Jul Alpha Blocker Meeting (f14alpha) #3 Tue 03-Aug Tue 03-Aug Software String Freeze Tue 03-Aug Tue 03-Aug Alpha Change Deadline Thu 05-Aug Thu 05-Aug Compose Alpha Candidate Fri 06-Aug Fri 06-Aug Alpha Blocker Meeting (f14alpha) #4 Have you found something that is working really well in your schedule? Or maybe you've found something you believe would work better in the future? Update the schedule retrospective page now to capture all of the important details as they happen: https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Blocker Meeting #2 Recap
Date: 2010-07-23 Meeting summary --- * roll call (poelcat, 16:00:07) * https://bugzilla.redhat.com/show_bug.cgi?id=597858 (poelcat, 16:04:23) * LINK: https://bugzilla.mozilla.org/show_bug.cgi?id=506693 (mcepl, 16:08:09) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=597858 approved blocker, remove F14Blocker, request feedback from maintainer (poelcat, 16:09:48) * https://bugzilla.redhat.com/show_bug.cgi?id=613695 (poelcat, 16:13:14) * https://bugzilla.redhat.com/show_bug.cgi?id=597858 (poelcat, 16:16:08) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=597858 approved blocker, remove F14Blocker, request feedback from maintainer, contact Martin Stránský to get a better idea of the future of this bug (poelcat, 16:17:16) * https://bugzilla.redhat.com/show_bug.cgi?id=613695 (poelcat, 16:18:01) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=613695 should be back in ASSIGNED, or VERIFIED->CLOSED next week (poelcat, 16:19:14) * https://bugzilla.redhat.com/show_bug.cgi?id=615443 (poelcat, 16:19:36) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=615443 approved blocker, add jkeating to CC, monitor the nightlies for the next week and try to keep track of exactly what's broken in each (poelcat, 16:27:04) * we've certainly confirmed the problem exists and is widespread ... need some love to further isolate+diagnose (poelcat, 16:27:15) * https://bugzilla.redhat.com/show_bug.cgi?id=616090 (poelcat, 16:29:12) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=616090 jlaska will retest this with the new rawhide acceptance images when they land (poelcat, 16:30:52) * #topic https://bugzilla.redhat.com/show_bug.cgi?id=617115 (poelcat, 16:31:28) * https://bugzilla.redhat.com/show_bug.cgi?id=617115 (jlaska, 16:38:32) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=617115 ApprovedBlocker, add "the world" to the CC list so we can get some more help attention and help on this critical issue (poelcat, 16:39:24) * open discussion (poelcat, 16:39:40) Meeting ended at 16:45:53 UTC. Action Items * https://bugzilla.redhat.com/show_bug.cgi?id=597858 approved blocker, remove F14Blocker, request feedback from maintainer * https://bugzilla.redhat.com/show_bug.cgi?id=597858 approved blocker, remove F14Blocker, request feedback from maintainer, contact Martin Stránský to get a better idea of the future of this bug * https://bugzilla.redhat.com/show_bug.cgi?id=613695 should be back in ASSIGNED, or VERIFIED->CLOSED next week * https://bugzilla.redhat.com/show_bug.cgi?id=615443 approved blocker, add jkeating to CC, monitor the nightlies for the next week and try to keep track of exactly what's broken in each * https://bugzilla.redhat.com/show_bug.cgi?id=616090 jlaska will retest this with the new rawhide acceptance images when they land * https://bugzilla.redhat.com/show_bug.cgi?id=617115 ApprovedBlocker, add "the world" to the CC list so we can get some more help attention and help on this critical issue Action Items, by person --- * jlaska * https://bugzilla.redhat.com/show_bug.cgi?id=616090 jlaska will retest this with the new rawhide acceptance images when they land * **UNASSIGNED** * https://bugzilla.redhat.com/show_bug.cgi?id=597858 approved blocker, remove F14Blocker, request feedback from maintainer * https://bugzilla.redhat.com/show_bug.cgi?id=597858 approved blocker, remove F14Blocker, request feedback from maintainer, contact Martin Stránský to get a better idea of the future of this bug * https://bugzilla.redhat.com/show_bug.cgi?id=613695 should be back in ASSIGNED, or VERIFIED->CLOSED next week * https://bugzilla.redhat.com/show_bug.cgi?id=615443 approved blocker, add jkeating to CC, monitor the nightlies for the next week and try to keep track of exactly what's broken in each * https://bugzilla.redhat.com/show_bug.cgi?id=617115 ApprovedBlocker, add "the world" to the CC list so we can get some more help attention and help on this critical issue Minutes: http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-23/fedora-bugzappers.2010-07-23-16.00.html Minutes (text): http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-23/fedora-bugzappers.2010-07-23-16.00.txt Log: http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-23/fedora-bugzappers.2010-07-23-16.00.log.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[Test-Announce] Fedora 14 Alpha Blocker Bug Review Meeting #1 2010-07-23 @ 16:00 UTC (12 PM EST)
When: Friday, 2010-07-23 @ 16:00 UTC (12 PM EST)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Friday is the
SECOND blocker bug review meeting for the Fedora 14 Alpha.
Here are the current bugs listed as blocking the Alpha release. We'll be
discussing all of these to determine if they meet the criteria, should
stay on the list, and are getting the attention they need:
615443 :: NEW :: livecd-tools :: David Huff :: boot from liveusb fails
(can't mount root filesystem) ::
https://bugzilla.redhat.com/show_bug.cgi?id=615443
613695 :: MODIFIED :: anaconda :: Martin Gracik :: ImportError: cannot
import name GObject :: https://bugzilla.redhat.com/show_bug.cgi?id=613695
616090 :: MODIFIED :: anaconda :: Anaconda Maintenance Team :: Rescue
mode fails :: https://bugzilla.redhat.com/show_bug.cgi?id=616090
If you are the owner of these bugs, kindly update the comments with your
feedback as to whether you believe it is a blocker and what your plans
for fixing the bug are.
Do you have an issue you believe should be fixed before the Fedora 14
Alpha ships? Please consider the following criteria when escalating an
issue: https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria
Our goal for Fedora 14, is to continue to make sure the release criteria
matches up with our 'gut feelings' for what needs to be fixed before
releasing. So, if you see an issue that you think should be a blocker
but doesn't meet the criteria, please add it as a blocker and mention at
the meeting that the criteria does't cover it. Thanks!
To promote a bug for consideration as a blocker, simply add 'F14Alpha'
to the "Blocks" field of the bug you are concerned about. A similar
technique works for marking bugs as blocking the Beta or Final release,
if appropriate, by using 'F14Beta' and 'F14Blocker' respectively.
Hope to see everyone on Friday.
John
The command used to generate the list of bugs above is:
$ bugzilla query --blocked=611990 \
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
\
--outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
%{assigned_to} :: %{summary} :: %{url}"
___
test-announce mailing list
test-annou...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Blocker Bug Review Meeting #2, 2010-07-23 @ 16:00 UTC (12 PM EST)
When: Friday, 2010-07-23 @ 16:00 UTC (12 PM EST)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Friday is the
SECOND blocker bug review meeting for the Fedora 14 Alpha.
Here are the current bugs listed as blocking the Alpha release. We'll be
discussing all of these to determine if they meet the criteria, should
stay on the list, and are getting the attention they need:
615443 :: NEW :: livecd-tools :: David Huff :: boot from liveusb fails
(can't mount root filesystem) ::
https://bugzilla.redhat.com/show_bug.cgi?id=615443
613695 :: MODIFIED :: anaconda :: Martin Gracik :: ImportError: cannot
import name GObject :: https://bugzilla.redhat.com/show_bug.cgi?id=613695
616090 :: MODIFIED :: anaconda :: Anaconda Maintenance Team :: Rescue
mode fails :: https://bugzilla.redhat.com/show_bug.cgi?id=616090
If you are the owner of these bugs, kindly update the comments with your
feedback as to whether you believe it is a blocker and what your plans
for fixing the bug are.
Do you have an issue you believe should be fixed before the Fedora 14
Alpha ships? Please consider the following criteria when escalating an
issue: https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria
Our goal for Fedora 14, is to continue to make sure the release criteria
matches up with our 'gut feelings' for what needs to be fixed before
releasing. So, if you see an issue that you think should be a blocker
but doesn't meet the criteria, please add it as a blocker and mention at
the meeting that the criteria does't cover it. Thanks!
To promote a bug for consideration as a blocker, simply add 'F14Alpha'
to the "Blocks" field of the bug you are concerned about. A similar
technique works for marking bugs as blocking the Beta or Final release,
if appropriate, by using 'F14Beta' and 'F14Blocker' respectively.
Hope to see everyone on Friday.
John
The command used to generate the list of bugs above is:
$ bugzilla query --blocked=611990 \
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
\
--outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
%{assigned_to} :: %{summary} :: %{url}"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Reminder: Fedora 14 Feature Freeze is Next Week (2010-07-27)
It's hard to believe, but the window for full blown feature development closes soon. A friendly reminder that next Tuesday, July 27, 2010 is Feature Freeze for Fedora 14. Feature Freeze means that all accepted feature for the release are *significantly* "feature complete", ready for testing, and have a current status. https://fedoraproject.org/wiki/Feature_Freeze_Policy. https://fedoraproject.org/wiki/Features/Policy/Milestones#Feature_Freeze If you have any questions about what this means, please ask now. Features which are not significantly feature complete at Feature Freeze will be be allowed to remain on an exception basis by FESCo or deferred to Fedora 15. Thank you, John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Schedule Reminder
Start End Name Wed 26-May Tue 03-Aug Packaging and Development (precedes Alpha) Thu 22-Jul Thu 22-Jul Create Installable Images for QA testing #3 Fri 23-Jul Fri 23-Jul Alpha Blocker Meeting (f14alpha) #2 Mon 26-Jul Fri 30-Jul Daily Review & Notification of Open Alpha Blocker Bugs Tue 27-Jul Tue 27-Jul Orphan Rawhide Packages Tue 27-Jul Tue 27-Jul Feature Freeze (Testable|Complete) Tue 27-Jul Tue 27-Jul Branch Fedora 14 from Rawhide Tue 27-Jul Tue 27-Jul Spins Freeze--All Fedora 14 Spins Identified Thu 29-Jul Thu 29-Jul Create Alpha Test Compose (TC) Fri 30-Jul Fri 30-Jul Alpha Blocker Meeting (f14alpha) #3 Tue 03-Aug Tue 03-Aug Alpha Change Deadline Tue 03-Aug Tue 03-Aug Software String Freeze Have you found something that is working really well in your schedule? Or maybe you've found something you believe would work better in the future? Update the schedule retrospective page now to capture all of the important details as they happen: https://fedoraproject.org/wiki/Fedora_14_Schedule_Retrospective -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Blocker Meeting #1 Recap 2010-07-16
Meeting summary --- * LINK: https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1 (adamw, 16:03:18) * https://bugzilla.redhat.com/show_bug.cgi?id=596985 (poelcat, 16:05:35) * LINK: http://tinyurl.com/2apxuo7 (adamw, 16:05:49) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=596985 remove from F14Alpha blocker--will reconsider if this bug impact turns out to be more widespread (poelcat, 16:11:18) * https://bugzilla.redhat.com/show_bug.cgi?id=613695 (poelcat, 16:12:04) * LINK: https://fedoraproject.org/wiki/Test_Results:Fedora_14_Pre-Alpha_Rawhide_Acceptance_Test_1 (adamw, 16:16:26) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=613695 request more information to determine if this bug breaks criterion or not (poelcat, 16:22:05) * https://bugzilla.redhat.com/show_bug.cgi?id=613817 (poelcat, 16:22:20) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=613817 keep as blocker unless feedback from devel is otherwise (poelcat, 16:31:45) * https://bugzilla.redhat.com/show_bug.cgi?id=614488 (poelcat, 16:32:12) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=614488 leave as blocking f14alpha, need additional information (poelcat, 17:01:25) * https://bugzilla.redhat.com/show_bug.cgi?id=614538 (poelcat, 17:02:31) * ACTION: https://bugzilla.redhat.com/show_bug.cgi?id=614538 accepted as a blocker (poelcat, 17:11:26) http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-16/fedora-bugzappers.2010-07-16-16.02.html 10:13:23 < zodbot> Minutes (text): http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-16/fedora-bugzappers.2010-07-16-16.02.txt 10:13:23 < zodbot> Log: http://meetbot.fedoraproject.org/fedora-bugzappers/2010-07-16/fedora-bugzappers.2010-07-16-16.02.log.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Alpha Blocker Bug Review Meeting #1 2010-07-16 @ 16:00 UTC (12 PM EST)
When: Friday, 2010-07-16 @ 16:00 UTC (12 PM EST)
Where: #fedora-bugzappers on irc.freenode.net
It's that time again: blocker bug review meeting time! Friday is the
FIRST blocker bug review meeting for the Fedora 14 Alpha.
Here are the current bugs listed as blocking the Alpha release. We'll be
discussing all of these to determine if they meet the criteria, should
stay on the list, and are getting the attention they need:
614488 :: NEW :: anaconda :: Anaconda Maintenance Team :: Dropped
vesamenu.c32 from rawhide boot.iso ::
https://bugzilla.redhat.com/show_bug.cgi?id=614488
614538 :: NEW :: firstboot :: Martin Gracik :: firstboot does not
start after manual install ::
https://bugzilla.redhat.com/show_bug.cgi?id=614538
613695 :: ASSIGNED :: anaconda :: Martin Gracik :: ImportError:
cannot import name GObject ::
https://bugzilla.redhat.com/show_bug.cgi?id=613695
If you are the owner of these bugs, kindly update the comments with your
feedback as to whether you believe it is a blocker and what your plans
for fixing the bug are.
Do you have an issue you believe should be fixed before the Fedora 14
Alpha ships? Please consider the following criteria when escalating an
issue: https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria
Our goal for Fedora 14, is to continue to make sure the release criteria
matches up with our 'gut feelings' for what needs to be fixed before
releasing. So, if you see an issue that you think should be a blocker
but doesn't meet the criteria, please add it as a blocker and mention at
the meeting that the criteria does't cover it. Thanks!
To promote a bug for consideration as a blocker, simply add 'F14Alpha'
to the "Blocks" field of the bug you are concerned about. A similar
technique works for marking bugs as blocking the Beta or Final release,
if appropriate, by using 'F14Beta' and 'F14Blocker' respectively.
Hope to see everyone on Friday.
John
The command used to generate the list of bugs above is:
bugzilla query --blocked=611990 \
--bug_status=NEW,ASSIGNED,NEEDINFO,ON_DEV,MODIFIED,POST,ON_QA,FAILS_QA,PASSES_QA,REOPENED,VERIFIED,RELEASE_PENDING
\
--outputformat="%{bug_id} :: %{bug_status} :: %{component} ::
%{assigned_to} :: %{summary} :: %{url}"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Feature Submission deadline is tomorrow (2010-07-13)
The Fedora 14 Feature Submission Deadline is TOMORROW. After tomorrow, newly submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo. Accepted Fedora 14 features so far: https://fedoraproject.org/wiki/Releases/14/FeatureList Thank you, John More information: Fedora 14 Schedule: https://fedoraproject.org/wiki/Releases/14/Schedule Fedora Feature Process: https://fedoraproject.org/wiki/Features/Policy ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Schedule Reminder
Start End Name Wed 26-May Tue 03-Aug Packaging and Development (precedes Alpha) Tue 13-Jul Tue 13-Jul Feature Submission Deadline Tue 13-Jul Tue 13-Jul Custom Spins Submission Deadline Thu 15-Jul Thu 15-Jul Create Installable Images for QA testing #2 Fri 16-Jul Fri 16-Jul Alpha Blocker Meeting (f14alpha) #1 Thu 22-Jul Thu 22-Jul Create Installable Images for QA testing #3 Fri 23-Jul Fri 23-Jul Alpha Blocker Meeting (f14alpha) #2 Mon 26-Jul Fri 30-Jul Daily Review & Notification of Open Alpha Blocker Bugs Tue 27-Jul Tue 27-Jul Spins Freeze--All Fedora 14 Spins Identified Tue 27-Jul Tue 27-Jul Feature Freeze (Testable|Complete) Tue 27-Jul Tue 27-Jul Orphan Rawhide Packages Tue 27-Jul Tue 27-Jul Branch Fedora 14 from Rawhide -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora 14 test release blocker bugs
James Laska said the following on 07/07/2010 05:43 AM Pacific Time: > On Tue, 2010-07-06 at 17:22 -0700, Adam Williamson wrote: >> On Tue, 2010-07-06 at 17:10 -0700, John Poelstra wrote: >>> Hard to believe, but Fedora QA starts its "Pre-Alpha Rawhide Acceptance >>> Test Plan" testing this Thursday (2010-07-08). >>> >>> We've run out of time and run way to implement a new means of tracking >>> blocker bugs for Fedora--previously discussed in the context of using >>> flags in Bugzilla. We'll continue to use the same process we've used >>> for past releases. >> >> Erm, really? We could throw the existing proposal in in an afternoon if >> we wanted to. I was fine with it. Jesse, what was your plan here? > > If there is a solution that addresses the problems identified during > F-13, and it can be implemented in *short* time. It would be > compelling. I'm a fan of solving problems with tooling, but I'm not > convinced that is where our big investment should be for the upcoming > release, or that it fully addresses the problems encountered during > F-13. > > I outlined 3 basic blocker bug process recommendations that are > attainable+sustainable and address the problems we had during F-13 [1]. > If someone feels flags are the better solution, and can develop a > proposal for creating bugzilla flags, the policy for managing them, and > bot automation to enforce them, I'm sure we'd all be happy to provide > feedback. > Long term I think flags will help streamline our process. With the first Alpha blocker bug meetings starting next Friday it doesn't make sense for Fedora 14. I agree there is probably enough time to write a proposal for how it could all work, but not enough time to get feedback on the proposal and definitely not enough time to implement and test everything before using it. We can get better near term impact by addressing the recommendations from the QA retrospective around bugzilla. I'm working on two of the tickets. John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 test release blocker bugs
Hard to believe, but Fedora QA starts its "Pre-Alpha Rawhide Acceptance Test Plan" testing this Thursday (2010-07-08). We've run out of time and run way to implement a new means of tracking blocker bugs for Fedora--previously discussed in the context of using flags in Bugzilla. We'll continue to use the same process we've used for past releases. I've created tracker bugs for the Fedora 14 Alpha and Beta releases: Fedora 14 Alpha = F14Alpha = https://bugzilla.redhat.com/show_bug.cgi?id=611990 Fedora 14 Beta = F14Beta = https://bugzilla.redhat.com/show_bug.cgi?id=611990 Other tracker bugs for Fedora 14 are at: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers#Fedora_14 The criteria for considering a bug a release blocker is at: Alpha--http://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria#Alpha_Blocker_Bugs Beta--http://fedoraproject.org/wiki/Fedora_14_Beta_Release_Criteria#Beta_Blocker_Bugs John -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Feature Submission Deadline is One Week Away (2010-07-13)
This email serves as the last reminder for the Fedora 14 Feature Submission Deadline--Tuesday, July 13, 2010. After this date newly submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo. Accepted Fedora 14 features so far: https://fedoraproject.org/wiki/Releases/14/FeatureList If you are a current feature page owner, thank you for submitting your feature for Fedora 14 and contributing to the next release of Fedora. If you haven't updated your feature page in the last month it would be a great help to every one if you would do so now. As we start to reach deadlines and test releases for Fedora 14, more and more people will query the feature pages. We'd love to know that what they find is current and correct. Thank you, John More information: Fedora 14 Schedule: https://fedoraproject.org/wiki/Releases/14/Schedule Fedora Feature Process: https://fedoraproject.org/wiki/Features/Policy ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Schedule Reminder
Start End Name Wed 26-May Tue 03-Aug Packaging and Development (precedes Alpha) Tue 06-Jul Tue 06-Jul Feature Submission Deadline One Week away Thu 08-Jul Thu 08-Jul Create Installable Images for QA testing #1 Tue 13-Jul Tue 13-Jul Custom Spins Submission Deadline Tue 13-Jul Tue 13-Jul Feature Submission Deadline Thu 15-Jul Thu 15-Jul Create Installable Images for QA testing #2 Fri 16-Jul Fri 16-Jul Alpha Blocker Meeting (f14alpha) #1 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Feature Submission Deadline in Two Weeks
Another friendly and brief reminder that the deadline for new features for Fedora 14 is July 13, 2010. A list of features accepted so far: https://fedoraproject.org/wiki/Releases/14/FeatureList Wiki pages explaining the feature process: https://fedoraproject.org/wiki/Features/Policy Please send any other questions about the feature process or this deadline by replying to this message on the list. John ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Schedule Tasks
Start End Name Wed 26-May Tue 03-Aug Packaging and Development (precedes Alpha) Tue 29-Jun Tue 29-Jun Feature Submission Deadline Two Weeks away Tue 06-Jul Tue 06-Jul Feature Submission Deadline One Week away Thu 08-Jul Thu 08-Jul Create Installable Images for QA testing #1 Tue 13-Jul Tue 13-Jul Feature Submission Deadline Tue 13-Jul Tue 13-Jul Custom Spins Submission Deadline -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Feature Submission Deadline in Three Weeks
It is hard to believe, but it is true, we are almost a month into Fedora 14 development. This email serves as a friendly reminder that the deadline for submitting new features for Fedora 14 is Tuesday, July 13, 2010. After this date newly submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo. Accepted Fedora 14 features so far: https://fedoraproject.org/wiki/Releases/14/FeatureList If you are are current feature page owner, thank you for already submitting your feature for Fedora 14 and contributing to the next release of Fedora. If you haven't updated your feature page in the last month it would be a great help to every one if you would do so. As we start to reach deadlines and test releases for Fedora 14, more and more people query the feature pages and we'd love to know that what they find is current and correct. Thank you! John More information: Fedora 14 Schedule: https://fedoraproject.org/wiki/Releases/14/Schedule Fedora Feature Process: https://fedoraproject.org/wiki/Features/Policy ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora 14 Schedule
Start End Name Wed 26-May Tue 03-Aug Packaging and Development (precedes Alpha) Tue 22-Jun Tue 22-Jun Request Feature Status Updates + Remind Submit Deadline Tue 29-Jun Tue 29-Jun Feature Submission Deadline Two Weeks away Tue 06-Jul Tue 06-Jul Feature Submission Deadline One Week away -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
