devel-announce July 2011

devel-announce@lists.fedoraproject.org

4 participants
4 discussions

Outage: Server reboots - 2011-08-01 14:00 UTC
by Kevin Fenzi 27 Jul '11

27 Jul '11

Outage: Server reboots - 2011-08-01 14:00 UTC There will be an outage starting at 2011-08-01 14:00 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 '2011-08-01 14:00 UTC' Reason for outage: A number of servers are being upgraded and must be rebooted. Where possible, services should continue to be available during this outage, but users and maintainers may see short periods of instability or interruptions in some services. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Main Website - http://fedoraproject.org/ Package Database - https://admin.fedoraproject.org/pkgdb/ Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ Unaffected Services: BFO - http://boot.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Fedora Insight - https://insight.fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2900 Contact Information: Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.

1 0

[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway 20 Jul '11

20 Jul '11

Here are the latest changes to the Fedora Packaging Guidelines: --- Some rpm versions pass pathnames to the automatic filtering macros, so a section has been added to the guidelines to help packagers deal with it: https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#P… --- For a while, Fedora considered mono packages to be architecture-specific, and installed assemblies to %{_libdir}. However, after discussions with upstream, we now consider mono packages to be architecture (and platform) independent. This means that mono packages should be correctly installed into the GAC in /usr/lib or installed into /usr/lib/PACKAGENAME. As a notable exception, any ELF binary libraries generated in a mono package must be correctly installed into %{_libdir}, because these files are architecture-specific. Also, even though we consider mono packages to be architecture independent, they must not be marked as "noarch". Although the assemblies are the same, the files may differ due to strings referring to the build architecture. https://fedoraproject.org/wiki/Packaging:Mono#File_Locations --- It was decided that gnome shell extension packages should have the prefix gnome-shell-extension (with no "s" on the end). https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.2… --- The section in the Fedora Packaging Guidelines concerning libexecdir has been improved and expanded: https://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir --- The Fedora Java Packaging Guidelines have been updated to reflect the latest macros for Maven 3. https://fedoraproject.org/wiki/Packaging:Java --- These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC). Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar, Stanislav Ochotnicky, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines. As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure Thanks, ~spot

1 0

Call for Test Days for Fedora 16
by Adam Williamson 19 Jul '11

19 Jul '11

Hi, folks. The Test Day cycle for Fedora 16 will open shortly, and we're putting out the call for anyone who has an idea for a Test Day. There are many open slots on the schedule - https://fedoraproject.org/wiki/QA/Fedora_16_test_days - and if they all fill up or you would like to run a set of Test Days on related topics, we can organize events outside of the scheduled Thursday windows too. It's often a good idea to have a Test Day for a major change or new feature you're introducing to the distribution, but we can run a Test Day on just about any topic. There is a full guide to organizing Test Days available - https://fedoraproject.org/wiki/QA/SOP_Test_Day_management - and the QA team is happy both to help you run a Test Day and to butt out and let you run it yourself, whichever you prefer! If you're interested in running a Test Day, please contact QA via the test mailing list, file a ticket in QA trac - https://fedorahosted.org/fedora-qa - and/or pencil in your event on the schedule, create a Wiki page based on the template (see the SOP for details), and get down to work. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw http://www.happyassassin.net

1 0

Fedora 16 Schedule Reminders - Feature Submission and Feature Freeze.
by Robyn Bergeron 11 Jul '11

11 Jul '11

A few friendly reminders: * The Feature Submission deadline for Fedora 16 is *tomorrow*, July 12. The current process for submitting a feature for Fedora 16 can be seen here: http://fedoraproject.org/wiki/Features/Policy * Feature Freeze comes quickly after the Feature Submission deadline, on July 26. Please note that at this point, Features should be *substantially complete and in a testable state.* For more information on the Feature Freeze policy, please read: http://fedoraproject.org/wiki/ReleaseEngineering/FeatureFreezePolicy And finally.... for those of you interested in seeing how the Feature List is shaping up for Fedora 16, it is up to date with the latest and greatest approvals from today's FESCo meeting. http://fedoraproject.org/wiki/FeatureList This is where I'm going to put on my Gentle Reminder Hat, and give everyone a chance to go into their individual feature pages and update their percentage complete, and update their "Last Updated" date, which I will apply to the main FeatureList page. Your efforts here are appreciated, and help a number of groups understand how close you are to completion, or conversely, if you are at risk of not making deadlines. If percentages don't start getting updated, and "last-updated" dates aren't getting touched, I'll be reaching out to folks individually, but I would prefer to see that people take the initiative and keep those things up. Otherwise I have to get out the not-so-Gentle-Reminder-Hat, and frankly, I don't look very good in that one. Communication is the key here. If you believe you are *at risk* of not making the Feature Freeze, please update your feature page accordingly. The rest of the schedule, as always, can be seen here: https://fedoraproject.org/wiki/Releases/16/Schedule Thanks! -Robyn

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce July 2011