From Fedora Project Wiki

< FWN‎ | Beats

mNo edit summary
(updating the beat)
Line 15: Line 15:


===Fedora Development News===
===Fedora Development News===
====Fedora 14 Alpha Go/No-Go Meeting August 12, 2010 @ 12:00 AM UTC====   
====155 more python packages need to be rebuilt for Python 2.7====   
[[User:Poelstra|John Poelstra]]<ref>John Poelstra</ref> on Tue Aug 10 19:51:28 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000654.html</ref>,
Nils Philippsen<ref>Nils Philippsen nils at redhat.com</ref> on Wed Aug 11 19:26:56 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000658.html</ref>,


"Join us on irc.freenode.net '''#fedora-meeting''' for this important meeting.
<references/>


'''Thursday, August 12, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT,Wednesday, August 11, 2010* )'''
====Want to help pick the F14 Release Slogan?==== 
Robyn Bergeron Robyn<ref>Bergeron robyn.bergeron at gmail.com</ref> on Wed Aug 11 20:40:12 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000659.html</ref>,


"Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: Go/No-Go Meeting."
<references/>


"Verifying that the Release criteria are met is the responsibility of the QA Team."
====One week slip of Fedora 14 schedule==== 
Jared K. Smith<ref>Jared K. Smith jsmith at fedoraproject.org</ref> on Thu Aug 12 01:57:40 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000656.html</ref>


For more details about this meeting see: <ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
<references/>
 
In the meantime keep an eye on the Fedora 14 Alpha Blocker list and help us test!


<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1</ref>
====Fedora 14 Alpha Go/No-Go Meeting: 2010-08-12 @ 12:00 UTC Recap==== 
<ref>http://fedoraproject.org/wiki/Category:Fedora_14_Alpha_RC_Test_Results"</ref>
Adam Williamson<ref>Adam Williamson awilliam at redhat.com</ref> on Thu Aug 12 02:10:41 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000657.html</ref>,


<references/>
<references/>


====Reminder: Bugzilla UPGRADE to 3.6 on August 13th 9:00 p.m.EDT [01:00 UTC]====  
====New bodhi release in production====  
[[User:Poelstra|John Poelstra]]<ref>John Poelstra</ref> on Wed Aug 11 15:33:08 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000655.html</ref>,
Luke Macken<ref>Luke Macken lmacken at redhat.com</ref> on Thu Aug 12 21:57:28 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000660.html</ref>,


"Sending on behalf of '''Dave Lawrence'''<ref>Dave Lawrence</ref>.  This will affect Fedora too.
<references/>


REMINDER: Red Hat Bugzilla (bugzilla.redhat.com) will be unavailable on August 13th starting at 9:00 p.m. EDT [01:00 UTC] to perform an upgrade from Bugzilla 3.4 to Bugzilla 3.6. We are hoping to be complete in no more than 5 hours barring any problems. Any services relying on bugzilla.redhat.com may not work properly during this time. Please be aware in case you need use of those services during the outage.
====Outage: PHX2 network outage - 2010-08-15 01:00 UTC==== 
Mike McGrath<ref>Mike McGrath mmcgrath at redhat.com</ref> on Fri Aug 13 00:12:20 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000661.html</ref>,


Also *PLEASE* make sure any scripts or other external applications that rely on bugzilla.redhat.com are tested against our test server before the upgrade if you have not done so already (see original email below). Let the Bugzilla Team know immediately of any issues found by reporting the bug in bugzilla.redhat.com against the Bugzilla product, version 3.6.
<references/>
 
-------------------------------------------


Greetings,
====Fedora 14 Alpha Go/No-Go Meeting August 19, 2010 @ 12:00 AM UTC==== 
John Poelstra<ref>John Poelstra poelstra at redhat.com</ref> on Tue Aug 17 23:59:56 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000662.html</ref>,


The Red Hat Bugzilla team is happy to announce another public beta release of the next version of Red Hat Bugzilla based on the upstream 3.6 code base.
=====Where=====
"Join us on irc.freenode.net #fedora-meeting for this important meeting.


Please test drive at: <ref>https://partner-bugzilla.redhat.com</ref>
=====When=====
Thursday, August 19, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT--Wednesday, August 18, 2010* )


Over the years Red Hat has made substantial customizations to Bugzilla to fit into the Engineering tool chain. Over time the upstream has incorporated some of these customizations or solved them in different ways. Upgrading reduces our customization footprint (and thus maintenance) while bringing many bug fixes & enhancements.
=====Details=====
"Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular
release. This meeting is called the: '''Go/No-Go Meeting'''."


The main area of focus for our public betas is stability. Functionality that currently works in our 3.4 code base should continue to work as expected in the new 3.6 release. These include various ajax optimizations, needinfo actor support, frontpage.cgi, product browser, several various UI enhancements, and of course the XMLRPC API.
"'''Verifying that the Release criteria are met is the responsibility of the QA Team.'''"
 
Please feel free to point your various scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly.
 
There are numerous other changes behind the scenes that we haven't listed. The goal is to make sure that functionality that people have come to expect in 3.4 is possible in the new system.
 
There are also numerous new features/fixes that are part of the upstream 3.6 release. For more detailed information on what has changed since the last release, check out the release notes page at<ref>https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html</ref> .
 
The database is a recent snapshot of the live database so should be useful for testing to make sure the information is displayed properly and changeable. Also with a full snapshot it is possible to test for any performance related issues. Email has been disabled so that unnecessary spam is not sent out. So feel free to make changes to bugs to verify proper working order.
 
We are asking for everyone to get involved as much as possible with testing and feedback on the beta releases to help us make this the most robust and stable release possible.
 
Please file any enhancement requests or bug reports in our current Bugzilla system at <ref>https://bugzilla.redhat.com</ref>. File them under the Bugzilla product and relevant component with the version 3.6. With everyone's help we can make this a great release."
 
<references/>


===Fedora Events===
For more details about this meeting see:<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
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 (June 2010 - August 2010)====
=====Fedora 14 Alpha Blocker list=====
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29</ref>
In the meantime keep an eye on the Fedora 14 Alpha Blocker list (which is currently EMPTY!)
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2</ref>
<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1</ref>"
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4</ref>


<references/>
<references/>

Revision as of 12:33, 19 August 2010

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]

Fedora Development News

155 more python packages need to be rebuilt for Python 2.7

Nils Philippsen[1] on Wed Aug 11 19:26:56 UTC 2010 announced[2],

Want to help pick the F14 Release Slogan?

Robyn Bergeron Robyn[1] on Wed Aug 11 20:40:12 UTC 2010 announced[2],

One week slip of Fedora 14 schedule

Jared K. Smith[1] on Thu Aug 12 01:57:40 UTC 2010 announced[2]

Fedora 14 Alpha Go/No-Go Meeting: 2010-08-12 @ 12:00 UTC Recap

Adam Williamson[1] on Thu Aug 12 02:10:41 UTC 2010 announced[2],

New bodhi release in production

Luke Macken[1] on Thu Aug 12 21:57:28 UTC 2010 announced[2],

Outage: PHX2 network outage - 2010-08-15 01:00 UTC

Mike McGrath[1] on Fri Aug 13 00:12:20 UTC 2010 announced[2],

Fedora 14 Alpha Go/No-Go Meeting August 19, 2010 @ 12:00 AM UTC

John Poelstra[1] on Tue Aug 17 23:59:56 UTC 2010 announced[2],

Where

"Join us on irc.freenode.net #fedora-meeting for this important meeting.

When

Thursday, August 19, 2010, @ 12:00 AM UTC ( *20:00 EDT/17:00 PDT--Wednesday, August 18, 2010* )

Details

"Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of the QA Team."

For more details about this meeting see:[3]

Fedora 14 Alpha Blocker list

In the meantime keep an eye on the Fedora 14 Alpha Blocker list (which is currently EMPTY!) [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.