From jkeating at redhat.com Tue Sep 4 16:43:55 2007 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 4 Sep 2007 12:43:55 -0400 Subject: Fedora 8 Test 2 slipping Message-ID: <20070904124355.59b604cd@ender> Due to issues with fast moving parts around installation and composition of the distribution (yum, anaconda, pykickstart, pungi, mash) we haven't had an installable tree for a little while, and not nearly enough time to shake out any other bugs that may be present due to Feature Freeze and lots of fresh content landing. As such we will be extending the freeze for a week to complete our unit testing and to prepare the release. New release date is 25 September 2007. No decisions have been made at this time about slipping any further part of the schedule. -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jkeating at redhat.com Tue Sep 4 17:17:47 2007 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 4 Sep 2007 13:17:47 -0400 Subject: Fedora 8 Test 2 slipping In-Reply-To: <20070904124355.59b604cd@ender> References: <20070904124355.59b604cd@ender> Message-ID: <20070904131747.74ca576f@ender> On Tue, 4 Sep 2007 12:43:55 -0400 Jesse Keating wrote: > New release date is 25 September 2007. *cough* Make that 13 September 2007. I accidentally read the Translation Freeze date. -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jkeating at redhat.com Fri Sep 7 21:36:32 2007 From: jkeating at redhat.com (Jesse Keating) Date: Fri, 7 Sep 2007 17:36:32 -0400 Subject: Fedora 8 Test 2 has gone gold, no more tag requests will be accepted. Freeze is over Message-ID: <20070907173632.0dd7293b@mentok.boston.redhat.com> We have satisfied ourselves that Test2 is as good as it's reasonably going to get without more delays. As such we're handing our release candidate tree off to the mirrors and unfreezing rawhide. This means that a pile of packages will land tomorrow and all kinds of new breakage may occur. The release day for Test2 is Thursday, as this gives the mirrors sufficient time to sync up and prepare for the release. Happy Hacking! -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jkeating at redhat.com Sat Sep 8 01:48:12 2007 From: jkeating at redhat.com (Jesse Keating) Date: Fri, 7 Sep 2007 21:48:12 -0400 Subject: Proposed changes to buildsys-build group (otherwise known as the Exceptions list) In-Reply-To: <20070830205314.7e66bdff@ender> References: <20070830205314.7e66bdff@ender> Message-ID: <20070907214812.05d204e1@ender> On Thu, 30 Aug 2007 20:53:14 -0400 Jesse Keating wrote: > The proposed new explicit list would look like: > > bzip2 > unzip > fedora-release > redhat-rpm-config > diffutils > make > cpio > gcc > coreutils > sed > which > rpm-build > gzip > patch > gcc-c++ > tar > bash > util-linux-ng > gawk > info > grep > findutils These are now the minimal build group. Reasonable requests to add more of what is currently implicit into the explicit list will gladly be discussed, but for now the important thing was to get util-linux-ng back in the set, and to remove perl(-devel) from the set. -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From tcallawa at redhat.com Tue Sep 11 18:07:44 2007 From: tcallawa at redhat.com (Tom "spot" Callaway) Date: Tue, 11 Sep 2007 14:07:44 -0400 Subject: [Guidelines Update] PHP Guidelines Changes Message-ID: <1189534064.3964.18.camel@localhost.localdomain> The following changes were committed to the PHP Guidelines (http://fedoraproject.org/wiki/Packaging/PHP). They were approved by the Fedora Packaging Committee and ratified by FESCo. In the Requires and Provides section, PEAR and PECL packages were redefined to the following: PEAR Packages ============== A PEAR package MUST have: BuildRequires: php-pear(PEAR) Requires: php-pear(PEAR) Requires(post): %{__pear} Requires(postun): %{__pear} Provides: php-pear(foo) = %{version} PECL Packages ============== A PECL package MUST have: BuildRequires: php-devel, php-pear Requires(post): %{__pecl} Requires(postun): %{__pecl} %if %{?php_zend_api}0 Requires: php(zend-abi) = %{php_zend_api} Requires: php(api) = %{php_core_api} %else Requires: php-api = %{php_apiver} %endif Provides: php-pecl(foo) = %{version} In the Macros and Scriptlets section, PECL Modules was redefined to the following: PECL Modules ============= You may need to define a few additional macros to extract some information from PHP. It is recommended that you use the following: %global php_apiver %((echo 0; php -i 2>/dev/null | sed -n 's/^PHP API => //p') | tail -1) %{!?__pecl: %{expand: %%global __pecl %{_bindir}/pecl}} %{!?php_extdir: %{expand: %%global php_extdir %(php-config --extension-dir)}} And here are some recommended scriptlets for properly registering and unregistering the module: %if 0%{?pecl_install:1} %post %{pecl_install} %{pecl_xmldir}/%{name}.xml >/dev/null || : %endif %if 0%{?pecl_uninstall:1} %postun if [ $1 -eq 0 ] ; then %{pecl_uninstall} %{pecl_name} >/dev/null || : fi %endif Thanks, ~spot From tcallawa at redhat.com Tue Sep 11 18:15:25 2007 From: tcallawa at redhat.com (Tom "spot" Callaway) Date: Tue, 11 Sep 2007 14:15:25 -0400 Subject: [Guidelines Change] New guidelines for R packages Message-ID: <1189534525.3964.21.camel@localhost.localdomain> New Guidelines are available for R module packaging: http://fedoraproject.org/wiki/Packaging/R These guidelines were approved by the Fedora Packaging Committee (FPC) and ratified by FESCo. Thanks, ~spot From tcallawa at redhat.com Tue Sep 11 18:24:25 2007 From: tcallawa at redhat.com (Tom "spot" Callaway) Date: Tue, 11 Sep 2007 14:24:25 -0400 Subject: [Guidelines Change] Emacs Guidelines Message-ID: <1189535065.3964.24.camel@localhost.localdomain> New guidelines describing how to package GNU Emacs and XEmacs addon packages can be found here: http://fedoraproject.org/wiki/Packaging/Emacs These guidelines were approved by the Fedora Packaging Committee (FPC) and ratified by FESCo. Thanks, ~spot From jkeating at redhat.com Thu Sep 13 14:30:50 2007 From: jkeating at redhat.com (Jesse Keating) Date: Thu, 13 Sep 2007 10:30:50 -0400 Subject: Announcing Fedora 8 Test 2 (7.91) Message-ID: <20070913103050.33a03547@lumos.localdomain> Batten down the hatches, Fedora 8 Test 2 spotted just over the port side bow! A veritable "sea" of choices await you in this release. First up is the "Fedora" installable 'choose your own adventure' style set of isos and trees for i386, x86_64, and ppc(64). Next up we have a variety of Live images: * Fedora Live (i686, x86_64, ppc) - A good general use Desktop live image. i686 even fits on a CD! * Fedora KDE Live (i686, x86_64) - A Desktop based on the KDE software suite. i686 even fits on a CD! * Fedora Developer Live (i686) - A Live image designed for software developers. * Fedora Electronic Lab (FEL) Live (i686) - A live image designed for engineers working on electronics. Fits on a CD! Remember that these Live images can be used on USB meida via the 'livecd-iso-to-disk' utility available in the livecd-tools package. Test 2 is for "beta" users. This is the time where we have more features in a "testable" state where the more people using them and the more feedback we get the better. So please help us make Fedora 8 as good as we can! Release Notes ============================= Work in progress release notes for this test release can be found in the Fedora wiki: http://fedoraproject.org/wiki/F8Test2/ReleaseNotes Road Map And Release Schedule ============================= This is the second test release of the Fedora 8 release, which is scheduled for November 8, 2007. For further information see http://fedoraproject.org/wiki/Releases/8/ How to get it: ============= DVD and network installation are available. We also offer a few different varieties of installable Live media. http://fedoraproject.org/get-fedora.html For those of you already running rawhide, all you need to do is yum update. You may already have packages newer than Test 2 installed. Bug reporting and tracking: ========================== The Release Engineering and QA teams keep track of bugs that are considered release blockers. You can see that list here: http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=F8Blocker In addition, a list of non-blocker bugs that should be fixed for Fedora 8 if possible can be found here: http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=F8Target Please check these lists before reporting new bugs! -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From lmacken at redhat.com Fri Sep 14 00:13:05 2007 From: lmacken at redhat.com (Luke Macken) Date: Thu, 13 Sep 2007 20:13:05 -0400 Subject: bodhi 0.2.0 Message-ID: <20070914001304.GA4274@crow.myhome.westell.com> I'm pleased to announce that bodhi 0.2.0 has been released and deployed[0]. This release has fixed a ton of issues and introduces many new features, such as: ? Multi-build updates. You can add as many builds to a single update as you want. Bodhi will treat it as a single update, but will still send individual update notification mails for each build. ? New homepage widget that allows you to keep up with the happenings inside of bodhi. You can see the latest comments, testing/security/stable updates, and keep track of your own business. ? Enhanced notifications. If you commented on an update, you'll receive notifications when others comment on that update, and when that update is modified or changes states. ? Automatic closing of bugs is now optional. ? Build-completion improvements. Package names will be automagically completed, and if you type '-' after, it will complete versions as well. ? Positive/negative comments effect an updates 'karma'. After an update achieves a karma of 3, it will automatically be pushed to the stable updates repository. This will hopefully encourage testers to get involved with the updates-testing process a bit more, and will add some automation to the workflow. ? Extended metadata (updateinfo.xml.gz) should start appearing in the repodata, which will allow tools like pup and the yum-security plugin to take advantage of it and do some nifty stuff. ? Reminders. You'll get nagged when your update sits around in testing for too long, and so on.. This release introduces many database changes from the previous version, so it will be much easier to jump back into the release-early-release often cycle. Soon to come: ? bodhi command-line client is almost ready to go. It needs to be polished up a bit, but should be released soon. ? RSS feeds and public details. ? Better build-completion based on koji tags. ? More sanity checking (koji buildroot verification, dependency closure, etc) There is still much more work to be done with bodhi, so if you're interested in helping out, you can setup a local bodhi development playground with just a few commands[1] and dive in. As always, please file any bugs or enhancement requests here[2]. Thanks, luke [0]: http://bodhi.fedoraproject.org [1]: https://hosted.fedoraproject.org/projects/bodhi/wiki/Development [2]: https://hosted.fedoraproject.org/projects/bodhi/newticket From a.badger at gmail.com Fri Sep 14 02:31:08 2007 From: a.badger at gmail.com (Toshio Kuratomi) Date: Thu, 13 Sep 2007 19:31:08 -0700 Subject: PackageDB 0.3.1 open for business Message-ID: <46E9F26C.1080407@gmail.com> Greetings all, After an extended period of testing, I'm officially announcing the PackageDB as open for (some) business. == What can you do == * Add yourself as an owner * Request to be a comaintainer or added to the CC List * Remove yourself from the above * Approve or reject people requesting the above == What can't you do == * Add new packages. The plan is to add a way to enter the package information via a packagedb interface eventually. Once entered, the information will either be queued for a cvsadmin to look at (similar to how requests are handled currently in bugzilla) or the request will automatically happen if a simple test can detect that the review bug was approved. In talks with a limited number of people, the favorite is queueing for an admin. Please discuss this if you think it should happen automatically. [1]_ * Add a branch. This needs a UI created for it as well. I haven't discussed this yet but it seems that adding branches for currently active Fedora (and EPEL) releases should be done automatically when a maintainer requests it. [2]_ * Add another user to a package. Currently, the person has to request the permissions that they want on the package. Then one of the maintainers approves the permissions. I need to code an interface to allow the package maintainers to add another user directly [3]_ .. _[1]: https://hosted.fedoraproject.org/projects/packagedb/ticket/18 .. _[2]: https://hosted.fedoraproject.org/projects/packagedb/ticket/65 .. _[3]: https://hosted.fedoraproject.org/projects/packagedb/ticket/63 == What's Next == The next few weeks of effort will be quick bugfixes and making sure we're ready for the branching of packages that will be done near Fedora 8 release. -Toshio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From jkeating at redhat.com Sun Sep 16 23:39:42 2007 From: jkeating at redhat.com (Jesse Keating) Date: Sun, 16 Sep 2007 19:39:42 -0400 Subject: Fedora 7 update data not valid, do not sync. Message-ID: <20070916193942.6d45afa7@localhost.localdomain> Due to a configuration error, the content in the Fedora 7 updates directory got removed. If you have any automated processes that would sync Fedora 7 updates, it is advised that you turn them off for the time being. We are re-populating the content from the build system but this will take some time (hours). I will respond to this when it finishes (if I'm still awake) and it is safe to sync updates once more. No new updates will be processed until this is fixed. -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jkeating at redhat.com Mon Sep 17 00:47:59 2007 From: jkeating at redhat.com (Jesse Keating) Date: Sun, 16 Sep 2007 20:47:59 -0400 Subject: Fedora 7 update data not valid, do not sync. In-Reply-To: <20070916193942.6d45afa7@localhost.localdomain> References: <20070916193942.6d45afa7@localhost.localdomain> Message-ID: <20070916204759.575d546a@localhost.localdomain> On Sun, 16 Sep 2007 19:39:42 -0400 Jesse Keating wrote: > We are re-populating the content from the build system but > this will take some time (hours). Just to clarify. We aren't rebuilding things, we're just rsyncing the content from the buildserver to the mirror masters. This is what is taking time. The content will be the same once restored. -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dennis at ausil.us Mon Sep 17 03:36:02 2007 From: dennis at ausil.us (Dennis Gilmore) Date: Sun, 16 Sep 2007 22:36:02 -0500 Subject: EPEL and Fedora Extras build system down Message-ID: <200709162236.16142.dennis@ausil.us> Hi All, The main build hub for the plague build system is currently down. It will remain down until we can get someone to look at it in the morning. Sorry for the short notice. Dennis -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From katzj at redhat.com Mon Sep 17 19:57:33 2007 From: katzj at redhat.com (Jeremy Katz) Date: Mon, 17 Sep 2007 15:57:33 -0400 Subject: REMINDER: Fedora 8 Test3 Freeze Message-ID: <1190059053.21026.104.camel@localhost.localdomain> The Fedora 8 Test 3 freeze is rapidly approaching! This is your last major chance for getting any bug fixes or other changes tested prior to the release of Fedora 8. The freeze date is next Tuesday, September 25. For full details of the schedule, as always, see http://fedoraproject.org/wiki/Releases/8/Schedule What does this mean? It means that it's probably a good time to go through and look through all of the bugs that are filed against your packages. And as much as possible, fixing those bugs which you deem important for Fedora 8 prior to the freeze date. Also, for tracking purposes, you might want to attach important bugs to one of the tracker bugs according to the criteria at http://fedoraproject.org/wiki/QA/ReleaseCriteria. A quick summary of the main tracking bugs are * F8Blocker (235703): This is for bugs which are very very bad. Bugs which the release team should consider slipping the release for. Note, you should not use this characterization lightly. And the final judgement on whether a bug is worth slipping the release will be made by the release team. * F8Target (235704): Bugs which are pretty important, but not slip-worthy. The release team will keep an eye on this list and would ultimately like the open bugs here to be as minimal as possible. Once we enter the freeze, changes for the test release will be approved according to the normal test freeze policy (http://fedoraproject.org/wiki/ReleaseEngineering/TestFreezePolicy). After Test3, we want to reduce the number of changes going in to help ensure that the final release has as few regressions as possible. So it's very important to get as many of the fixes as possible done prior to Test3. More complete details about the post-test3 procedure will be forthcoming as we reach that point in the schedule. Thanks for your hard work! Jeremy From jkeating at redhat.com Tue Sep 18 11:13:51 2007 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 18 Sep 2007 07:13:51 -0400 Subject: Fedora 7 update data not valid, do not sync. In-Reply-To: <20070916204759.575d546a@localhost.localdomain> References: <20070916193942.6d45afa7@localhost.localdomain> <20070916204759.575d546a@localhost.localdomain> Message-ID: <20070918071351.22c33394@localhost.localdomain> On Sun, 16 Sep 2007 20:47:59 -0400 Jesse Keating wrote: > > We are re-populating the content from the build system but > > this will take some time (hours). > > Just to clarify. We aren't rebuilding things, we're just rsyncing the > content from the buildserver to the mirror masters. This is what is > taking time. The content will be the same once restored. All the data has been restored and a successful update push has occurred. It is safe once again to sync updates. -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jakub at redhat.com Tue Sep 18 23:33:06 2007 From: jakub at redhat.com (Jakub Jelinek) Date: Tue, 18 Sep 2007 19:33:06 -0400 Subject: -D_FORTIFY_SOURCE=2 and C++ Message-ID: <20070918233306.GG25210@devserv.devel.redhat.com> Hi! Starting with gcc-4.1.2-25 and glibc-2.6.90-14 -D_FORTIFY_SOURCE=2 protects not only C code, but also C++. There have been several security issues already which would have been unexploitable if this checking was in place earlier. All the mem*, str* etc. routines that were previously protected in C will now do so in C++ as well, similarly *printf won't accept %n if format string is in writable memory, open{,at}{,64} functions are checked too (compile time detecteable O_CREAT with only 2 arguments (3 for openat{,64}) results in link time errors, if it is unclear whether oflag arg has O_CREAT or not at compile time and only 2 (resp. 3 for openat{,64}) args are provided, runtime checking is done). BTW, even for C open is no longer a function-like macro, while it is desirable to fix packages that don't allow open to be defined as function-like macro, it will no longer be a necessity for F8 to change this. If you see any bugs on the toolchain side (rather than newly discovered package bugs), please let us know in bugzilla ASAP. Thanks. Jakub From jkeating at redhat.com Tue Sep 18 14:51:37 2007 From: jkeating at redhat.com (Jesse Keating) Date: Tue, 18 Sep 2007 10:51:37 -0400 Subject: Xulrunner in Fedora 8 Message-ID: <20070918105137.1da06ba6@localhost.localdomain> A xulrunner build appeared in Fedora 8 buildroot and was pushed out to rawhide. This was a bit premature and as such we have untagged the build. There is no older build, nor any new build to immediately fix issues. Therefor xulrunner will not be available in buildroots and it will disappear from rawhide until the issues surrounding it are resolved (matching firefox build, ppc(64) support, no conflicting files). -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From wtogami at redhat.com Thu Sep 20 17:19:53 2007 From: wtogami at redhat.com (Warren Togami) Date: Thu, 20 Sep 2007 13:19:53 -0400 Subject: Proposed changes to F8 Freeze Process Message-ID: <46F2ABB9.7040504@redhat.com> September 20th, 2007 Fedora Engineering Steering Committee ratified these changes to the final F8 freeze process. http://fedoraproject.org/wiki/Releases/8/Schedule 1) CHANGE: At F8 Development freeze currently scheduled for October 4th, the tree will be unlocked for new builds to be automatically tagged into dist-f8. We will be treating this as an "honor system" freeze, where participants are expected to commit only bug fixes and NOT threaten the release with new features or risky changes. The purpose of this new "freeze" policy is an experiment to smoothen the process of getting last-minute fixes in F8 without creating a large workload on rel-eng. This should reduce confusion of built but not tagged packages like during past freezes. HOWEVER, peer policing of proper adherence to freeze guidelines is essential. We will be advertising loudly expectations of package maintainers of acceptable changes during the freeze period. 2) REMINDER: If you screw up and add something to F8 that shouldn't be (horribly broken new version, ABI change, so-name bump, new features, etc.) we will NOT roll-back your build if it has already hit a daily rawhide push. Your only option to recover from this mistake will be to increase the version number or Epoch. 3) CHANGE: Prior to Final Freeze (October 17th) devel/ CVS branch will build into dist-f8. Some package maintainers will want to begin building packages with risky changes (ABI, new features, etc.) in preparation for F9. At their option they may request per-package CVS branch to F-8/ so they may do so without risking F-8 stability. Then devel/ can be used to target dist-f9. 4) CHANGE: Due to the definition of "Development freeze" changing, we are moving up the Final freeze date a week to October 17th. At this point builds will no longer be automatically tagged dist-f8 and will require rel-eng approval to be included in the F8 release. All remaining devel/ will be branched to F-8/, and devel/ will target builds to dist-f9. Warren Togami wtogami at redhat.com From wtogami at redhat.com Thu Sep 20 17:28:53 2007 From: wtogami at redhat.com (Warren Togami) Date: Thu, 20 Sep 2007 13:28:53 -0400 Subject: CORRECTION: Changes to F8 Freeze Process In-Reply-To: <46F2ABB9.7040504@redhat.com> References: <46F2ABB9.7040504@redhat.com> Message-ID: <46F2ADD5.3020604@redhat.com> Oops. The previous announcement incorrectly said "Proposed" in the subject. This correction is to be explicitly clear that the changes were ratified. That is all. Warren Togami wtogami at redhat.com From tcallawa at redhat.com Sat Sep 22 20:29:20 2007 From: tcallawa at redhat.com (Tom "spot" Callaway) Date: Sat, 22 Sep 2007 16:29:20 -0400 Subject: [Policy Change] Kernel Module packages no longer permitted Message-ID: <1190492961.3966.4.camel@localhost.localdomain> At one point (pre Fedora 8), packages containing "addon" kernel modules were permitted. This is no longer the case. Fedora strongly encourages kernel module packagers to submit their code into the upstream kernel tree. Existing kernel module packages must be removed (or merged into the main kernel package) before Fedora 9. The reference documentation on how to package kernel modules in the "kmod" style has been preserved http://fedoraproject.org/wiki/Obsolete/KernelModules This change was ratified by FESCo. Thanks, ~spot From mmcgrath at redhat.com Tue Sep 25 14:29:14 2007 From: mmcgrath at redhat.com (Mike McGrath) Date: Tue, 25 Sep 2007 09:29:14 -0500 Subject: Outage Notification - 2007-09-26 04:00 UTC (DB2) Message-ID: <46F91B3A.3050108@redhat.com> There will be an outage starting at 2007-09-26 04:00 UTC UTC, which will last approximately 5 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2007-09-26 04:00 UTC' Affected Services: Websites Buildsystem Database Unaffected Services: CVS / Source Control DNS Mail Torrent Ticket Link: https://hosted.fedoraproject.org/projects/fedora-infrastructure/ticket/163 Reason for Outage: DB2 is running out of disk space. This is a preventative maintenance to ensure that we don't completely run out. There are a couple of avenues I'm still examining but if they fail I'll be forced to rebuild db2 with more storage and that's the reason for the outage. Its possible the actual outage will only take an hour or two but just in case I've created a 5 hour block. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. From jkeating at redhat.com Wed Sep 26 11:28:00 2007 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 26 Sep 2007 07:28:00 -0400 Subject: We are Frozen for Test3 Message-ID: <20070926072800.2e91ac04@redhat.com> We froze for test3 early this morning. This also marks the Devel freeze for the remainder of the Fedora 8 development cycle. Builds from rawhide will continue to get the 'dist-f8' tag, and will be available in the buildroots to build against. However rawhide will compose from the 'dist-rawhide' tag, which inherits from 'f8-test3'. If you need to get a build into Fedora 8 Test3, please follow http://fedoraproject.org/wiki/ReleaseEngineering/TestFreezePolicy For schedule information, see http://fedoraproject.org/wiki/Releases/8/Schedule To see if your build made the freeze cut off, see http://koji.fedoraproject.org/koji/builds?tagID=27 or simply call 'koji latest-pkg f8-test3 ' -- Jesse Keating Fedora -- All my bits are free, are yours? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: