March 2009 - devel-announce - Fedora Mailing-Lists

by James Laska

Greetings testers, Apologies for the late notice. We had a slight change in the plan for this weeks test day. The focus will be on upcoming Intel graphics driver changes. Planning for this test day began with an eye towards validating the upcoming F11 Intel KMS feature [1]. However, after some great feedback from developer Kristian Høgsberg, the scope has changed. With Kristian's input, Adam Williamson crafted a wiki page [2] and test cases designed to stress Intel graphics support and DRI2 [3]. So if you have an Intel graphics adapter ... # /sbin/lspci | grep -q VGA.*Intel && echo "Join Fedora Test Day" I invite you to join #fedora-qa this Thursday, March 12, 2009 to share your Intel graphics test results. Stay tuned for more details at https://fedoraproject.org/wiki/QA/Test_Days/2009-03-12. Thanks, James [1] https://fedoraproject.org/wiki/Features/IntelKMS [2] https://fedoraproject.org/wiki/QA/Test_Days/2009-03-12 [3] https://fedoraproject.org/wiki/Features/DRI2

15 years, 1 month

1
0
0 / 0

Fedora 11 Blocker Review Day :: Monday 2009-03-16

by John Poelstra

The BugZappers will be hosting a blocker review day on Monday, March 16, 2009. The purpose of this meeting will be to: 1) review all of the bugs on the Fedora 11 Beta Blocker list to see if they belong there 2) assess how things are looking for shipping the Fedora 11 Beta on time based on what remains on the list It would be helpful if lead package maintainers for each of the groups could join us or be in the channel should questions arise. WHEN: Monday, March 16, 2009 @ 14:00 UTC (10 AM EDT) and going as long as we need to WHERE: irc.freenode.net #fedora-bugzappers Fedora 11 Beta Blocker: https://bugzilla.redhat.com/showdependencytree.cgi?id=476774&hide_resolved=1 Approximately 1,000 rawhide bugs that have not been triaged for potential blocker status may warrant consideration as well. Those bugs are found here: http://tinyurl.com/6llac8 Other tracker bugs of interest for Fedora 11 are here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers See you Monday! John

15 years, 1 month

1
0
0 / 0

Heads-Up: WebKit soname bump (ABI changes); rebuilds required

by Peter Gordon

Hi, all. I've just committed an update to WebKit in rawhide for the recently released WebKitGTK+ 1.1.1, which contains some ABI updates; and the library soname has been bumped accordingly upstream: "libwebkit-1.0.so.1" to "libwebkit-1.0.so.2". (The API has not changed; only the binary interface is modified.) According to repoquery, the following packages (maintainers CC-ed) depend on WebKit and will therefore need a rebuild for this change. * anjuta * evolution-rss * gimp * kazehakase * libproxy * liferea * midori * pywebkitgtk I will take care of Midori, and any other packages whose maintainers would like me to bump and rebuild in their stead. If there are any concerns or problems with rebuilding, please do not hesitate to let me know. Thanks, and Regards. -- Peter Gordon (codergeek42) <peter(a)thecodergeek.com> Who am I? :: http://www.thecodergeek.com/about-me

15 years, 1 month

1
0
0 / 0

PLEASE READ: provenpackager reseed

by Jon Stanley

At the FESCo meeting that took place on 3/6/2009, it was decided that on Monday, 3/9/2009, the 'provenpackager' group would be emptied and repopulated with only sponsors in the 'packager' group, who would be given user status in the provenpackager group. This was done for a few reasons: 1) The initial method of seeding the provenpackager group was seen by some to be arbitrary - any packager who owned 8 or more packages was admitted to the group without question. 2) Due to 1, the provenpackager group did not have the desired effect - the removal of ACL's on all but maybe a few packages. In order for anyone else that is not currently a sponsor to be admitted to the group, a process very similar to new sponsor acceptance (however a distinct process) will be put into effect: 1) The user makes their desire to be a member of provenpackager known to FESCo (they can do this in really any way - mailing list, IRC, file a ticket, etc) 2) Much as is the process for new sponsors, a discussion will take place for 1 week on the sponsors list. 3) Based on the input from step 2, FESCo will vote on the individual in their regular meeting. Also, any user that becomes a sponsor will also be added to the 'provenpackager' group. It is anticipated that the volume of requests at first will be moderately large. This is expected and will be dealt with in the normal course of business.

15 years, 1 month

1
0
0 / 0

Reminder: Fedora 11 Beta/String freeze

by Dennis Gilmore

This is a reminder that the Fedora 11 schedule ( http://fedoraproject.org/wiki/Releases/11/Schedule ) calls for the Beta and string freeze to happen on Monday March 11 2009. What does this mean for you? It means anything that needs translations needs to be done by COB monday. This is a blocking Freeze any packages you need included in the Beta release must be requested via release engineering https://fedorahosted.org/rel-eng Please be mindful of this when making changes to packages. Dennis For FESCo

15 years, 1 month

1
1
0 / 0

Fedora 11 Beta Freeze coming

by Jesse Keating

The Fedora 11 Beta Freeze is coming. It is scheduled for Tuesday, March 10th. They way we've historically enacted the beta freeze is to tag the content in that day's rawhide into the freeze tag. That is, what gets reported as rawhide-20090310 is the frozen content. As such, your builds need to be complete by 0600 UTC March 10 2009 in order to be in the Beta, without a special request. https://fedoraproject.org/wiki/Beta_Freeze_Policy covers the freeze policy. Bug tracking of important Beta issues is done at https://bugzilla.redhat.com/show_bug.cgi?id=F11Beta -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating

15 years, 1 month

1
0
0 / 0

Please update your Feature Page ASAP

by John Poelstra

To increase our chances of a successful and solid Fedora 11 release, all new features should now be significantly complete and in a "testable" condition. We need the help of a few remaining feature owners to bring their pages current or target them for Fedora 12. According to a review of all the feature pages, the following features have not been updated recently or are not 100% complete. They need to be updated by the end of tomorrow (2009-03-05). https://fedoraproject.org/wiki/Features/20SecondStartup https://fedoraproject.org/wiki/Features/Archer https://fedoraproject.org/wiki/Features/ArchitectureSupport https://fedoraproject.org/wiki/Features/CrashCatcher https://fedoraproject.org/wiki/Features/Empathy https://fedoraproject.org/wiki/Features/Firefox_3.1 https://fedoraproject.org/wiki/Features/gcc4.4 https://fedoraproject.org/wiki/Features/GFS2Stable https://fedoraproject.org/wiki/Features/IBus https://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment https://fedoraproject.org/wiki/Features/liblvm https://fedoraproject.org/wiki/Features/MinimalPlatform https://fedoraproject.org/wiki/Features/NouveauAsDefault https://fedoraproject.org/wiki/Features/NouveauModesetting https://fedoraproject.org/wiki/Features/SSSD https://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control https://fedoraproject.org/wiki/Features/EFI https://fedoraproject.org/wiki/Features/VirtVNCAuth If you believe your feature is substantially complete and testable state for Fedora 11, please perform the following: 1) Update the % complete and "last updated" date 2) In the status section please also include what remains to be completed including your realistic assessment as to whether it is possible to complete by Final Feature Freeze on 2009-04-14. I will be sending a list features with no update to FESCo tomorrow evening to be reviewed at their 2009-03-06 meeting. At that meeting I will recommend that feature pages which are not current be dropped from the Fedora 11 feature list-- https://fedoraproject.org/wiki/Releases/11/FeatureList If you believe your feature is not ready for Fedora 11, that is okay :) Fedora 12 is only a few short months away. If you would like to target your feature for Fedora 12, please change the page category to "Cateogory:FeatureReadyForWranger". If your feature will not be ready for Fedora 11 and you aren't sure what is going to happen to it: 1) Please change the category of your page to Category:FeaturePageIncomplete 2) Remove Fedora 11 as the targeted release. I have a watch on all the feature pages. Thank you for your help, John p.s. this is a follow-up message to: https://www.redhat.com/archives/fedora-devel-announce/2009-February/msg00... p.s.s individual feature owners have also been bcc on this email

15 years, 1 month

1
0
0 / 0

Fedora Test Day - Anaconda Storage Rewrite

by James Laska

Greetings testers, This week's Test Day will focus on a quiet but important feature. If done properly you won't know anything changed. The Fedora installers (anaconda) concept of managing storage is changing from the ground up. As stated in the Feature scope [1]: "All of anaconda's code for creating and configuring disk partitions, LVM, mdraid, dmraid, multipath, iSCSI, LUKS devices, and filesystems is being rewritten." Dave Lehman and Chris Lumens from the anaconda development team will be available for discussion+guidance. Given the raw nature of the code at this point, rather than outlining specific detailed test cases ... Robert Williams is pulling together a set of test areas with some exploratory test guidance. We don't expect all paths to be fully functional. We need your help collecting data on the myriad storage environments you run anaconda in. This data will be used to re-factor future installer storage+partitioning testing and help identify any development gaps. Please join #fedora-qa this Thursday, March 5, 2009 to get some hands on time with the revamped anaconda storage code. Follow the action at https://fedoraproject.org/wiki/QA/Test_Days/2009-03-05. Thanks, James [1] https://fedoraproject.org/wiki/Features/AnacondaStorageRewrite

15 years, 1 month

1
0
0 / 0

qt-4.5.0 license change to include LGPLv2

by Rex Dieter

With qt-4.5.0 final release today, QtSoftware has implemented the planned licensing change to include LGPLv2. In practical fedora packaging/license terms, qt went from License: GPLv3 with exceptions or GPLv2 with exceptions to License: GPLv3 with exceptions or LGPLv2 with exceptions which is more permissive. See also: http://www.qtsoftware.com/products/licensing -- Rex

15 years, 1 month

1
0
0 / 0

Purging the orphans

by Jesse Keating

It's that time of the release cycle, where we purge the unblocked orphans from rawhide. I just wrote a script to easily discover these (only takes a few seconds). I haven't yet fed these into any useful repoclosure runs though. First I'd like to just post the list and give folks a chance to pick them up before spending more time on it. Orphans that remain unblocked just before Beta freeze will be blocked, and will not be shipped with F11. Unblocked orphan 8Kingdoms Unblocked orphan abcde Unblocked orphan aspell-sk Unblocked orphan cd-discid Unblocked orphan codeina Unblocked orphan compat-libosip2 Unblocked orphan cvs2cl Unblocked orphan cvsps Unblocked orphan fluxstyle Unblocked orphan freetennis Unblocked orphan gkrellm Unblocked orphan gkrellm-volume Unblocked orphan itext Unblocked orphan jabbin Unblocked orphan kbackup Unblocked orphan libeXosip2 Unblocked orphan libid3tag Unblocked orphan libmodplug Unblocked orphan libsamplerate Unblocked orphan mach Unblocked orphan moodss Unblocked orphan moomps Unblocked orphan mrxvt Unblocked orphan nautilus-share Unblocked orphan pekwm Unblocked orphan pikdev Unblocked orphan pikloops Unblocked orphan python-quixote Unblocked orphan python-simpletal Unblocked orphan python-tpg Unblocked orphan pytz Unblocked orphan redet Unblocked orphan redet-doc Unblocked orphan SDL_image Unblocked orphan svn2cl -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating

15 years, 1 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce March 2009