devel-announce April 2008

devel-announce@lists.fedoraproject.org

12 participants
25 discussions

Change in Board composition
by Paul W. Frields 21 Apr '08

21 Apr '08

Since the Fedora Board originally formed in 2006, the Fedora Project has changed quite a bit. We now have about two-thirds of our packages maintained by volunteer community members. Our technical steering committee, FESCo, is made up of a roughly even mix of volunteers and Red Hat employees. This community has developed and enforced its own high standards and done it in an open and transparent fashion in the best tradition of open source. And through all of these efforts, we've helped build a community of contributors -- not just people who *use* Fedora, but people who *give back* to the open source ecosystem, and their fellow human beings. I'm very pleased to report that with the post-Fedora 9 election, the Board composition will be a better reflection of the strides our community has made in self-organization and self-governance, and of our healthy partnership with Red Hat. Starting with this election, the Board will move to a composition of five (5) community-elected seats and four (4) Red Hat-appointed seats. This is an issue I've been advocating over the past couple of weeks, and I'm delighted to be able to make this change following my first release as Fedora Project Leader. I look at this as a significant step in the evolution of the Board and Fedora's governance overall. The rest of the Board and I look forward to the elections, and to the continued opportunity to serve everyone in the Fedora community. We appreciate the support and the trust you give us, and will always work hard to earn it. Thanks for reading! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

1 0

Rawhide Builds coming later
by Mike McGrath 20 Apr '08

20 Apr '08

We're slowly narrowing down some issues we've been seeing. As a result I'm in the process of picking possible trigger apps (apps we think may be causing the outages to occur) and moving them to times when we're not all asleep. As a result the rawhide build script will be moved 4 hours later then it currently is. -Mike

1 0

Outage Notification - 2008-04-18 19:05 UTC
by Toshio Kuratomi 18 Apr '08

18 Apr '08

We experienced an unplanned outage of the buildsystem starting at 19:05 UTC and being resolved by 19:51 UTC. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d 'YYYY-MM-DD HH:MM UTC' Affected Services: Websites Buildsystem Unaffected Services: CVS / Source Control Database DNS Mail Torrent Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/510 Reason for Outage: One of the xen servers crashed, taking all with it all the guests on it. The koji hub is the only non-load balanced application on that server so it was the only service that suffered an outage. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.

1 0

Fedora 9 Release date slipping by two weeks (new date, May 13)
by Jesse Keating 17 Apr '08

17 Apr '08

At today's regularly scheduled meeting, the Fedora Engineering Steering Committee (FESCo) decided that Fedora 9 release will be slipping by exactly two weeks. Because of other slippage, coupled with some technical difficulties during this previous week, our Preview Release was unexpectedly stalled. The Preview Release is where we expect to catch all manner of last-minute bugs, do very heavy QA, and otherwise perform all the final spit-and-polish. There needs to be sufficient time between the PR and the release for testers to find and report issues. There are less than two weeks remaining until the original target date of April 29th. About a week before that date we have to have everything locked and loaded for distribution by our mirrors. That small a timeframe would then make the Preview Release -- normally a very important part of our release schedule -- nearly useless. This slip is not intended to make room for more changes, it is only intended to make room for fixing the things we already know about, and allowing new things to be found, and evaluated as release blocking, and fixed. There are also a fair number of bugs we think we've already fixed, but need wider audience testing to be sure. The current blocker list is viewable at https://bugzilla.redhat.com/showdependencytree.cgi?id=235706&hide_resolved=1 however since there is nothing preventing people from adding bugs to this list it will get culled from time to time from things that aren't actually blockers. A (rather longer) list of things we'd like to see fixes for can be seen https://bugzilla.redhat.com/showdependencytree.cgi?id=235705&hide_resolved=1 although this list does get less attention than the blocker list. We deeply appreciate the value we get from our community in using our development tree and testing our release attempts. Without your input, our releases couldn't possibly be as good as they have been. Please help us use these extra couple of weeks to make the already awesome Fedora 9 even better! -- Jesse Keating Fedora -- All my bits are free, are yours?

1 0

Rawhide issues
by Jesse Keating 14 Apr '08

14 Apr '08

Some of you may have noticed some "issues" with rawhide today. Many (most) the packages reverted to unsigned versions, and then at some point today, the content went back in time to yesterday. This is because of a timing issue with trying to sign all the packages for Fedora 9 release. A small thinko led to a big churn that I tried to cut off before it got too far. I think I've recovered most of the damage, and I've prevented rawhide from being composed again until we're done signing packages, which hopefully will be at some point tomorrow. Just wanted to keep you all informed of what's going on. Cheers! P.S. Preview Release is also pending these signatures. It will happen, eventually (: -- Jesse Keating Fedora -- All my bits are free, are yours?

1 0

Red Hat Support Engineering Team is looking for talented, motivated engineers around the world!
by marco bill-peter 10 Apr '08

10 Apr '08

hi Fedora Developers Have you ever thought of making your passion your day job? The Red Hat 3rd level Support Engineering Group - is always looking for talented engineers in almost all corners of the world! If you're interested, go to http://www.redhat.com/about/careers/ and search for 3rd/third level Support Engineering. Apply directly to the website, even if the location is not your current home country. Also feel free to email me directly if you have any question about this position. marco bill-peter Senior Director Support Engineering Group Red Hat mbp at redhat dot com ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Following is a small abstract of the role of our engineers. 3rd level Support Engineer Summary Resolves complex customer problems on the Linux packages, or other complex RH products like GFS, RHCS. This Support Engineer will work closely with RedHat’s front line support engineers, the RH development engineering and the upstream communities. The engineer analyzes upstream development against current customer reported defects (bugs) and develops patches or workaround to resolve the issues. * Develops and recommends corrective workarounds. * Uses skills as a seasoned, experienced professional with a full understanding of industry practices and company policies and procedures; resolves a wide range of issues in imaginative as well as practical ways. * Demonstrates considerable judgment in selecting methods and techniques for obtaining solutions. * Interacts with senior internal and external personnel (upstream community). * Works independently on tasks with minimal guidance on complex issues. Job Requirements * 5 years related experience * Excellent understanding of Linux components, or/and kernel, virtual memory, networking concepts and protocols. * Upstream Linux and Fedora Project or Kernel engagement a plus * Familiar with other operating systems including Solaris, AIX, Tru64 and Microsoft Windows Server desirable * Good understanding of hardware and computer architecture * Development level experience with C, be comfortable to write kernel patches * Experience writing scripts using BASH or Python, Perl to troubleshoot and correct Linux issues.

1 0

Outage Notification - 2008-04-09 20:30:30 UTC
by Mike McGrath 09 Apr '08

09 Apr '08

There will be an outage starting at 2008-04-09 20:30:30 UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2008-04-09 20:30:30 UTC' Affected Services: Buildsystem Unaffected Services: Websites CVS / Source Control Database DNS Mail Torrent Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/400 Reason for Outage: More NFS Lock issues https://bugzilla.redhat.com/show_bug.cgi?id=436174 We recently reverted to a RHEL4 box in hopes that the older version might be more stable but the older kernel and utils did not support our large 10T ext3 filesystem. So we started seeing IO errors. This caused the fs to get mounted RO and caused the first outage. Upon rebuilding nfs1 as a RHEL5 box I decided it best to run e2fsck for good measure. That's where we are at now. The box is up, all configured to export but we're running e2fsck. I'd expect it to be done within the hour. Sorry for all the confusion in this we're working towards a solution. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.

1 0

Fedora 9 Final Freeze
by Jesse Keating 08 Apr '08

08 Apr '08

We froze for Fedora 9 early this morning (the same time the rawhide compose happened). This is our final freeze. http://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy explains the policy. We're planning a snapshot we'll call 'Preview Release' this Thursday or Friday. Then release candidates will be created next week. If it becomes obvious that we will have to slip the release date for getting certain bugs fixed we will announce very loudly as soon as we make the decision. Mass CVS branching will come later this week so that folks can begin work on F10. PS: to see if your build is tagged for Fedora 9, check 'koji latest-pkg f9-final <package>' -- Jesse Keating Fedora -- All my bits are free, are yours?

1 0

Reminder: Repackage with Translations before Development Freeze (next 24h)
by Dimitris Glezos 07 Apr '08

07 Apr '08

For packagers of shipped packages that receive translations from Fedora L10n: Today was the deadline for translation contributions guaranteed to make it into the release. If your packages has received translations, please repackage them before the development freeze date of 8/4 (ie. tomorrow). For Fedora 10, we'll make sure the period to get translations and repackage will be at least a few days. -d -- Dimitris Glezos Jabber ID: glezos(a)jabber.org, GPG: 0xA5A04C3B http://dimitris.glezos.com/ "He who gives up functionality for ease of use loses both and deserves neither." (Anonymous) --

1 0

[Fwd: Final Freeze coming--feature page updates needed]
by John Poelstra 06 Apr '08

06 Apr '08

This email was sent to all individual feature owners. I'm sending it a few other place to keep everyone in the loop and to route around those that have black-listed the feature wrangler's or are waiting for me to send post cards ;-) If you are depending on information about the features below you may want to set wiki page watches to track changes and updates Thanks, John -------- Original Message -------- Subject: Final Freeze coming--feature page updates needed Date: Sun, 06 Apr 2008 17:17:34 -0700 From: John Poelstra <poelstra(a)redhat.com> Hello Feature People :) With final development freeze coming on Tuesday, April 8, 2008 (two days from now in most parts of the world--less in others), sadly this is one of the last times you'll be able to receive nag mail from me for Fedora 9. ;-) Final Development Freeze, defined here: http://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy means that all features must be at 100% completion by this date. Yes, we know "this is Fedora" and "stuff is never 100% done" and all the usual arguments about "what does percentage completion really mean, etc., etc.", but for the average user and members of the other Fedora teams it is important and very helpful to make one last update to your feature page... and for those that will still complain, please make some constructive suggestions for improving the process and lobby to change it for Fedora 10 :) These feature pages are pointed to by a lot by the press and used by many other teams to turn Fedora into a polished looking release so your help is greatly needed and appreciated. You have the distinct privilege of receiving this message because you are listed as the owner for one or more features that are not listed at 100% completion, though many are very close! http://fedoraproject.org/wiki/Releases/9/FeatureList http://fedoraproject.org/wiki/Releases/FeatureDictionary http://fedoraproject.org/wiki/Features/Ext4 http://fedoraproject.org/wiki/Releases/FeatureEncryptedFilesystems http://fedoraproject.org/wiki/Features/OneSecondX http://fedoraproject.org/wiki/Features/Firefox3 http://fedoraproject.org/wiki/Features/freeIPA http://fedoraproject.org/wiki/Features/NewGdm http://fedoraproject.org/wiki/Features/XULRunner http://fedoraproject.org/wiki/Features/XenPvops http://fedoraproject.org/wiki/Features/VirtStorage http://fedoraproject.org/wiki/Features/Upstart http://fedoraproject.org/wiki/Features/XserverOnePointFive http://fedoraproject.org/wiki/Releases/FeatureTexLive http://fedoraproject.org/wiki/Anaconda/Features/SecondStageInstallSource http://fedoraproject.org/wiki/Features/RandrSupport http://fedoraproject.org/wiki/Features/PreUpgrade http://fedoraproject.org/wiki/Features/PartitionResizing http://fedoraproject.org/wiki/Features/PackageKit http://fedoraproject.org/wiki/Features/LivePersistence http://fedoraproject.org/wiki/Releases/FeatureKDE4 http://fedoraproject.org/wiki/Features/K12Linux http://fedoraproject.org/wiki/Features/JigdoRelease http://fedoraproject.org/wiki/Features/IMDesktopIntegration http://fedoraproject.org/wiki/Features/NewGdm I've received several questions in the past about what to do to bring a feature page to 100% or what to do if all the advertised things on the feature page can't be completed in time. Hopefully this helps... 1) If you implemented all of the things described on your feature page and the package is in rawhide, update to 100% 2) If you DID NOT implement all of the things described on your feature page a) change the feature page to reflect all the things you DID complete for Fedora 9 b) make sure the package is in rawhide c) update to 100% d) if you plan to do more unfinished exciting things in F10 move them to a new feature page 3) If your feature page will end up being empty or very brief in order to honestly say it is 100% done it probably should be removed from the Fedora 9 feature list. Simply change the category of your feature page to CategoryProposedFeature (from CategoryAcceptedFedora9) and let me know 4) If this is still confusing, please contact me :) Thanks for your help, John 'tired feature wrangler and yes this manual process is starting to not scale any more' Poelstra

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce April 2008