devel-announce July 2008

devel-announce@lists.fedoraproject.org

12 participants
19 discussions

Implementing new wiki categories names for feature process
by John Poelstra 31 Jul '08

31 Jul '08

Since there were no objections to the original proposal: https://www.redhat.com/archives/fedora-devel-announce/2008-July/msg00009.ht… I will be implementing the change in category names for the feature process starting today. John

1 0

[Fwd: bugzilla.redhat.com Web UI, Database, XMLRPC Planned Outage | August 2nd, 2008 - 9:00 AM EST - 7:00 PM EST]
by John Poelstra 31 Jul '08

31 Jul '08

Reminder: This Weekend -------- Original Message -------- Subject: bugzilla.redhat.com Web UI, Database, XMLRPC Planned Outage | August 2nd, 2008 - 9:00 AM EST - 7:00 PM EST Date: Tue, 29 Jul 2008 00:05:42 -0400 From: Dave Lawrence <dkl(a)redhat.com> O U T A G E R E Q U E S T F O R M ===================================== Severity: Severity Two (High) Scheduled Date: August 2nd, 2008 Scheduled Time: 9:00 AM EST - 7:00 PM EST Estimated Time Required: 10 hours Performed By: Red Hat Engineering Operations People/Groups Impacted: Users of bugzilla.redhat.com and any services that rely on bugzilla.redhat.com Site/Services Affected: bugzilla.redhat.com Web UI, Database, XMLRPC Impact: bugzilla.redhat.com will be unavailable during the posted time on August 2nd, 2008. Description: On August 2nd, bugzilla.redhat.com will go down for an update to the latest upstream code base. During this time the web servers will be reinstalled with the latest OS updates as well as the latest Bugzilla code. Also the database servers will undergo a data migration to be made compatible with the latest Bugzilla code. The web UI, database, and all XMLRPC services will be unavailable during the migration. Services that rely on bugzilla.redhat.com may not function properly during this time so please let your users know about the outage as well. Also please take time to point your services/scripts at our test server https://partner-bugzilla.redhat.com to make sure that they will still work with the new system once it goes live. Care has been taken to make the new system backwards compatible as much as possible with the old XMLRPC API but still confirm that they work properly. If you encounter any problems, please contact bugzilla-owner redhat com or file a bug at https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&version=3.2 Signoff: kbaker redhat com

1 0

Outage Notification - 2008-07-31 03:30 UTC to 2008-07-31 06:20 UTC
by Nigel Jones 31 Jul '08

31 Jul '08

An unplanned outage occurred at approximately 2008-07-31 03:30 UTC and is mostly resolved as of 2008-07-31 06:20 UTC Affected Services where: - Websites - Package DB, Mirror Manager Admin Interface, Bodhi, Translate - Account System (FAS) - Any other authenticated requests - Buildsystem Partial Outages: - Hosted (Trac authentication) - Wiki (Read Only, some pages may appear broken as well) Unaffected Services: - CVS / Source Control - Database - DNS - Mail - Torrent - Fedora Talk Reason for Outage: Our main filer took a turn for the worst, and took down one of our main database servers and other associated infrastructure. We have now for the most part resolved the issue, and diagnostic work has begun, we apologise for any inconvenience. Ticket Information: More information will be made available to https://fedorahosted.org/fedora-infrastructure/ticket/735 when it comes to hand. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. Regards, Nigel Jones

1 0

Release Planning Recap :: 2008-07-30, UTC 1700
by Paul W. Frields 30 Jul '08

30 Jul '08

= Release planning meeting, 2008-07-30 = == Attendance == ''Present:'' Tom Callaway (Engineering/Legal), Paul Frields (moderator), Jesse Keating (RelEng), Jonathan Roberts (Marketing), Seth Vidal (Infrastructure), Karsten Wade (Docs) == Agenda == === Reiterating purpose === * Not policy setting, nor decision making * Progress reporting and schedule debugging only * Making sure that dependencies that affect releases are being satisfied across Fedora community teams * Any action items are potential only, until pushed out into the community space for discussion and follow-through === Current Alpha status (RelEng) === * Not finished ** Number of composes happening internally on f13's workstation ** Not enough got done during OLS/OSCON - not enough people doing anything with looking at bits ** We can't compose yet in PHX, which is why it happens on f13's station ** Chasing down issues with anaconda currently, hopefully on the last few now ** f13 hopes to have a candidate release tree ** New problem in installer right now * Not yet in danger of slipping ** If we don't have a tree by tomorrow, that's not good === Infrastructure === * uncomfortable problems in existing BT server, it keeps dying (serverbeach1) ** Might be routing, or hardware... testing to figure it out ** skvidal is going to keep a very close eye on making sure the old and new servers are sync'd '''DEBUGGING:''' Should f13's routine change? No. * Space issues? 261GB available on netapps ** many terabytes coming back online "soon" ** drives hopefully coming in next week, then it's just reconfiguring, no onsite required === Docs === * Alpha and Beta release notes are a one-sheet on the wiki ** Living document, can change after release day ** QA, Desktop, and RelEng have done a great job of adding some important content ** Priority is to let testers know what you want them to do with the Alpha '''DEBUGGING:''' We need a list of pre-approved URLs for release announcement * Docs can handle the majority of the text for the release announcement email, and check URLs, so releng can concentrate on sending it out when final * Release notes production is hopefully going to change with F10 to use an in-distro tool, publican, to build === Marketing === * Not much on plate for Alpha in particular * Geek news will be all over the Alpha, are we doing anything to publicize it? ** Paul has been working with Kara on e.g. a press blog entry ** Our announcement should also serve as testing recruitment === Legal === * Nothing at this time == Next meeting == * Post-partum Alpha meeting would probably be useful ** if no agenda items, no meeting * Definitely one a few days ahead of Beta freeze ** Announcements to go to fedora-devel-list

1 0

The results are in for the Fedroa 10 naming
by Josh Boyer 28 Jul '08

28 Jul '08

Drum roll... And the winner of the Fedora 10 codename is: Cambridge The full GPG-signed information from our election coordinator, Nigel Jones, including vote totals, is located here: http://jwboyer.fedorapeople.org/fedora10relname.txt.asc Many thanks to the Board, Paul Frields, and Nigel Jones for their effort in getting the name candidates and vote set up. josh -- fedora-announce-list mailing list fedora-announce-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-announce-list

1 0

The results are in for the Fedroa 10 naming
by Josh Boyer 28 Jul '08

28 Jul '08

1 0

CVS/Pkgdb outage
by Casey Dahlin 25 Jul '08

25 Jul '08

Outage Notification - 2008-07-28 01:20 UTC There will be an outage starting at 2008-07-28 01:20 UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2008-07-28 01:20 UTC' Affected Services: PackageDB CVS / Source Control Reason for Outage: Renaming cvsextras group to 'packager' Contact Information: Casey Dahlin <cdahlin(a)redhat.com> Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.

1 0

Slight change in how cvs notifications work
by Toshio Kuratomi 25 Jul '08

25 Jul '08

We've had some issues with notification emails being sent on cvs commits. Sometimes generating the list of email addresses to notify was slow, on other occassions it would fail altogether. To alleviate this we've changed from a dynamic determination of who is notified by querying the pkgdb to a static one by sending to an email alias generated from pkgdb information once an hour. There is one major difference (besides speed) to note in this: Before, the owner and people in the watchcommits acls received notifications that a cvs commit was made to a package. Now the owner and people onwatchcommits and watchbugzilla acls are notified. The aliases used to send these messages are all pkg-owner(a)fedoraproject.org in case you have mail filters you want to setup to handle it. Thank you, -Toshio

1 0

Cast your vote for the Fedora 10 Codename!
by Josh Boyer 22 Jul '08

22 Jul '08

We have several options for the Fedora 10 codename, and you get to help decide which we use! https://admin.fedoraproject.org/voting/about/10 is the URL to cast your vote. Log in with your Fedora Account name and password. As long as you have signed the CLA and belong to one additional group in the Fedora Account System, you can cast your vote. Voting will end and be tallied at 23:59:59 28 July 2008 UTC. josh

1 0

Feature Process Improvements
by John Poelstra 21 Jul '08

21 Jul '08

I was recently talking with Paul Frields about how to make the feature process more accessible... this combined with feedback in the rpm thread have led to a (hopefully) clearer presentation of how the feature process works. FIRST: Paul did a great job reorganizing the content on the main page. None of the content has changed, but the presentation is a lot simpler and less overwhelming. https://fedoraproject.org/wiki/Features/Policy I still need to add definitions and guidance for what belongs in each section of the form. SECOND: We are proposing new category names to make it more self-evident which state a feature page is in. Unless there are objections I plan to run this past FESCo for a sanity check this coming Thursday and start using them thereafter--including converting the category names for existing pages. The new category names would look like this: Category:FeaturePageIncomplete (was ProposedFeature)--every feature starts in this category and returns to this category if it is reviewed or voted on and needs more work. Category:FeatureReadyForWrangler (was ProposedF10)--feature owner signals that their feature page is complete and requests that FESco review and accept it for the release under development Category:FeatureReadyForFesco (was ProposedF10)--Feature wrangler changes features to this category when they are ready for FESCo vote Category:FeatureAcceptedF10 (unchanged)--voted on and accepted by fesco A draft updated illustration is here: http://poelstra.fedorapeople.org/misc/feature-process-flow-v3.2.png Source: http://poelstra.fedorapeople.org/misc/feature-process-flow-v3.2.odg Thanks also to Paul for his ideas and help on the illustration! John

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce July 2008