From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 12: Line 12:
'''THE BREAKING news (Fedora 12 (Constantine) related) are as follows''':  
'''THE BREAKING news (Fedora 12 (Constantine) related) are as follows''':  


===New channel on freenode called #fedora-fad===
==FEDORA ANNOUNCE LIST==


Gerold Kassube announced<ref>http://www.redhat.com/archives/fedora-announce-list/2009-September/msg00006.html</ref> the new IRC-Channel #fedora-fad which is opened right now for everybody to attend a FAD (== Fedora Activity Day) online. Gerold mentioned, “I created that channel, because of some people asked (also in the past) about who cann't attend a FAD. The next FAD in EMEA takes place (again and by tradition) in Rheinfelden, Germany on the next weekend <ref>https://fedoraproject.org/wiki/FAD_EMEA_2009</ref>.
===Reminder: Fedora Board IRC meeting 1600 UTC 2009-10-01===
” 
Paul W. Frields announced,"The Board is holding its monthly public meeting on Thursday, October
1, 2009, at 1600 UTC on IRC Freenode.<ref>http://www.redhat.com/archives/fedora-announce-list/2009-September/msg00009.html</ref>"


<references/>
<references/>


===All Features Need to be 100% by Beta Freeze (2009-09-29)===
==FEDORA DEVELOPMENT ANNOUNCEMENTS==


John Poelstra had explicitly announced<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00008.html</ref> that All Features Need to be 100% by Beta Freeze by Tuesday, September 29th, 2009.
===Final Review of Incomplete Fedora 12 Features===
John Poelstra announced,<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00000.html</ref>


Beta Freeze <ref>https://fedoraproject.org/wiki/Beta_Freeze_Policy</ref> means that all features and their associated feature pages must be at 100% completion by this date. The following features are currently not 100% complete and need to be by Tuesday, September 29, 2009. In many cases it appears they are just 1% away.  
"With the passing of Beta Freeze we are now at the point in our release process where we expect all features to be at 100% completion. After requesting status updates, including direct email to the feature owners, the following feature pages do not have a current status.


<ref>https://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00008.html</ref>
<ref>https://fedoraproject.org/wiki/Features/DisplayPort</ref>
<ref>https://fedoraproject.org/wiki/Features/DisplayPort</ref>
<ref>https://fedoraproject.org/wiki/Anaconda/Features/FCoE</ref>
<ref>https://fedoraproject.org/wiki/Features/FedoraStudio</ref>
<ref>https://fedoraproject.org/wiki/Features/GFS2ClusteredSamba</ref>
<ref>https://fedoraproject.org/wiki/Features/Gnome2.28</ref>
<ref>https://fedoraproject.org/wiki/Features/KVM_Huge_Page_Backed_Memory</ref>
<ref>https://fedoraproject.org/wiki/Features/liblvm</ref>
<ref>https://fedoraproject.org/wiki/Features/LowerProcessCapabilities</ref>
<ref>https://fedoraproject.org/wiki/Features/LowerProcessCapabilities</ref>
<ref>https://fedoraproject.org/wiki/Features/MoreNetworkManagerMobileBroadband</ref>
<ref>https://fedoraproject.org/wiki/Features/PolicyKitOne</ref>
<ref>https://fedoraproject.org/wiki/Features/FedoraMoblin</ref>
<ref>https://fedoraproject.org/wiki/Features/NFSv4Default</ref>
<ref>https://fedoraproject.org/wiki/Features/NFSv4Default</ref>
<ref>https://fedoraproject.org/wiki/Features/PackageKitBrowserPlugin</ref>
<ref>https://fedoraproject.org/wiki/Features/SystemTapEclipseGUI</ref>
<ref>https://fedoraproject.org/wiki/Features/SystemtapTracingRefresh</ref>
<ref>https://fedoraproject.org/wiki/Features/Thusnelda</ref>
<ref>https://fedoraproject.org/wiki/Features/VolumeControlContinued</ref>
<ref>https://fedoraproject.org/wiki/Features/XI2</ref>
<ref>https://fedoraproject.org/wiki/Features/F12X86Support</ref>


In accordance with our recorded policy of requiring that all features be at 100% at Beta Freeze, I am proposing these features for your review to determine what their disposition should be.
<ref>https://fedoraproject.org/wiki/Features/Policy/Dropping</ref>"


Poel also mentioned, “I will raise feature pages not at 100% at FESCo's meeting on October 2, 2009. Hopefully my job will be easy and there there won't be any.”
<references/>


<references/>
===Buyer Beware: A Major Change in NFS is about to happen===
Steve Dickson announced as follows,<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00013.html</ref>
 
As part of the NFSv4 Default <ref>https://fedoraproject.org/wiki/Features/NFSv4Default</ref> feature
I am one commit away from changing the default protocol version NFS will
be using (or at least trying to use).
 
What does this means to you? Hopefully nothing! In theory this should
be a very seamless transition but with all new technology there
will be (and are) some rough spots.
 
Why are make the change? See the NFSv4Default wiki for details,
but in a nutshell:
    * Better performance - V4 is now a stateful protocol. Meaning the server keeps
      state on all the clients access a particular file or directory. This
      allows the server to give out delegations (or leases) which in turn
      allows the client to aggressive cache both data and meta data locally
 
    * Firewall Friendly- With v4 only one port is used 2049 for all traffic
      including mounting and file locking.
 
    * Finally it enables us use upcoming minor releases of the the protocol.
      NFS version 4.1 and pNFS are two example of upcoming minor releases.
 
 
FYI, V4 was introduced in Fedora Core 2 so it has been around for a while. I
personally have been using it for my home directory for a couple years now..
For more of the nitty gritty details see 
    http://www.iaps.com/NFSv4-new-features.html
 
That's the good news... Here is the bad....


===GraphicsMagick-1.3.x for F-11 (ABI change)===
Because the mount command will try NFS v4 first, mounts to older Linux servers
will start failing like:


Rex Dieter announced<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00004.html</ref>, “Heads up, I'm working on a GM-1.3.7 update to F-11 which includes an ABI break. I'll be taking care of building/fixing dependent packages (including dvdauthor, koffice).”
# mount linux-server:/export /mnt
mount.nfs: mounting linux-server:/export failed, reason given by server:
    No such file or directory


<references/>
This is due to a defect in the Linux server exporting code, which is fixed
in F-12, *but* there are a number of workarounds


===Announcing Fedora 12 Snapshot 3===
On the server (Which is suggested):
  * Add the following entry to the /etc/exports file:
    / *(ro,fsid=0) Note: 'fsid=0' is explained in the exports(5) man pages.


“Fedora 12 Snapshot 3 is now available for testing. These snapshots
On the client, go back to v3 mounts by doing one of the following:
consist of live images only.  These were composed yesterday, and made
available today.” announced Jesse Keating<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00005.html</ref><ref>http://torrent.fedoraproject.org/</ref><ref>http://spins.fedoraproject.org/</ref>
Jessy requested to report issues in bugzilla.


<references/>
  * Add -o v3 to command line, similar to:
        mount linux-server:/export /mnt


===Updating libchamplain to 0.4.0===
  * Change the default mount version in the new /etc/nfsmount.conf file by
Debarshi Ray included<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00006.html</ref>
    uncommenting the Nfsvers=3 setting in the 'NFSMount_Global_Options' section.
, “I am going to build libchamplain-0.4.0 for Rawhide in a few hours and this involves a change in the soname that will affect:
    See nfsmount.conf(5) man page for details. The diff would look like:
+ eog-plugins
+ empathy”


        --- /etc/nfsmount.conf 2009-09-29 16:58:13.000000000 -0400
        +++ /tmp/nfsmount.conf 2009-09-29 16:56:04.000000000 -0400
        @@ -29,7 +29,7 @@
        # options that can be applied on all NFS mount.
        #
        # Protocol Version [2,3,4]
        -#Nfsvers=3
        +Nfsvers=3
        # Network Transport [Udp,Tcp,Rdma]
        # Proto=Tcp
        #
<references/>
<references/>


===Fedora 12 Mass Branching coming soon===
===Fedora 12 Freeze at 0600~ 2009-09-30 UTC===
Jesse Keating briefly announced, "Just a reminder that the Fedora 12 freeze will be happening tonight at
0600 2009-09-30 UTC, just prior to the rawhide compose tonight.  The
rawhide for 20090930 will be built from frozen content.  You do not need
to send tag requests until after that.<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00012.html</ref>"


Jesse Keating announced<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00007.html</ref>, “Per the Fedora 12 Schedule<ref>http://fedoraproject.org/wiki/Schedule</ref>
<references/>
, mass branching for Fedora 12 will happen on
the 28th of September, which is this coming Monday.  There will be a
short CVS outage associated with this event.  The exact timing of this
outage has not been decided yet, but we will send the outage
notification when it has been decided.”


===Re: CVS Outage Notification - 2009-09-29 04:25 UTC===
"It was pointed out to me that many of the packages starting with "a"
were not properly branched.  I've restarted the branch run for the "a"
packages, however this time email will go out for the branch events, and
this won't incur another outage.  The branching of "a" packages should
be done in 10 or 15 minutes.<ref>http://www.redhat.com/archives/fedora-devel-announce/2009-September/msg00011.html</ref>
", replied Jesse Keating. 
<references/>
<references/>
==FEDORA EVENTS==
Mark your agenda with the following events. Please, consider attending or volunteering at an event near you!


===Upcoming Events===
===Upcoming Events===
    * North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29</ref>
    * Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_2</ref>
    * Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_3</ref>
    * India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_4</ref>


Mark your agenda with the following events. Please, consider attending or volunteering at an event near you!
<references/>


* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29</ref>
===Past Events===
* Central & South America (LATAM)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_2</ref>
Archieve of Past Fedora Events<ref>http://fedoraproject.org/wiki/Events#Past_Events</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_3</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_4</ref>


<references/>
<references/>

Revision as of 12:07, 5 October 2009

Announcements

In this section, we cover announcements from the Fedora Project[1] [2] [3].

Contributing Writer: Rashadul Islam

THE BREAKING news (Fedora 12 (Constantine) related) are as follows:

FEDORA ANNOUNCE LIST

Reminder: Fedora Board IRC meeting 1600 UTC 2009-10-01

Paul W. Frields announced,"The Board is holding its monthly public meeting on Thursday, October 1, 2009, at 1600 UTC on IRC Freenode.[1]"

FEDORA DEVELOPMENT ANNOUNCEMENTS

Final Review of Incomplete Fedora 12 Features

John Poelstra announced,[1]

"With the passing of Beta Freeze we are now at the point in our release process where we expect all features to be at 100% completion. After requesting status updates, including direct email to the feature owners, the following feature pages do not have a current status.

[2] [3] [4] [5]

In accordance with our recorded policy of requiring that all features be at 100% at Beta Freeze, I am proposing these features for your review to determine what their disposition should be. [6]"

Buyer Beware: A Major Change in NFS is about to happen

Steve Dickson announced as follows,[1]

As part of the NFSv4 Default [2] feature I am one commit away from changing the default protocol version NFS will be using (or at least trying to use).

What does this means to you? Hopefully nothing! In theory this should be a very seamless transition but with all new technology there will be (and are) some rough spots.

Why are make the change? See the NFSv4Default wiki for details, but in a nutshell:

   * Better performance - V4 is now a stateful protocol. Meaning the server keeps 
     state on all the clients access a particular file or directory. This
     allows the server to give out delegations (or leases) which in turn
     allows the client to aggressive cache both data and meta data locally
   * Firewall Friendly- With v4 only one port is used 2049 for all traffic
     including mounting and file locking.
   * Finally it enables us use upcoming minor releases of the the protocol. 
     NFS version 4.1 and pNFS are two example of upcoming minor releases.


FYI, V4 was introduced in Fedora Core 2 so it has been around for a while. I personally have been using it for my home directory for a couple years now.. For more of the nitty gritty details see

   http://www.iaps.com/NFSv4-new-features.html 

That's the good news... Here is the bad....

Because the mount command will try NFS v4 first, mounts to older Linux servers will start failing like:

# mount linux-server:/export /mnt
mount.nfs: mounting linux-server:/export failed, reason given by server:
   No such file or directory

This is due to a defect in the Linux server exporting code, which is fixed in F-12, *but* there are a number of workarounds

On the server (Which is suggested):

  * Add the following entry to the /etc/exports file:
    / *(ro,fsid=0) Note: 'fsid=0' is explained in the exports(5) man pages.

On the client, go back to v3 mounts by doing one of the following:

  * Add -o v3 to command line, similar to:
       mount linux-server:/export /mnt
  * Change the default mount version in the new /etc/nfsmount.conf file by 
    uncommenting the Nfsvers=3 setting in the 'NFSMount_Global_Options' section.
    See nfsmount.conf(5) man page for details. The diff would look like:
       --- /etc/nfsmount.conf	2009-09-29 16:58:13.000000000 -0400
       +++ /tmp/nfsmount.conf	2009-09-29 16:56:04.000000000 -0400
       @@ -29,7 +29,7 @@
        # options that can be applied on all NFS mount.
        #
        # Protocol Version [2,3,4]
       -#Nfsvers=3
       +Nfsvers=3
        # Network Transport [Udp,Tcp,Rdma]
        # Proto=Tcp
        #

Fedora 12 Freeze at 0600~ 2009-09-30 UTC

Jesse Keating briefly announced, "Just a reminder that the Fedora 12 freeze will be happening tonight at 0600 2009-09-30 UTC, just prior to the rawhide compose tonight. The rawhide for 20090930 will be built from frozen content. You do not need to send tag requests until after that.[1]"

Re: CVS Outage Notification - 2009-09-29 04:25 UTC

"It was pointed out to me that many of the packages starting with "a" were not properly branched. I've restarted the branch run for the "a" packages, however this time email will go out for the branch events, and this won't incur another outage. The branching of "a" packages should be done in 10 or 15 minutes.[1] ", replied Jesse Keating.

FEDORA EVENTS

Mark your agenda with the following events. Please, consider attending or volunteering at an event near you!

Upcoming Events

   * North America (NA)[1]
   * Central & South America (LATAM) [2]
   * Europe, Middle East, and Africa (EMEA)[3]
   * India, Asia, Australia (India/APJ)[4]

Past Events

Archieve of Past Fedora Events[1]