From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 65: Line 65:
<references/>
<references/>


====Your package translation====
====Beta change freeze====


Noriko<ref>noriko at fedoraproject.org</ref> on Mon Mar 21 23:57:43 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000769.html</ref>,
[[User:Ausil|Dennis Gilmore]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000773.html</ref>,


"Dear Fedora package maintainers
"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.


Could you all please take a few minutes and check if your packages are
thanks
on the list<ref>http://www.transifex.net/projects/p/fedora/r/fedora-15/l/en/</ref>and set to allow Fedora Localization Project to translate?


* setuptool: <ref>http://www.transifex.net/projects/p/setuptool/</ref>
Dennis"
* pam_krb5: <ref>http://www.transifex.net/projects/p/pam_krb5/</ref>
* pkinit-nss: <ref>http://www.transifex.net/projects/p/pkinit-nss/</ref>


* The above packages are on the list but do not allow Fedora Localization teams to upload the translated files. This means that these
<references/>
packages will not receive any translation from FLP. Please change the  
 
setting to allow FLP, or advise us if the maintainers choose having
====Fedora 15 schedule to slip an additional week====
their own translation teams. In that case, the packages may be removed
 
from the list of Fedora Project on tx.net."
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.
 
--
Jared Smith
Fedora Project Leader
"


<references/>
<references/>

Revision as of 18:19, 30 March 2011

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

Fedora Announcement News

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

Changes to the Packaging Guidelines

Tom 'Spot' Callaway announced[1],

"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 [2]

Thanks,

~spot"

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

Beta change freeze

Dennis Gilmore announced[1],

"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"

Fedora 15 schedule to slip an additional week

Jared K. Smith announced[1]

"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[2]. If you have any questions or concerns, please don't hesitate to let me know.

-- Jared Smith Fedora Project Leader "

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 (Dec 2010 - Feb 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.