devel-announce March 2011

devel-announce@lists.fedoraproject.org

8 participants
12 discussions

Beta change freeze
by Dennis Gilmore 29 Mar '11

29 Mar '11

Hi All a heads up that change freeze for the Fedora 15 Beta is Tuesday April 5th. after this point only accepted blocker bugs will be pulled in. Please limit your changes to try and avoid unintended breakages. thanks Dennis

1 0

Fedora 15 schedule to slip an additional week
by Jared K. Smith 24 Mar '11

24 Mar '11

The Fedora 15 development cycle is well under way, and making good progress. Yesterday I met[1] with Release Engineering, QA, the Fedora Program Manager, and we decided that in order to accommodate some late-breaking changes, we're going to need to slip the Fedora 15 release schedule by a week in order to have adequate time to do proper testing of the candidate images before the Beta. This slip will affect the entire Fedora 15 development cycle, as shown in the chart below: o F15 Devel Start 2010-11-02 o Feature Submission Deadline 2011-01-25 o Feature Freeze 2011-02-08 o Branch From Rawhide 2011-02-08 o Software String Freeze 2011-02-15 o Alpha Change Deadline 2011-02-15 o Alpha Release 2011-03-08 -------------------- N O W ----------------------- o Software Translation Deadline 2011-04-05 o Beta Change Deadline 2011-04-05 o Features 100% Complete 2011-04-05 o Beta Release 2011-04-19 o Final Change Deadline 2011-05-09 o Compose RC 2011-05-10 o GA 2011-05-24 Robyn Bergeron has also kindly updated the complete break-out of the Fedora release schedule, which is available from http://rbergero.fedorapeople.org/schedules/f-15/. If you have any questions or concerns, please don't hesitate to let me know. -- Jared Smith Fedora Project Leader

1 0

[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway 24 Mar '11

24 Mar '11

Here are the changes to the Fedora Packaging Guidelines for this week: --- The Packaging:PHP guidelines have been updated to reflect that PEAR documentation provided by upstream are installed in %{pear_docdir}, should stay there, and must be marked as %doc. Additionally, the definition of pear_docdir has been defined as %{_docdir}/pear. https://fedoraproject.org/wiki/Packaging:PHP --- The Java guidelines have been updated to add information and sample template for Maven 3 (Fedora 15+). https://fedoraproject.org/wiki/Packaging:Java --- These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC). Many thanks to Remi Collet, 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

[Guidelines Change] Changes to the Packaging Guidelines
by Tom Callaway 22 Mar '11

22 Mar '11

Here are the latest set of changes to the Fedora Packaging Guidelines: --- The Emacs packaging guidelines were updated to handle cases where a package's principal functionality does not require (X)Emacs, but the package also includes some auxiliary Elisp files to provide support for the package in (X)Emacs. https://fedoraproject.org/wiki/Packaging:Emacs --- The Scriptlet Snippets section dealing with the order that scriptlets are invoked has been updated to include %trigger scripts. https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Orderi… --- A subsection was added to the Packaging Guidelines section on Filesystem Layout in which it is made explicit that binaries in /bin or /sbin must NOT depend on any libraries in /usr/lib or /usr/lib64. https://fedoraproject.org/wiki/Packaging:Guidelines#Binaries_in_.2Fbin_and_… --- The section on Epochs was improved, and clarifying language about Epoch use in Requires was added to the Packaging Guidelines. https://fedoraproject.org/wiki/Packaging:Guidelines#Use_of_Epochs https://fedoraproject.org/wiki/Packaging:Guidelines#Requires --- New guidelines were added covering the packaging of Ada programs. https://fedoraproject.org/wiki/Packaging:Ada --- The section on Boostrapping in the Treatment of Bundled Libraries page in the Packaging Guidelines has been amended to add the following: Packages which are built in such a bootstrapping mode must not be tagged for a final release (or pushed as an update for any stable release). FPC will track the progress of approved bootstrapping exceptions via the ticket requesting the bootstrap bundling exception. https://fedoraproject.org/wiki/Packaging:Treatment_Of_Bundled_Libraries#Boo… --- Macro forms of system executables (such as %{__rm}) should not be used except when there is a need to allow the location of those executables to be configurable. https://fedoraproject.org/wiki/Packaging:Guidelines#Macros --- These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC). Many thanks to Hans Niedermann, Jonathan Underwood, Pavel Zhukov, 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

Your package translation
by Noriko Mizumoto 22 Mar '11

22 Mar '11

(cc'd to trans at lists) Dear Fedora package maintainers Could you all please take a few minutes and check if your packages are on the list [1] and set to allow Fedora Localization Project to translate? - setuptool: http://www.transifex.net/projects/p/setuptool/ - pam_krb5: http://www.transifex.net/projects/p/pam_krb5/ - pkinit-nss: http://www.transifex.net/projects/p/pkinit-nss/ * The above packages are on the list but do not allow Fedora Localization teams to upload the translated files. This means that these packages will not receive any translation from FLP. Please change the setting to allow FLP, or advise us if the maintainers choose having their own translation teams. In that case, the packages may be removed from the list of Fedora Project on tx.net. [1]:http://www.transifex.net/projects/p/fedora/r/fedora-15/l/en/ noriko Fedora Localization Project

1 0

poppler soname bump in F15 and rawhide
by Marek Kasik 18 Mar '11

18 Mar '11

Hi, I plan to rebase poppler in Fedora 15 and rawhide to poppler-0.16.3. There is one API change (in PreScanOutputDev.h) and 1 soname bump (libpoppler.so.12 to libpoppler.so.13). You can test it against your package with this scratch-build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2884655 I'll do chain-build of poppler and packages requiring it next Thursday (10th of March). Regards Marek

1 2

Reminder: today is GNOME 3 Test Day #2
by Adam Williamson 10 Mar '11

10 Mar '11

Hi, everyone! Just a quick reminder that today is the second Test Day for GNOME 3: https://fedoraproject.org/wiki/Test_Day:2011-03-10_GNOME3_Beta . Please do come along and help with testing if you can. We're having trouble with the 32-bit live image, but a 64-bit image is available now and all the test instructions are in place. We'll be in #fedora-test-day on IRC all day long to help out with testing, so come along and join us there. Thanks a lot! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

1 0

xerces-c soname bump in Rawhide
by Kalev Lember 10 Mar '11

10 Mar '11

Hi, Jonathan Robie and I are planning to update xerces-c from 3.0.1 to 3.1.1 in Rawhide, which includes a soname bump; F-15 will stay on 3.0.1. I will handle the rebuilds of affected packages: blahtexml-0.8-2.fc15 cegui-0.7.5-5.fc15 enigma-1.01-12 frepple-0.8.1-3.fc15 gdal-1.7.3-2.fc15 glest-3.2.2-7.fc15 libdigidocpp-0.3.0-3.fc15 opensaml-2.3-3.fc15 ovaldi-5.6.4-1.fc14 qpid-cpp-0.8-6.fc16 xalan-c-1.10.0-8.fc15 xmlcopyeditor-1.2.0.2-4.fc15 xml-security-c-1.5.1-4.fc15 xmltooling-1.3.3-2.fc15 xqilla-2.2.3-8.fc14 xsd-3.3.0-4.fc15 -- Regards, Kalev

1 0

Announcing the release of Fedora 15 Alpha!!
by Dennis Gilmore 08 Mar '11

08 Mar '11

The Fedora 15 "Lovelock" Alpha release is available! This release offers a preview of some of the best free and open source technology currently under development. Catch a glimpse of the future: http://fedoraproject.org/get-prerelease *** What is the Alpha release? *** The Alpha release contains all the beefy features of Fedora 15 in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete, and bears a very strong resemblance to the third and final release. The final release of Fedora 15 is due in May. We need your help to make Fedora 15 the best release yet, so please take a moment of your time to download and try out the Alpha and make sure the things that are important to you are working. If you find a bug, please report it -- every bug you uncover is a chance to improve the experience for millions of Fedora users worldwide. Together, we can make Fedora a rock-solid distribution. (Read down to the end of the announcement for more information on how to help.) *** Features *** This release of Fedora includes a variety of features both over and under the hood that show off the power and flexibility of the advancing state of free software. Examples include: * Updated Desktop Environments. Fedora 15 will ship with GNOME 3, the next major version of the GNOME desktop. If you're interested in other experiences, KDE and Xfce will also be showcasing the latest and greatest in desktop technology from their respective projects. * System and session management. Previously available as a technology preview in F14, systemd makes its full-fledged debut in Fedora 15. systemd is a smarter, more efficient way of starting up and managing the background daemons relied on by services we all use every day - such as NetworkManager and PulseAudio. * Cloud. Looking to create appliances for use in the Cloud? BoxGrinder creates appliances (virtual machines) for various platforms (KVM, Xen, EC2) from simple plain text appliance definition files for various virtual platforms. * Updated programming languages and tools. Fedora 15 features new versions of Rails, OCaml, and Python. GDB and GCC have also been updated. (Fedora 15 was built with GCC 4.6.0, too!) * Productivity Applications. LibreOffice is filled with tools for everyday use, including word processing, spreadsheet, and presentation applications. * Consistent Network Device Naming. Server management just got even easier. Fedora 15 uses BIOS-provided, non-arbitrarily given names for network ports, taking the burden off of system administrators. * Dynamic Firewall. Fedora 15 adds support for the optional firewall daemon, that provides a dynamic firewall management with a D-Bus interface. * eCryptfs in Authconfig. Fedora 15 brings in improved support for eCryptfs, a stacked cryptographic filesystem for Linux. Starting with Fedora 15, authconfig can be used to automatically mount a private encrypted part of the home directory when a user logs in. * DNSSEC for workstations. NetworkManager now uses the BIND nameserver as a DNSSEC resolver. All received DNS responses are proved to be correct. If particular domain is signed and failed to validate then resolver returns SERFVAIL instead of invalidated response, which means something is wrong. * Go Green. Power Management improvements include the PowerTOP tool, which identifies the software components that make your computer use more energy than necessary while idle. Automatic tuning of power consumption and performance helps conserve on laptop battery usage, too! * Business Management tools. Tryton is a three-tier high-level general purpose application platform, providing solutions for accounting, invoicing, sale management, purchase management, analytic accounting, and inventory management. * New Package Suite Groups. The Graphics suite group has been renamed to the Design group, and the Robotics SIG has created the Robotics Package Suite, a collection of software that provides an out-of-the-box usable robotic simulation environment featuring a linear demo to introduce new users. These and many other improvements provide a wide and solid base for future releases, further increasing the range of possibilities for developers and helping to maintain Fedora's position at the leading edge of free and open source technology. A more complete list and details of each new cited feature is available here: http://fedoraproject.org/wiki/Releases/15/FeatureList We have nightly composes of alternate spins available here: http://alt.fedoraproject.org/pub/alt/nightly-composes/ *** Issues and Details *** For more information including common and known bugs, tips on how to report bugs, and the official release schedule, please refer to the release notes: http://fedoraproject.org/wiki/Fedora_15_Alpha_release_notes A shorter list of common bugs can be found here: https://fedoraproject.org/wiki/Common_F15_bugs *** Contributing *** Bug reports are helpful, especially for Alpha. If you encounter any issues please report them and help make this release of Fedora the best ever. Thank you, and we hope to see you in the Fedora project!

1 0

ACTION REQUIRED: Important hanges to Fedora translation workflow
by Jared K. Smith 03 Mar '11

03 Mar '11

Quick Summary --- The Fedora translation workflow has changed. If you are a developer of a package being translated by the Fedora Translation (L10n) Project, you must change your workflow slightly if you want translated strings to appear in your software package. Tools and assistance are available to make this workflow as simple as possible for developers. Read below for details. Details --- Over the past couple of weeks, we've made some improvements and infrastructure changes to the Fedora translation system. We've moved from a self-hosted version 0.7 instance of the Transifex software to a hosted version of the 1.1-dev version at Transifex.net. The upgrade from version 0.7 to version 1.0 (and beyond) introduces a number of important changes for developers and packagers. Please pay close attention to this email, particularly if your software package uses translations provided by the Fedora Translation team. While the changes aren't terribly complicated, they do have a bigger impact on the developer than they do on the translation team. The most visible change is that Transifex’s native integration with source code management systems has been replaced by a mechanism for automatic updates. Transifex now watches an HTTP view of a repository for change notifications. In addition, there is now a more secure command-line tool for project maintainers and translators. This new command-line tool has been packaged for Fedora in the "transifex-client" package. It is currently available in Rawhide (pre-F16), and in the "updates-testing" repositories for Fedora 13, 14, and 15, and EPEL 5 and 6. Here's the new workflow: This series of steps only needs to be run once for a project. * The developer installs the "transifex-client" package: yum --enablerepo=updates-testing install transifex-client * The developer runs the "tx init" command in the top level folder of the project. * The developer runs the "tx set" command according to the transifex-client user guide found at: http://help.transifex.net/user-guide/client/client-0.4.html. This creates a small config file, .tx/config, which can be committed in the repository for re-use, if desired. This series of steps are run on as as-needed basis: * The developer updates and commits his or her POT file to the project's repository at string-freeze time or as needed. * Transifex watches an HTTP link to that POT file and auto-updates its English strings regularly, *OR* the developer can also push the POT file to Transifex (either manually or as part of a build script) by using the "tx push" command. * Translators work inside Transifex. Translated strings are stored inside of Transifex, and are *not* pushed automatically to the developer's repo. * Before rolling a release, the developer runs 'tx pull' (either manually or from a build script) to fetch the latest translation files from Transifex. Translation files do not need to live in the repo, although the developer may commit and store copies if desired. For more details on the features of the new version of Transifex and more help on using the transifex client, please refer to either http://help.transifex.net/user-guide/one-dot-zero.html or the Fedora-specific wiki page at https://fedoraproject.org/wiki/FAQ_on_migration_to_transifex.net. If you have technical questions, feel free to ask questions in the #fedora-l10n or #transifex IRC channels or on the devel mailing list. -- Jared Smith Fedora Project Leader

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce March 2011