No edit summary |
No edit summary |
||
| Line 131: | Line 131: | ||
Questions | Questions | ||
1) Why tag all Update requests into f12-final? | 1) Why tag all Update requests into f12-final? | ||
At this point of the schedule we realized that there were updates sitting in the queue from since October. They were sitting there. Not getting pushed to any repository. Rawhide gives these packages several more weeks of testing exposure. This was decided to be better than a flood of day zero updates that are poorly tested. | At this point of the schedule we realized that there were updates sitting in the queue from since October. They were sitting there. Not getting pushed to any repository. Rawhide gives these packages several more weeks of testing exposure. This was decided to be better than a flood of day zero updates that are poorly tested. | ||
Revision as of 15:31, 9 November 2009
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 ANNOUNCE LIST
CC license changeover complete
Ian Weller announced about the CC license changeover complete [1]. He mentioned, “The Docs team has finished converting all current documentation and project content from the OPL to a CC BY-SA 3.0 Unported license.
Additional information can be found at [2]</ref>http://www.redhat.com/archives/fedora-announce-list/2009-October/msg00001.html</ref>
Thanks again to Tom "spot" Callaway, Richard Fontana of Red Hat Legal and all the Fedora contributors who helped with the conversion. Here's to freer documentation for Fedora 12!”
Reminder: Fedora Board IRC meeting 1700 UTC 2009-11-05
Paul W. Frields, the Fedora Project Leader, announced [1] as reminder about the Fedora Board IRC Meeting. He said, “The Board is holding its monthly public meeting on Thursday, November 5, 2009, at 1700 UTC on IRC Freenode. For this meeting, the public is invited to do the following:
Join #fedora-board-meeting to see the Board's conversation. Join #fedora-board-questions to discuss topics and post questions. This channel is read/write for everyone.”
Note that daylight savings time ends in the USA on November 1, and on November 5, 1700 UTC == 12:00pm US Eastern == 9:00am US Pacific.
Announcing Fedora-Medical SIG.
Susmit shannigrahi had announced Fedora-Medical SIG[1]. On his announcement, he mentioned how the idea came from (Fedora India mailing list [2]), how to make the Fedora Medical SIG successful, the initial SIG page [3] and the goal of the SIG. He said, “Simply put, the goal of the SIG is going to be:
1. Working on identifying the various workflows / needs of the medical or healthcare community in terms of software. 2. Bring together and package the software those fitting in the workflow. 3. Composing a spin to get a out-of-the-box solution. 4. At a later stage, developing any crucial app that may be lacking. ”
Fedora 12 now in RC freeze
Bill Nottingham announced on behalf of the Fedora Release Engineering, “Fedora 12 now in RC freeze” [1]. He said, “We are reaching a very deep freeze now as we try and get a final release candidate for Fedora 12. Bodhi is now open for submitting F-12 updates, and we hope to have update repositories for testing later this weekend. If you have critical blocking issues, you can continue to file tag requests with 'make tag-request', and they will be considered. For the majority of updates, though, please use bodhi.”
</references>
FEDORA DEVELOPMENT ANNOUNCEMENTS
Outage Notification - 2009-11-05 13:00 UTC
“There will be an outage starting at 2009-11-05 13:00 UTC, which will last approximately 1 hour.”, announced[2] Mike McGrath. He widely mentioned, “ To convert UTC to your local time, take a look at [3] or run:
date -d '2009-11-05 13:00 UTC'
Affected Services: Buildsystem DNS Torrent Translation Services Websites
Unaffected Services: CVS / Source Control Database Fedora Hosted Fedora People Fedora Talk Mail Mirror System
Ticket Link:[4]
Reason for Outage: IBM wants us reseat the DIMMs and get FRU information off of them. Don is going to do this work for us (thanks ibiblio). Seth is going to do a graceful shutoff.
Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to trackthe status of this outage.”
Addition to the Policy for non responsive maintainers
Kevin announced, “FESCo has made an additional 'fast track' process for non responsive maintainers available for some rare cases.”[1]
[2] For more details. [3] As well as: [4]
- ↑ http://www.redhat.com/archives/fedora-devel-announce/2009-October/msg00010.html
- ↑ https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers#Fast_Track_procedure
- ↑ https://fedorahosted.org/fesco/ticket/251
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2009-09-18/fedora-meeting.2009-09-18-16.59.log.html#l-31
Upcoming Bugzilla Changes
Edward Kirk on behalf of the Fedora Bug Triage Team mentioned the upcoming Bugzilla Changes [1].
He said, “This e-mail is designed to let you know about two things happening around November 17, 2009 (Fedora 12 release day) and what you need to do, if anything.
(1) We will be automatically changing the version all rawhide bugs to Fedora 12.This will result in regular bugs reported against rawhide during the Fedora 12 development cycle being changed to version '12' instead of their current assignment, 'rawhide'. This is done in order to more accurately tell where in the lineage of releases the bug was last reported because over time 'rawhide'becomes ambiguous.
Note that this procedure does not apply to bugs that are against component 'Package Review' or bugs that have the 'FutureFeature' or 'Tracking' keywords set. They will stay open as rawhide bugs indefinitely.
If you do not want your bugs changed to version '12', add the FutureFeature keyword. If you need help changing a large amount of bugs manually, we'd be glad to help. Stop by #fedora-bugzappers on irc.freenode.net and we'll help you.
(2) All bugs for upcoming EOL releases (at this point, Fedora 10) will get a comment on release day, explaining that one month of maintenance remains. These bugs must move to a later version if still applicable or they will be automatically closed in one month with a resolution of WONTFIX.”
More about these processes is here:[2]
Request your FUDCon funding now: cutoff Thursday 19:30 UTC
Mel Chua announced, [1] “Request your FUDCon funding now: cutoff Thursday 19:30 UTC”.
Here is the brief, “We’d like to wrap up budgeting for FUDCon Toronto 2009 as the happy date draws nearer. And we need your help. Ask us for money! Before Thursday October 29 at 19:30 UTC, that is. More details here (the blog post below will lead you to instructions on the wiki outlining how to request funding):[2] I look forward to a flooded inbox on Thursday afternoon. ;)”
Notice: Fedora 12 Tagging Status Update
Warren Togami announced [1] that Fedora Release Engineering had decided to deal with the 250+ backlog of Bodhi update requests by tagging them all into f12-final. Bodhi is now disabled for Fedora 12 updates. He said, “
Questions 1) Why tag all Update requests into f12-final? At this point of the schedule we realized that there were updates sitting in the queue from since October. They were sitting there. Not getting pushed to any repository. Rawhide gives these packages several more weeks of testing exposure. This was decided to be better than a flood of day zero updates that are poorly tested.
2) When will we be able to submit Updates again? Rel-eng will decide when to begin accepting Updates for Fedora 12 again during Monday's rel-eng meeting. Meanwhile please use the rel-eng ticketing system to request tagging into f12-final.
3) How do I file a tag request to include my package into Fedora 12? [2] Please file tag request tickets here if you want your package build to be included in Fedora 12. Please include details like:
- Full Name-Version-Release of your package(s)
- What changed?
- How risky is this change?
- How important is this change?
- How well tested is this package build?
- Is this package in the critical-path list?
4) Which packages are critical-path? [3] Unfortunately we do not yet have a permanent URL with the critical-path list. This page contains an auto-generated list of critical-path packages as of today. If your package is not critical-path and not a risk to others to update, then it is highly likely proper to tag at this point of the schedule.
5) How many untagged packages are there? koji list-tagged --latest dist-f12-updates-candidate This command lists all packages that are not tagged for f12-final. In some cases these are false positives because a newer package is instead tagged into f12-final. After you have tested your package and verified it doesn't make things worse, please file rel-eng tickets to have it included. Please direct questions to fedora-devel-list. “
Reminder: Tagging Policy for Fedora 12
Warren announced the Tagging Policy for Fedora 12[1]. He also detailed about the following on the announcement: What Qualifies for Tagging? Many Builds Not Tagged, but Probably Should Be How to Request Tagging [2] Upcoming Deadlines [3]
FEDORA EVENTS
Fedora events are the 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
- North America (NA)[1]
- Central & South America (LATAM) [2]
- Europe, Middle East, and Africa (EMEA)[3]
- India, Asia, Australia (India/APJ)[4]
- ↑ http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29
- ↑ http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_2
- ↑ http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_3
- ↑ http://fedoraproject.org/wiki/Events#FY10_Q3_.28September_2009_-_November_2009.29_4
Past Events
Archive of Past Fedora Events[1]