From Fedora Project Wiki

< FWN‎ | Beats
No edit summary
Line 5: Line 5:
http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Events<ref>http://fedoraproject.org/wiki/Events</ref>.
http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Events<ref>http://fedoraproject.org/wiki/Events</ref>.


Contributing Writer: [[User:Rashadul|Rashadul Islam]]
Contributing Writer: [[User:pcalarco|Pascal Calarco]]


<references/>
<references/>
Line 13: Line 13:


===Fedora Development News===
===Fedora Development News===
====[Guidelines Change] Changes to the Packaging Guidelines 04/09 - 02/10====   
====Google Summer of Code proposal: Better iptables management====   
[[User:Spot|Tom "spot" Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000584.html</ref> the changes to the Packaging Guidelines 04/09 - 02/10. He said, "It has been almost a year since we announced changes to the Packaging
Zubin Mithra<ref>Zubin Mithra</ref> invited comments<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000591.html</ref> on a Google Summer of Code proposal to improve iptables in Fedora:
Guidelines, so this will be a long list. In the future, we'll try to be more timely in writing up changes and announcing them to the Fedora Community.


Here are the list of changes to the Fedora Packaging Guidelines:
"My name is Zubin Mithra and I am aspiring to get into GSoC on behalf
When selecting which source to download from upstream and use in a Fedora package, the smallest available (and Fedora compatible) source
of Fedora. I wish to work on making a library for better iptables
should be used:<ref>https://fedoraproject.org/wiki/Packaging/SourceURL#Referencing_Source</ref>
management. Details can be viewed in the proposal which I have
attached along with the email.


The Fortran Packaging Guidelines have been updated: <ref>https://fedoraproject.org/wiki/Packaging:Fortran</ref>
I would love to hear your views on it."


The Ant Sample Spec in the Java Packaging Guidelines has been corrected:<ref>https://fedoraproject.org/wiki/Packaging/Java</ref>
A PDF<ref>http://lists.fedoraproject.org/pipermail/devel-announce/attachments/20100312/60f1c65f/attachment-0001.pdf</ref> of the proposal is available.
<references/>
 
====Note: comps moved to Fedora Hosted git==== 


The R Packaging Guidelines have been updated:<ref>https://fedoraproject.org/wiki/Packaging:R</ref>
[[User:Nottingham|Bill Nottingham]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000590.html</ref>


The Scrollkeeper scriptlets were removed from the Packaging Guidelines:<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scrollkeeper</ref>
"As discussed both on-list, and at this week's FESCo meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-03-09/fesco.2010-03-09-20.00.txt</ref>
the 'comps' module used for mapping packages to package groups
in Fedora has moved from CVS to Fedora Hosted git.


The Python Packaging Guidelines were significantly rewritten including
You may view the module at:
changes to address:
http://git.fedorahosted.org/git/?p=comps.git
* Python 3
and check it out at any of:
* PyGTK2 and Numpy
http://git.fedorahosted.org/git/comps.git (r/o)
<ref>https://fedoraproject.org/wiki/Packaging:Python</ref>
git://git.fedorahosted.org/comps.git (r/o)
ssh://git.fedorahosted.org/git/comps.git (r/w, for packagers)


Dos2unix is no longer forbidden when removing DOS line breaks in a file:<ref>https://fedoraproject.org/wiki/Packaging/Guidelines#Rpmlint_Errors</ref>
Access control and policies remain the same. The old comps module in CVS will remain in a read-only state while users of it upgrade their scripts.


The Packaging Guidelines now contain a lengthy explanation of why Bundled Libraries are not permitted in Fedora: <ref>https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries</ref>
If you have any issues with the new location, please file a ticket in
release-engineering trac<ref>https://fedorahosted.org/rel-eng/newticket</ref>
Thanks,
Bill Nottingham"


The Packaging Guideline section on dealing with pre-built libraries has been improved:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-built_binaries_or_libraries</ref>
<references/>


Fedora packages no longer need to explicitly define a BuildRoot, as RPM now always defines one:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#BuildRoot_tag</ref>
====Release Notes Wiki Freeze====
John J. McDonough reminded<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000589.html</ref> the community that:


The Fedora Packaging Guidelines now contain more information on how to deal with Conflicting Files in scenarios involving "common names": <ref>https://fedoraproject.org/wiki/Packaging:Conflicts#Conflicting_Files</ref>
"Next week is the wiki freeze for Fedora 13 Release Notes.


There are now Packaging Guidelines for Wordpress Plugins:<ref>https://fedoraproject.org/wiki/Packaging:WordPress_plugin_packaging_guidelines</ref>
If you have something important that needs to be in the release notes, update the appropriate wiki beat<ref>http://fedoraproject.org/wiki/Documentation_Beats</ref>.


There are now Packaging Guidelines for Globus Toolkit components: <ref>https://fedoraproject.org/wiki/Packaging:Globus</ref>
Go above and select the appropriate beat.  Then add a note to that beat.


Since RPM now detects pkgconfig dependencies in all Fedora releases, it is no longer necessary for Fedora packages with .pc files to explicitly Require: pkgconfig :<ref>https://fedoraproject.org/wiki/PackagingGuidelines#Pkgconfig_Files</ref>
Your update need not be polished prose; if you can summarize the key
points that need to be documented and perhaps include a link to more
details, the Docs Project can take it from there.


Fedora packages should contain man pages for all included binaries and scripts, and if not present, Fedora packagers should work with upstream to add them: <ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Man_pages</ref>
As in Fedora 12, we are not looking to document every little change.
The release notes will highlight significant changes, and include a link to the upstream page for all changes.  If your component is hosted by Fedora, please consider enhancing the information pointed to by the yum link, which is what will appear in the release notes.


There are now Packaging Guidelines for MPI packages: <ref>https://fedoraproject.org/wiki/Packaging:MPI</ref>
Thanks for your help
--McD"


There are now Packaging Guidelines for proper usage of Environment Modules: <ref>https://fedoraproject.org/wiki/Packaging:EnvironmentModules</ref>
<references/>


There are now Packaging Guidelines for proper usage of Alternatives: <ref>https://fedoraproject.org/wiki/Packaging:Alternatives</ref>
=====Announcing the release of Fedora 13 Alpha!=====
[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000588.html</ref> the availability of Fedora 13 Alpha:


The Packaging Guidelines now have a section covering how to properly handle filtering of Automatic Provides and Requires:<ref>https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering</ref>
"The Fedora 13 "Goddard" Alpha release is available! What's next for the free operating system that shows off the best new technology of
tomorrow? You can see the future now<ref>http://fedoraproject.org/get-prerelease?anF13a</ref>


The GConf scriptlets have been rewritten to use macros (and be much simpler): <ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GConf</ref>
== What is the Alpha release? ==


The Guidelines concerning RPath have been clarified:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath</ref>
The Alpha release contains all the features of Fedora 13 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 13 is due in May.


The Guidelines concerning File and Directory ownership have been clarified:<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Ownership</ref>
We need your help to make Fedora 13 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.)


The Emacs Packaging Guidelines have been changed:<ref>https://fedoraproject.org/wiki/Packaging:Emacs</ref>
== Features ==


The PHP Packaging Guidelines have been changed:<ref>https://fedoraproject.org/wiki/Packaging:PHP</ref>
Among the top features for end users, we have:


The Fedora Packaging Guidelines now contain a section on dealing with Buildtime Macros in Source RPMS: <ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Source_RPM_Buildtime_Macros</ref>
    * Automatic print driver installation. We're using RPM and
PackageKit for automatic installation of printer drivers, so when you
plug in a USB printer, Fedora will automatically offer to install
drivers for it if needed.  


A clarification note has been added to the SourceURL section, reminding Fedora packagers to use "downloads.sourceforge.net": <ref>https://fedoraproject.org/wiki/Packaging:SourceURL#Sourceforge.net</ref>
    * Automatic installation of language packs. Yum language packs
plugin support makes software installation smarter and easier for
everyone worldwide, by automatically downloading language support for
large suites of Fedora software when the user's environment requires
it.  


These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC) and ratified by FESCo.
    * Redesigned user management interface. The user account tool has
been completely redesigned, and the accountsdialog and accountsservice test packages are available to make it easy to configure personal information, make a personal profile picture or icon, generate a strong passphrase, and set up login options for your Fedora system.  


Many thanks to Pierre-Yves Chibon, Remi Collet, Mattias Ellert, Adam Jackson, Jussi Lehtola, David Malcolm, Till Maas, Bill Nottingham, Orcan Ogetbil, Rahul Sundaram, Alexey Torkhov, Jonathan Underwood, Ivana Varekova, Ian Weller, Chris Weyl and all of the members of the FPC and FESCo, for assisting in drafting, refining, and passing these guidelines.
    * Color management. Color Management allows you to better set and
control your colors for displays, printers, and scanners, through the
gnome-color-manager package.  


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:<ref>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
    * NetworkManager improvements include CLI. NetworkManager is now a one stop shop for all of your networking needs in Fedora, be it dial-up, broadband, wifi, or even Bluetooth. And now it can all be done in the command line, if you're into that sort of thing.  


<references/>
    * Experimental 3D extended to free Nouveau driver for NVidia cards. In this release we are one step closer to having 3D supported on completely free and open source software (FOSS) drivers. In Fedora 12 we got a lot of ATI chips working, and this time we've added a wide range of NVidia cards. You can install the mesa-dri-drivers-experimental package to try out the work in progress.


====Build F-13 collection packages for all language translators==== 
For developers there are all sorts of additional goodies:
[[User:Noriko|Noriko Mizumoto]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000583.html</ref> to the Fedora package maintainers, "This is kind reminder asking you to rebuild your package with latest translation. Localization team has been translating for updated and/or newly added strings since the String is frozen (2010-02-09). To allow translators to review and correct their latest translation in UI, this is essential. This is different from 'Rebuild all translated packages for Beta', this is added entry since Fedora 12<ref>http://poelstra.fedorapeople.org/schedules/f-13/f-13-devel-tasks.html</ref>.


"Build F-13 collection packages for all language translators" is expected between 2010-03-03 to 2010-03-05. Please make sure your build
    * SystemTap static probes. SystemTap now has expanded capabilities to monitor higher-level language runtimes like Java, Python and Tcl, and also user space applications starting with PostgreSQL. In the future Fedora will add support for even more user space applications, greatly increasing the scope and power of monitoring for application developers.  
is completed by 2010-03-05, so that a live image to be composed on 2010-03-05.


The packages to be built are:
    * Easier Python debugging. We've added new support that allows
* ABRT » master
developers working with mixed libraries (Python and C/C++) in Fedora to get more complete information when debugging with gdb, making Fedora an exceptional platform for powerful, rapid application development.
* anaconda » master
* audit-viewer » tip
* authconfig » tip
* chkconfig » master
* comps » HEAD
* desktop-backgrounds » HEAD
* desktop-effects » master
* firstboot » master
* im-chooser » trunk
* initscripts » master
* iok » trunk
* kexec-tools » HEAD
* libuser » tip
* liveusb-creator » master
* mlocate » tip
* multimedia-menus » master
* newt » master
* passwd » tip
* policycoreutils » HEAD
* pykickstart » master
* python-meh » master
* readahead » master
* redhat-menus » HEAD
* setroubleshoot » tip-framework
* setroubleshoot » tip-plugins
* setuptool » master
* smolt » master
* smolt » master-smoon
* sos » trunk
* switchdesk » HEAD
* system-config-audit » tip
* system-config-bind » tip
* system-config-boot » master
* system-config-date » master-docs
* system-config-date » master
* system-config-date » master-timezones
* system-config-display » master
* system-config-firewall » master
* system-config-httpd » tip
* system-config-kdump » new
* system-config-keyboard » trunk
* system-config-kickstart » master
* system-config-language » trunk
* system-config-lvm » master
* system-config-netboot » trunk
* system-config-network » master
* system-config-nfs » master
* system-config-nfs » master-docs
* system-config-printer » master
* system-config-rootpassword » trunk
* system-config-samba » master
* system-config-samba » master-docs
* system-config-services » master
* system-config-services » master-docs
* system-config-users » master
* system-config-users » master-docs
* system-switch-java » tip
* system-switch-mail » HEAD
* usermode » tip"


<references/>
    * Parallel-installable Python 3 stack. The parallel-installable
Python 3 stack will will help programmers write and test code for use in both Python 2.6 and Python 3 environments, so you can future-proof your applications now using Fedora.


====Fedora 13 Alpha Go/No-Go Meeting====
    * NetBeans 6.8 first IDE to support entire Java 6 EE spec. NetBeans IDE 6.8 is the first IDE to offer complete support for the entire Java EE 6 specification.  
=====Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 at 19:00 UTC (14:00 EST)===== 
[[User:Adamwill|Adam Williamson]] announced as an important note<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "...we are rescheduling the Go/No-Go meeting for Fedora 13 Alpha. Previously scheduled for 2010-02-25 01:00 UTC, it is now scheduled for 2010-02-25 19:00 UTC (14:00 EST, 11:00 PST). This delay is to give sufficient time for the QA team to test the expected RC3 build.


The original announcement, with the new time, is reproduced below for reference.
And don't think we forgot the system administrators:


Join us on irc.freenode.net #fedora-meeting for this important meeting.
    * boot.fedoraproject.org. (BFO) allows users to download a single, tiny image (could fit on a floppy) and install current and future versions of Fedora without having to download additional images.  
Thursday, February 25, 2010 @ 19:00 UTC (14:00 EST).


"Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular
    * System Security Services Daemon (SSSD). SSSD provides expanded
release. This meeting is called the: Go/No-Go Meeting."
features for logging into managed domains, including caching for offline authentication. This means that, for example, users on laptops can still login when disconnected from the company's managed network. The authentication configuration tool in Fedora has already been updated to support SSSD, and work is underway to make it even more attractive and functional.  


"Verifying that the Release criteria are met is the responsibility of the QA Team."
    * Pioneering NFS features. Fedora offers the latest version 4 of the NFS protocol for better performance, and in conjunction with recent kernel modifications includes IPv6 support for NFS as well.  


For more details about this important meeting see: <ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"
    * Zarafa Groupware. Zarafa now makes available a complete Open
Source groupware suite that can be used as a drop-in Exchange
replacement for Web-based mail, calendaring, collaboration and tasks.
Features include IMAP/POP and iCal/CalDAV capabilities, native mobile
phone support, the ability to integrate with existing Linux mail
servers, a full set of programming interfaces, and a comfortable look
and feel using modern Ajax technologies.  


<references/>
    * Btrfs snapshots integration. Btrfs is capable of creating
lightweight filesystem snapshots that can be mounted (and booted into) selectively. The created snapshots are copy-on-write snapshots, so there is no file duplication overhead involved for files that do not change between snapshots. It allows developers to feel comfortable experimenting with new software without fear of an unusable install, since automated snapshots allow them to easily revert to the previous day's filesystem.


=====Feodra 13 Alpha slip by one week=====
And that's only the beginning. A more complete list and details of each new cited feature is available<ref>http://fedoraproject.org/wiki/Releases/13/FeatureList?anF13a</ref>
[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000581.html</ref> on the basis of the announcement<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "Today at the go / no-go meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-02-25/fedora-meeting.2010-02-25-18.59.log.html</ref> we decided to slip the Alpha by one week.  This slip is needed to verify blocker bug fixes and validate new builds of software necessary to fix those bugs.  We are confident that the fixes we have are valid, however we do not have enough time to prove them valid.  We will spend the next few days doing that validation.  In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be pushed unless they are fixing a release blocking issue.  Once we've validated all the fixes we will do more frequent pushes to 13 stable.
At this time we are not adjusting later milestone dates, as with no frozen rawhide we are not taking away any developer time." 


<references/>
We have nightly composes of alternate spins available<ref>http://alt.fedoraproject.org/pub/alt/nightly-composes/?anF13a</ref>


=====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC (2010-03-03 @ 20:00 EST)===== 
== Contributing ==
[[User:Adamwill|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000582.html</ref>, "Join us on irc.freenode.net #fedora-meeting for this important meeting. This is Thursday, March 4, 2010 @ 01:00 UTC, which makes it '''WEDNESDAY EVENING''' in North America: 20:00 EST, 17:00 PST.


"Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular
For more information including common and known bugs, tips on how to
release. This meeting is called the: Go/No-Go Meeting."
report bugs, and the official release schedule, please refer to the
release notes<ref>http://fedoraproject.org/wiki/Fedora_13_Alpha_release_notes?anF13a</ref>


"Verifying that the Release criteria are met is the responsibility of the QA Team."
Thank you, and we hope to see you in the Fedora project!


For more details about this important meeting see:<ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating


<references/>
<references/>


=====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC Recap=====
=====F13 Release Slogan - Rock it.=====  
[[/User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000585.html</ref> the meeting summary, "Representatives from Fedora QA, Rel-Eng and Development met on IRC to review determine whether the Fedora 13 Alpha release criteria<ref>https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria</ref> have been met.  The team agreed that the Alpha criteria have been met, and to proceed with releasing F-13-Alpha-RC4.  For additional details, please refer to the attached minutes.
[[User:Rbergeron|Robyn Bergeron]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000587.html</ref> the slogan for Fedora 13:
 
* '''fedora-meeting: F-13-Alpha engineering readiness meeting'''
 
Meeting started by jlaska at 01:00:03 UTC. The full logs are available at <ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-03-04/f-13-alpha-eng-readiness.2010-03-04-01.00.log.html</ref>.


'''Meeting summary'''
"For the 13th Release of Fedora, "Goddard," the Fedora Marketing team
* Waiting for critical mass . (jlaska, 01:00:25)
ran an open, community based process of slogan submissions,<ref>https://fedoraproject.org/wiki/Release_slogan_SOP</ref>. That processincluded guidelines for producing great slogans, and as a result ofour call, we received a large number of slogan contributions<ref>https://fedoraproject.org/wiki/F13_release_slogan</ref>
* adamw representing QA  (jlaska, 01:03:02)
* Oxf13 representing Rel-Eng  (jlaska, 01:03:07)
* Oxf13 wearing the notting mask, representing Devel  (jlaska,01:03:21)


'''Why are we here?'''  (jlaska, 01:03:44)
After an exciting and enjoyable Marketing Team meeting, the release
* The purpose is to decide whether the alpha has met the release criteria  (jlaska, 01:03:49)
slogan for Fedora 13 "Goddard" has been chosen and approved: "Rock
* LINK:<ref>https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria</ref>(jlaska, 01:03:54)
it!"


'''Go or No Go?'''  (jlaska, 01:04:57)
We would like to thank all the contributors who have participated in
* all desktop and install validation tests for alpha point have been run  (jlaska, 01:08:36)
this process.
* only bug blocking alpha is <ref>https://bugzilla.redhat.com/show_bug.cgi?id=567346</ref> - we have decided it's okay as it has a usable workaround, so we should take it off the list  (jlaska, 01:08:52)
* ACTION: Decided that bug#567346 can be removed from F13Alpha(jlaska, 01:13:10)
* LINK: <ref>https://fedoraproject.org/wiki/Common_F13_bugs#yum-langpacks</ref>(jlaska, 01:15:09)
* IDEA: should KDE Live image be respun to address kpackagekit issue?(jlaska, 01:16:44)
* source DVD is 5.0G  (Oxf13, 01:20:49)
* IDEA: need to determine how to handle source ISO's for F-13-Final(jlaska, 01:24:01)
* ACTION: several remaining CommonBugs? needing documentation(jlaska, 01:25:15)
* AGREED: QA + Rel-Eng + Devel* agreed to proceed with releasing F-13-Alpha-RC4 as the Alpha  (jlaska, 01:26:09)


'''What's next?'''  (jlaska, 01:26:38)
Cheers!
* ACTION: adamw + jlaska to document remaining CommonBugs? issues(jlaska, 01:28:44)
* LINK: <ref>http://fedoraproject.org/wiki/Fedora_12_Alpha_Announcement</ref>  (Oxf13, 01:32:06)
* ACTION: jlaska - send out the meeting minutes to devel-announce@test-announce@ and logistics@  (jlaska, 01:33:34)
* expect to be fully staged for mirrors by tomorrow  (Oxf13, 01:34:16)


'''Open Discussion'''  (jlaska, 01:34:45)
-Robyn


Meeting ended at 01:36:45 UTC.
'''Action Items'''
* Decided that bug#567346 can be removed from F13Alpha
* several remaining CommonBugs? needing documentation
* adamw + jlaska to document remaining CommonBugs? issues
* jlaska - send out the meeting minutes to devel-announce@test-announce@ and logistics@
'''Action Items, by person'''
* adamw
  * adamw + jlaska to document remaining CommonBugs? issues
* jlaska
  * adamw + jlaska to document remaining CommonBugs? issues
  * jlaska - send out the meeting minutes to devel-announce@
    test-announce@ and logistics@
* **UNASSIGNED**
  * Decided that bug#567346 can be removed from F13Alpha
  * several remaining CommonBugs? needing documentation
'''People Present (lines said)'''
* jlaska (67)
* Oxf13 (41)
* adamw (32)
* juhp (10)
* poelcat (6)
* rhe (4)
* zodbot (4)
* skvidal (2)
<references/>
<references/>


Revision as of 15:57, 15 March 2010

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Pascal Calarco

  1. ↑ http://lists.fedoraproject.org/pipermail/announce/
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/
  3. ↑ http://fedoraproject.org/wiki/Events

Fedora Announcement News

There were no announcements on the announce@lists.fedoraproject.org last week.

Fedora Development News

Google Summer of Code proposal: Better iptables management

Zubin Mithra[1] invited comments[2] on a Google Summer of Code proposal to improve iptables in Fedora:

"My name is Zubin Mithra and I am aspiring to get into GSoC on behalf of Fedora. I wish to work on making a library for better iptables management. Details can be viewed in the proposal which I have attached along with the email.

I would love to hear your views on it."

A PDF[3] of the proposal is available.

  1. ↑ Zubin Mithra
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000591.html
  3. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/attachments/20100312/60f1c65f/attachment-0001.pdf

Note: comps moved to Fedora Hosted git

Bill Nottingham announced[1]

"As discussed both on-list, and at this week's FESCo meeting[2] the 'comps' module used for mapping packages to package groups in Fedora has moved from CVS to Fedora Hosted git.

You may view the module at: http://git.fedorahosted.org/git/?p=comps.git and check it out at any of: http://git.fedorahosted.org/git/comps.git (r/o) git://git.fedorahosted.org/comps.git (r/o) ssh://git.fedorahosted.org/git/comps.git (r/w, for packagers)

Access control and policies remain the same. The old comps module in CVS will remain in a read-only state while users of it upgrade their scripts.

If you have any issues with the new location, please file a ticket in release-engineering trac[3]

Thanks, Bill Nottingham"

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000590.html
  2. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2010-03-09/fesco.2010-03-09-20.00.txt
  3. ↑ https://fedorahosted.org/rel-eng/newticket

Release Notes Wiki Freeze

John J. McDonough reminded[1] the community that:

"Next week is the wiki freeze for Fedora 13 Release Notes.

If you have something important that needs to be in the release notes, update the appropriate wiki beat[2].

Go above and select the appropriate beat. Then add a note to that beat.

Your update need not be polished prose; if you can summarize the key points that need to be documented and perhaps include a link to more details, the Docs Project can take it from there.

As in Fedora 12, we are not looking to document every little change. The release notes will highlight significant changes, and include a link to the upstream page for all changes. If your component is hosted by Fedora, please consider enhancing the information pointed to by the yum link, which is what will appear in the release notes.

Thanks for your help --McD"

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000589.html
  2. ↑ http://fedoraproject.org/wiki/Documentation_Beats
Announcing the release of Fedora 13 Alpha!

Jesse Keating announced[1] the availability of Fedora 13 Alpha:

"The Fedora 13 "Goddard" Alpha release is available! What's next for the free operating system that shows off the best new technology of tomorrow? You can see the future now[2]

What is the Alpha release?

The Alpha release contains all the features of Fedora 13 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 13 is due in May.

We need your help to make Fedora 13 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

Among the top features for end users, we have: 

   * Automatic print driver installation. We're using RPM and

PackageKit for automatic installation of printer drivers, so when you plug in a USB printer, Fedora will automatically offer to install drivers for it if needed. 

   * Automatic installation of language packs. Yum language packs

plugin support makes software installation smarter and easier for everyone worldwide, by automatically downloading language support for large suites of Fedora software when the user's environment requires it. 

   * Redesigned user management interface. The user account tool has

been completely redesigned, and the accountsdialog and accountsservice test packages are available to make it easy to configure personal information, make a personal profile picture or icon, generate a strong passphrase, and set up login options for your Fedora system. 

   * Color management. Color Management allows you to better set and

control your colors for displays, printers, and scanners, through the gnome-color-manager package. 

   * NetworkManager improvements include CLI. NetworkManager is now a one stop shop for all of your networking needs in Fedora, be it dial-up, broadband, wifi, or even Bluetooth. And now it can all be done in the command line, if you're into that sort of thing. 

   * Experimental 3D extended to free Nouveau driver for NVidia cards. In this release we are one step closer to having 3D supported on completely free and open source software (FOSS) drivers. In Fedora 12 we got a lot of ATI chips working, and this time we've added a wide range of NVidia cards. You can install the mesa-dri-drivers-experimental package to try out the work in progress.

For developers there are all sorts of additional goodies: 

   * SystemTap static probes. SystemTap now has expanded capabilities to monitor higher-level language runtimes like Java, Python and Tcl, and also user space applications starting with PostgreSQL. In the future Fedora will add support for even more user space applications, greatly increasing the scope and power of monitoring for application developers. 

   * Easier Python debugging. We've added new support that allows

developers working with mixed libraries (Python and C/C++) in Fedora to get more complete information when debugging with gdb, making Fedora an exceptional platform for powerful, rapid application development. 

   * Parallel-installable Python 3 stack. The parallel-installable

Python 3 stack will will help programmers write and test code for use in both Python 2.6 and Python 3 environments, so you can future-proof your applications now using Fedora. 

   * NetBeans 6.8 first IDE to support entire Java 6 EE spec. NetBeans IDE 6.8 is the first IDE to offer complete support for the entire Java EE 6 specification.

And don't think we forgot the system administrators: 

   * boot.fedoraproject.org. (BFO) allows users to download a single, tiny image (could fit on a floppy) and install current and future versions of Fedora without having to download additional images. 

   * System Security Services Daemon (SSSD). SSSD provides expanded

features for logging into managed domains, including caching for offline authentication. This means that, for example, users on laptops can still login when disconnected from the company's managed network. The authentication configuration tool in Fedora has already been updated to support SSSD, and work is underway to make it even more attractive and functional. 

   * Pioneering NFS features. Fedora offers the latest version 4 of the NFS protocol for better performance, and in conjunction with recent kernel modifications includes IPv6 support for NFS as well. 

   * Zarafa Groupware. Zarafa now makes available a complete Open

Source groupware suite that can be used as a drop-in Exchange replacement for Web-based mail, calendaring, collaboration and tasks. Features include IMAP/POP and iCal/CalDAV capabilities, native mobile phone support, the ability to integrate with existing Linux mail servers, a full set of programming interfaces, and a comfortable look and feel using modern Ajax technologies. 

   * Btrfs snapshots integration. Btrfs is capable of creating

lightweight filesystem snapshots that can be mounted (and booted into) selectively. The created snapshots are copy-on-write snapshots, so there is no file duplication overhead involved for files that do not change between snapshots. It allows developers to feel comfortable experimenting with new software without fear of an unusable install, since automated snapshots allow them to easily revert to the previous day's filesystem.

And that's only the beginning. A more complete list and details of each new cited feature is available[3]

We have nightly composes of alternate spins available[4]

Contributing

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[5]

Thank you, and we hope to see you in the Fedora project!

-- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000588.html
  2. ↑ http://fedoraproject.org/get-prerelease?anF13a
  3. ↑ http://fedoraproject.org/wiki/Releases/13/FeatureList?anF13a
  4. ↑ http://alt.fedoraproject.org/pub/alt/nightly-composes/?anF13a
  5. ↑ http://fedoraproject.org/wiki/Fedora_13_Alpha_release_notes?anF13a
F13 Release Slogan - Rock it.

Robyn Bergeron announced[1] the slogan for Fedora 13:

"For the 13th Release of Fedora, "Goddard," the Fedora Marketing team ran an open, community based process of slogan submissions,[2]. That processincluded guidelines for producing great slogans, and as a result ofour call, we received a large number of slogan contributions[3]

After an exciting and enjoyable Marketing Team meeting, the release slogan for Fedora 13 "Goddard" has been chosen and approved: "Rock it!"

We would like to thank all the contributors who have participated in this process.

Cheers!

-Robyn

  1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000587.html
  2. ↑ https://fedoraproject.org/wiki/Release_slogan_SOP
  3. ↑ https://fedoraproject.org/wiki/F13_release_slogan

Fedora Events

Fedora events are the source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (March 2010 to May 2010)

  • North America (NA)[1]
  • Central & South America (LATAM) [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]
  1. ↑ http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29
  2. ↑ http://fedoraproject.org/wiki/Events#FY10_Q4_.28March_2010_-_May_2010.29
  3. ↑ http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_2
  4. ↑ http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_3

Past Events

Archive of Past Fedora Events[1]

  1. ↑ http://fedoraproject.org/wiki/FedoraEvents/PastEvents

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.
Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Announcements&oldid=159479"