From Fedora Project Wiki

< FWN‎ | Beats

(updating the beat)
No edit summary
Line 37: Line 37:
====New bodhi release in production====   
====New bodhi release in production====   
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>,
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>,
"A new version of bodhi has just hit production.  This release contains a number of bugfixes and improvements, along with some important process changes.
      <ref>https://admin.fedoraproject.org/updates</ref>
=====ChangeLog=====
* Package update acceptance criteria compliance <ref>https://fedoraproject.org/wiki/Package_update_acceptance_criteria</ref>
      - Disable direct-to-stable pushes(<ref>https://fedorahosted.org/bodhi/ticket/434</ref>)
      - Minimum time-in-testing requirements
          - Every day bodhi will look for updates that have been in testing for N days (fedora: N=7, epel: N=14), and will add a comment notifying the maintainer that the update is now able to be pushed to stable.
          - When someone tries to push an update to stable, bodhi will look to see if it has the appropriate karma, or if it has been in testing for more than N days.
* Critical path update changes
  - Hide obsolete updates in our critpath view(<ref>https://fedorahosted.org/bodhi/ticket/447</ref>)
  - Disabled strict critical path procedures for EPEL
      - EPEL is back to the same process that it has always had
  - Add a new nagmail message for unapproved critical path updates
* RSS feed & grid of unapproved critical path updates
* <ref>https://admin.fedoraproject.org/updates/rss/rss2.0?critpath=True&release=F13</ref>
* <ref>https://admin.fedoraproject.org/updates/critpath?unapproved=True&release=F13</ref>
* RSS feed & grid of user-specific comments(<ref>https://fedorahosted.org/bodhi/ticket/445</ref>)
    <ref>https://admin.fedoraproject.org/updates/comments?user=lmacken</ref>
* <ref>https://admin.fedoraproject.org/updates/rss/rss2.0?comments=True&user=lmacken</ref>
* Package-specific RSS feeds of updates(<ref>https://fedorahosted.org/bodhi/ticket/339</ref>)
    <ref>https://admin.fedoraproject.org/updates/rss/rss2.0?package=kernel</ref>
* Add more links to the package-specific page
      <ref>https://admin.fedoraproject.org/updates/TurboGears2</ref>
* Show 7 days worth of entries in our RSS feeds, as opposed to 20 entries (<ref>https://fedorahosted.org/bodhi/ticket/339</ref>)
* Bodhi command-line client fixes
  - Output now goes to stdout, instead of stderr (<ref>https://fedorahosted.org/bodhi/ticket/449</ref>)
    (Thanks to Till Maas)
  - Duplicate logging issue resolved(<ref>https://bugzilla.redhat.com/show_bug.cgi?id=613533</ref>)
  - Support using --critpath and --type with --testable
* Link to the submitter and release on the home page & testing list (Thanks to Till Maas)
* Made the suggest_reboot flag actually configurable
    (<ref>https://fedorahosted.org/bodhi/ticket/352</ref>)
* Notify the security team when an update is edited and turned into a security update (<ref>https://fedorahosted.org/bodhi/ticket/403</ref>)
* Only verify the autokarma thresholds if it is enabled (Thanks to Till Maas)
* Only touch bugs under the Fedora/EPEL Bugzilla products
    (<ref>https://fedorahosted.org/bodhi/ticket/448</ref>)
* Prevent the masher from pushing obsolete updates
* Prevent obsolete updates from getting auto-promoted to stable
* Obsolete updates upon deletion, as opposed to destroying them.
* Added more unit tests (up to 122)
* Link up bug numbers and other URLs in the text of comments
* Document the `newpackage` update type in the bodhi-client commands
  (<ref>https://bugzilla.redhat.com/show_bug.cgi?id=621828</ref>)
* Set bugs to MODIFIED upon submission
  (<ref>https://fedorahosted.org/bodhi/ticket/343</ref>)
* Added a `bodhi --push-request={stable,testing}` command to improve our releng updates push workflow
* A new /updates/releases JSON API and python-fedora BodhiClient.get_releases() method for AutoQA
* Have the build auto-completion widget query candidate builds from koji, as opposed to looking in /mnt/koji/packages
    (<ref>https://fedorahosted.org/bodhi/ticket/173</ref>)
=====Bugs & RFEs=====
Please file and bug reports or enhancement requests here:<ref>https://fedorahosted.org/bodhi/newticket</ref>"


<references/>
<references/>
Line 42: Line 107:
====Outage: PHX2 network outage - 2010-08-15 01:00 UTC====   
====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>,
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>,
"'''There will be an outage starting at 2010-08-15 01:00 UTC, which will last approximately 4 hours.'''
To convert UTC to your local time, take a look at <ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
or run:
date -d '2010-08-15 01:00 UTC'
=====Reason for outage=====
Network work is being done in our primary hosting facility.  Some services may be offline during this time.  It is possible nothing will go offline.
=====Affected Services=====
* Bodhi - <ref>https://admin.fedoraproject.org/updates/</ref>
* Buildsystem - <ref>http://koji.fedoraproject.org/</ref>
* CVS / Source Control
* Email system
* Fedora Account System - <ref>https://admin.fedoraproject.org/accounts/</ref>
* Fedora Community - <ref>https://admin.fedoraproject.org/community/</ref>
* Fedora Hosted - <ref>https://fedorahosted.org/</ref>
* Fedora People - <ref>http://fedorapeople.org/</ref>
* Fedora Talk - <ref>http://talk.fedoraproject.org/</ref>
* Mirror Manager - <ref>https://admin.fedoraproject.org/mirrormanager/</ref>
* Package Database - <ref>https://admin.fedoraproject.org/pkgdb/</ref>
* Smolt - <ref>http://smolts.org/</ref>
* Translation Services - <ref>http://translate.fedoraproject.org/</ref>
* Wiki - <ref>http://fedoraproject.org/wiki/</ref>
=====Unaffected Services=====
* BFO - <ref>http://boot.fedoraproject.org/</ref>
* DNS - ns1.fedoraproject.org, ns2.fedoraproject.org</ref>
* Docs - <ref>http://docs.fedoraproject.org/</ref>
* Main Website - <ref>http://fedoraproject.org/</ref>
* Mirror List - <ref>https://mirrors.fedoraproject.org/</ref>
* Spins - <ref>http://spins.fedoraproject.org/</ref>
* Start - <ref>http://start.fedoraproject.org/</ref>
* Torrent - <ref>http://torrent.fedoraproject.org/</ref>
=====Ticket Link=====
The link is at<ref>https://fedorahosted.org/fedora-infrastructure/ticket/2335</ref>
=====Contact Information=====
Please join '''#fedora-admin in irc.freenode.net''' or respond to this email<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000661.html</ref> to track the status of this outage."


<references/>
<references/>

Revision as of 12:51, 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

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

Fedora Announcement News

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

  1. ↑ http://lists.fedoraproject.org/pipermail/announce/2010-August/thread.html

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],

  1. ↑ Nils Philippsen nils at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000658.html

Want to help pick the F14 Release Slogan?

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

  1. ↑ Bergeron robyn.bergeron at gmail.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000659.html

One week slip of Fedora 14 schedule

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

  1. ↑ Jared K. Smith jsmith at fedoraproject.org
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000656.html

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],

  1. ↑ Adam Williamson awilliam at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000657.html

New bodhi release in production

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

"A new version of bodhi has just hit production. This release contains a number of bugfixes and improvements, along with some important process changes. 

     [3]
ChangeLog
  • Package update acceptance criteria compliance [4]
      - Disable direct-to-stable pushes([5])

      - Minimum time-in-testing requirements

          - Every day bodhi will look for updates that have been in testing for N days (fedora: N=7, epel: N=14), and will add a comment notifying the maintainer that the update is now able to be pushed to stable.

          - When someone tries to push an update to stable, bodhi will look to see if it has the appropriate karma, or if it has been in testing for more than N days.
  • Critical path update changes
  - Hide obsolete updates in our critpath view([6])

  - Disabled strict critical path procedures for EPEL
      - EPEL is back to the same process that it has always had

  - Add a new nagmail message for unapproved critical path updates
  • RSS feed & grid of unapproved critical path updates
  • [7]
  • [8]
  • RSS feed & grid of user-specific comments([9])
    [10]
  • [11]
  • Package-specific RSS feeds of updates([12])
    [13]
  • Add more links to the package-specific page
      [14]
  • Show 7 days worth of entries in our RSS feeds, as opposed to 20 entries ([15])
  • Bodhi command-line client fixes
  - Output now goes to stdout, instead of stderr ([16])
    (Thanks to Till Maas)

  - Duplicate logging issue resolved([17])

  - Support using --critpath and --type with --testable
  • Link to the submitter and release on the home page & testing list (Thanks to Till Maas)
  • Made the suggest_reboot flag actually configurable
   ([18])
  • Notify the security team when an update is edited and turned into a security update ([19])
  • Only verify the autokarma thresholds if it is enabled (Thanks to Till Maas)
  • Only touch bugs under the Fedora/EPEL Bugzilla products
   ([20])
  • Prevent the masher from pushing obsolete updates
  • Prevent obsolete updates from getting auto-promoted to stable
  • Obsolete updates upon deletion, as opposed to destroying them.
  • Added more unit tests (up to 122)
  • Link up bug numbers and other URLs in the text of comments
  • Document the newpackage update type in the bodhi-client commands
  ([21])
  • Set bugs to MODIFIED upon submission
  ([22])
  • Added a bodhi --push-request={stable,testing} command to improve our releng updates push workflow
  • A new /updates/releases JSON API and python-fedora BodhiClient.get_releases() method for AutoQA
  • Have the build auto-completion widget query candidate builds from koji, as opposed to looking in /mnt/koji/packages
   ([23])
Bugs & RFEs

Please file and bug reports or enhancement requests here:[24]"

  1. ↑ Luke Macken lmacken at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000660.html
  3. ↑ https://admin.fedoraproject.org/updates
  4. ↑ https://fedoraproject.org/wiki/Package_update_acceptance_criteria
  5. ↑ https://fedorahosted.org/bodhi/ticket/434
  6. ↑ https://fedorahosted.org/bodhi/ticket/447
  7. ↑ https://admin.fedoraproject.org/updates/rss/rss2.0?critpath=True&release=F13
  8. ↑ https://admin.fedoraproject.org/updates/critpath?unapproved=True&release=F13
  9. ↑ https://fedorahosted.org/bodhi/ticket/445
  10. ↑ https://admin.fedoraproject.org/updates/comments?user=lmacken
  11. ↑ https://admin.fedoraproject.org/updates/rss/rss2.0?comments=True&user=lmacken
  12. ↑ https://fedorahosted.org/bodhi/ticket/339
  13. ↑ https://admin.fedoraproject.org/updates/rss/rss2.0?package=kernel
  14. ↑ https://admin.fedoraproject.org/updates/TurboGears2
  15. ↑ https://fedorahosted.org/bodhi/ticket/339
  16. ↑ https://fedorahosted.org/bodhi/ticket/449
  17. ↑ https://bugzilla.redhat.com/show_bug.cgi?id=613533
  18. ↑ https://fedorahosted.org/bodhi/ticket/352
  19. ↑ https://fedorahosted.org/bodhi/ticket/403
  20. ↑ https://fedorahosted.org/bodhi/ticket/448
  21. ↑ https://bugzilla.redhat.com/show_bug.cgi?id=621828
  22. ↑ https://fedorahosted.org/bodhi/ticket/343
  23. ↑ https://fedorahosted.org/bodhi/ticket/173
  24. ↑ https://fedorahosted.org/bodhi/newticket

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

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

"There will be an outage starting at 2010-08-15 01:00 UTC, which will last approximately 4 hours.

To convert UTC to your local time, take a look at [3] or run: date -d '2010-08-15 01:00 UTC'

Reason for outage

Network work is being done in our primary hosting facility. Some services may be offline during this time. It is possible nothing will go offline.

Affected Services
  • Bodhi - [4]
  • Buildsystem - [5]
  • CVS / Source Control
  • Email system
  • Fedora Account System - [6]
  • Fedora Community - [7]
  • Fedora Hosted - [8]
  • Fedora People - [9]
  • Fedora Talk - [10]
  • Mirror Manager - [11]
  • Package Database - [12]
  • Smolt - [13]
  • Translation Services - [14]
  • Wiki - [15]
Unaffected Services
  • BFO - [16]
  • DNS - ns1.fedoraproject.org, ns2.fedoraproject.org</ref>
  • Docs - [17]
  • Main Website - [18]
  • Mirror List - [19]
  • Spins - [20]
  • Start - [21]
  • Torrent - [22]
Ticket Link

The link is at[23]

Contact Information

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

  1. ↑ Mike McGrath mmcgrath at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000661.html
  3. ↑ http://fedoraproject.org/wiki/Infrastructure/UTCHowto
  4. ↑ https://admin.fedoraproject.org/updates/
  5. ↑ http://koji.fedoraproject.org/
  6. ↑ https://admin.fedoraproject.org/accounts/
  7. ↑ https://admin.fedoraproject.org/community/
  8. ↑ https://fedorahosted.org/
  9. ↑ http://fedorapeople.org/
  10. ↑ http://talk.fedoraproject.org/
  11. ↑ https://admin.fedoraproject.org/mirrormanager/
  12. ↑ https://admin.fedoraproject.org/pkgdb/
  13. ↑ http://smolts.org/
  14. ↑ http://translate.fedoraproject.org/
  15. ↑ http://fedoraproject.org/wiki/
  16. ↑ http://boot.fedoraproject.org/
  17. ↑ http://docs.fedoraproject.org/
  18. ↑ http://fedoraproject.org/
  19. ↑ https://mirrors.fedoraproject.org/
  20. ↑ http://spins.fedoraproject.org/
  21. ↑ http://start.fedoraproject.org/
  22. ↑ http://torrent.fedoraproject.org/
  23. ↑ https://fedorahosted.org/fedora-infrastructure/ticket/2335
  24. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000661.html

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

  1. ↑ John Poelstra poelstra at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2010-August/000662.html
  3. ↑ https://fedoraproject.org/wiki/Go_No_Go_Meeting
  4. ↑ https://bugzilla.redhat.com/showdependencytree.cgi?id=611990&hide_resolved=1

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