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:pcalarco|Pascal Calarco]]
Contributing Writer: [[User:Rashadul|Rashadul Islam]]


<references/>
<references/>
Line 14: Line 14:
<references/>
<references/>


====Changes to the Packaging Guidelines====
====Vote for your favorite Fedora 16 release name====  
[[User:Spot|Tom 'Spot' Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002942.html</ref>,


"Here are the changes to the Fedora Packaging Guidelines for this week:
Jared K. Smith<ref>Jared K. Smith jsmith at fedoraproject.org</ref> on Mon Apr 4 14:04:41 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-April/002944.html</ref> the Vote for your favorite Fedora 16 release name. The details of the announcement are as follows.


The Packaging:PHP guidelines have been updated to reflect that PEAR
"The time has come to vote for the release name for Fedora 16. The
documentation provided by upstream are installed in %{pear_docdir},
Fedora community has submitted quite a few suggestions for the Fedora
should stay there, and must be marked as %doc.
16 release name, and that list has been narrowed down to the final
nine candidates. Now you can vote on these names and assist in the
final selection for the successor of Fedora 15 "Lovelock".


Additionally, the definition of pear_docdir has been defined as %{_docdir}/pear.
'''This vote begins 5 April 2011 and runs until 11 April 2011 at
23:59:59 UTC.''' Other important facts:


https://fedoraproject.org/wiki/Packaging:PHP
* We are using the Range Voting method
(<ref>http://en.wikipedia.org/wiki/Range_voting</ref>)


---
* Ballots may be cast on the Fedora Elections System at
<ref>https://admin.fedoraproject.org/voting</ref>


The Java guidelines have been updated to add information and sample template for Maven 3 (Fedora 15+).
* If this is the first time you've used the voting system, you might
want to read the Fedora Elections Guide, currently located at
<ref>http://pfrields.fedorapeople.org/documents/elections-guide/</ref>


https://fedoraproject.org/wiki/Packaging:Java
* To vote, you must have a valid Fedora Contributors License Agreement
(CLA) and be a member of at least one non-CLA group


---
To vote, visit: <ref>https://admin.fedoraproject.org/voting/about/relnamef16</ref>


These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).
Thank you to everyone who helped by contributing names for
consideration, and reviewing the names for the final ballot."


Many thanks to Remi Collet, Stanislav Ochotnicky, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.
<references/>
 
====Outage: hosted servers 2011-04-12 04:00 UTC==== 
 
Stephen John Smoogen<ref>Stephen John Smoogen smooge at gmail.com</ref> on Wed Apr 6 17:16:42 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-April/002945.html</ref>,
 
"There will be an outage starting at 2011-04-12 04:00  UTC, which will last
approximately 6 hours.


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
To convert UTC to your local time, take a look at
<ref>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>


Thanks,
or run:
'''date -d '  2011-04-12 04:00 UTC''''


~spot"
=====Reason for outage:=====
 
Serverbeach (our service provider for our hosted and other servers)
are upgrading switches in their San Antonio (SAT) Datacenter. The
outage for our systems are supposed to be 15 minutes but can be
anywhere within that 6 hours.
 
=====Affected Services:=====
 
Email system
Fedora Hosted - <ref>https://fedorahosted.org/</ref>
Fedora People - <ref>http://fedorapeople.org/</ref>
 
=====Unaffected Services:=====
 
Most services should stay up, however various items depending on
fedorahosted will be affected (which may then affect other services,
etc etc.)
 
=====Contact Information:=====
 
Please join #fedora-admin in irc.freenode.net or respond to this email to
track the status of this outage."


<references/>
<references/>
Line 65: Line 103:
<references/>
<references/>


====Beta change freeze====
====poppler soname bump in rawhide====
 
[[User:Ausil|Dennis Gilmore]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000773.html</ref>,
 
"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"
 
<references/>
 
====Fedora 15 schedule to slip an additional week====
 
Jared K. Smith announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000772.html</ref>
 
"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:
 
<code>
  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
</code>


Robyn Bergeron has also kindly updated the complete break-out of the Fedora release schedule, which is available<ref>http://rbergero.fedorapeople.org/schedules/f-15/</ref>.  If you have any questions or concerns, please don't hesitate to let me know.
Marek Kasik<ref>Marek Kasik mkasik at redhat.com</ref> on Fri Apr 1 16:13:45 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-April/000774.html</ref>,


--
"I plan to rebase poppler in rawhide to poppler-0.17.0.
Jared Smith
There are several API changes and 2 soname bumps (libpoppler.so.13 to
Fedora Project Leader
libpoppler.so.14 and libpoppler-glib.so.6 to libpoppler-glib.so.8).
"
You can test it against your package with this scratch-build:
<ref>http://koji.fedoraproject.org/koji/taskinfo?taskID=2966806</ref>
I'll do chain-build of poppler and packages requiring it next Friday
(8th of April)."  


<references/>
<references/>

Revision as of 04:28, 7 April 2011

Announcements

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

Contributing Writer: Rashadul Islam

Fedora Announcement News

The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1]

Vote for your favorite Fedora 16 release name

Jared K. Smith[1] on Mon Apr 4 14:04:41 UTC 2011 announced[2] the Vote for your favorite Fedora 16 release name. The details of the announcement are as follows.

"The time has come to vote for the release name for Fedora 16. The Fedora community has submitted quite a few suggestions for the Fedora 16 release name, and that list has been narrowed down to the final nine candidates. Now you can vote on these names and assist in the final selection for the successor of Fedora 15 "Lovelock".

This vote begins 5 April 2011 and runs until 11 April 2011 at 23:59:59 UTC. Other important facts:

  • We are using the Range Voting method

([3])

  • Ballots may be cast on the Fedora Elections System at

[4]

  • If this is the first time you've used the voting system, you might

want to read the Fedora Elections Guide, currently located at [5]

  • To vote, you must have a valid Fedora Contributors License Agreement

(CLA) and be a member of at least one non-CLA group

To vote, visit: [6]

Thank you to everyone who helped by contributing names for consideration, and reviewing the names for the final ballot."

Outage: hosted servers 2011-04-12 04:00 UTC

Stephen John Smoogen[1] on Wed Apr 6 17:16:42 UTC 2011 announced[2],

"There will be an outage starting at 2011-04-12 04:00 UTC, which will last approximately 6 hours.

To convert UTC to your local time, take a look at [3]

or run: date -d ' 2011-04-12 04:00 UTC'

Reason for outage:

Serverbeach (our service provider for our hosted and other servers) are upgrading switches in their San Antonio (SAT) Datacenter. The outage for our systems are supposed to be 15 minutes but can be anywhere within that 6 hours.

Affected Services:

Email system Fedora Hosted - [4] Fedora People - [5]

Unaffected Services:

Most services should stay up, however various items depending on fedorahosted will be affected (which may then affect other services, etc etc.)

Contact Information:

Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."

Fedora Development News

The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above

poppler soname bump in rawhide

Marek Kasik[1] on Fri Apr 1 16:13:45 UTC 2011 announced[2],

"I plan to rebase poppler in rawhide to poppler-0.17.0. There are several API changes and 2 soname bumps (libpoppler.so.13 to libpoppler.so.14 and libpoppler-glib.so.6 to libpoppler-glib.so.8). You can test it against your package with this scratch-build: [3] I'll do chain-build of poppler and packages requiring it next Friday (8th of April)."

Fedora Events

The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and 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 - May 2011)

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

Past Events

Archive of Past Fedora Events[1]

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.