From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 77: Line 77:


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:<ref>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
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:<ref>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
<references/>
====Fedora 13 Alpha Go/No-Go Meeting====
=====Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 at 19:00 UTC (14:00 EST)===== 
[[User:Adamwill|Adam Williamson]] announced as an important note<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "...we are rescheduling the Go/No-Go meeting for Fedora 13 Alpha. Previously scheduled for 2010-02-25 01:00 UTC, it is now scheduled for 2010-02-25 19:00 UTC (14:00 EST, 11:00 PST). This delay is to give sufficient time for the QA team to test the expected RC3 build.
The original announcement, with the new time, is reproduced below for reference.
Join us on irc.freenode.net #fedora-meeting for this important meeting.
Thursday, February 25, 2010 @ 19:00 UTC (14:00 EST).
"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 important meeting see: <ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"
<references/>
=====Feodra 13 Alpha slip by one week=====
[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000581.html</ref> on the basis of the announcement<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "Today at the go / no-go meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-02-25/fedora-meeting.2010-02-25-18.59.log.html</ref> we decided to slip the Alpha by one week.  This slip is needed to verify blocker bug fixes and validate new builds of software necessary to fix those bugs.  We are confident that the fixes we have are valid, however we do not have enough time to prove them valid.  We will spend the next few days doing that validation.  In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be pushed unless they are fixing a release blocking issue.  Once we've validated all the fixes we will do more frequent pushes to 13 stable.
At this time we are not adjusting later milestone dates, as with no frozen rawhide we are not taking away any developer time." 
<references/>
=====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC (2010-03-03 @ 20:00 EST)===== 
[[User:Adamwill|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000582.html</ref>, "Join us on irc.freenode.net #fedora-meeting for this important meeting. This is Thursday, March 4, 2010 @ 01:00 UTC, which makes it '''WEDNESDAY EVENING''' in North America: 20:00 EST, 17:00 PST.
"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 important meeting see:<ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"


<references/>
<references/>
Line 186: Line 150:
<references/>
<references/>


====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC Recap====
====Fedora 13 Alpha Go/No-Go Meeting====
=====Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 at 19:00 UTC (14:00 EST)===== 
[[User:Adamwill|Adam Williamson]] announced as an important note<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "...we are rescheduling the Go/No-Go meeting for Fedora 13 Alpha. Previously scheduled for 2010-02-25 01:00 UTC, it is now scheduled for 2010-02-25 19:00 UTC (14:00 EST, 11:00 PST). This delay is to give sufficient time for the QA team to test the expected RC3 build.
 
The original announcement, with the new time, is reproduced below for reference.
 
Join us on irc.freenode.net #fedora-meeting for this important meeting.
Thursday, February 25, 2010 @ 19:00 UTC (14:00 EST).
 
"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 important meeting see: <ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"
 
<references/>
 
=====Feodra 13 Alpha slip by one week=====
[[User:Jkeating|Jesse Keating]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000581.html</ref> on the basis of the announcement<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-February/000580.html</ref>, "Today at the go / no-go meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-02-25/fedora-meeting.2010-02-25-18.59.log.html</ref> we decided to slip the Alpha by one week.  This slip is needed to verify blocker bug fixes and validate new builds of software necessary to fix those bugs.  We are confident that the fixes we have are valid, however we do not have enough time to prove them valid.  We will spend the next few days doing that validation.  In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be pushed unless they are fixing a release blocking issue.  Once we've validated all the fixes we will do more frequent pushes to 13 stable.
At this time we are not adjusting later milestone dates, as with no frozen rawhide we are not taking away any developer time." 
 
<references/>
 
=====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC (2010-03-03 @ 20:00 EST)===== 
[[User:Adamwill|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000582.html</ref>, "Join us on irc.freenode.net #fedora-meeting for this important meeting. This is Thursday, March 4, 2010 @ 01:00 UTC, which makes it '''WEDNESDAY EVENING''' in North America: 20:00 EST, 17:00 PST.
 
"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 important meeting see:<ref>https://fedoraproject.org/wiki/Engineering_Readiness_Meetings</ref>"
 
<references/>
 
=====Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC Recap=====
[[/User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000585.html</ref> the meeting summary, "Representatives from Fedora QA, Rel-Eng and Development met on IRC to review determine whether the Fedora 13 Alpha release criteria<ref>https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria</ref> have been met.  The team agreed that the Alpha criteria have been met, and to proceed with releasing F-13-Alpha-RC4.  For additional details, please refer to the attached minutes.
[[/User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000585.html</ref> the meeting summary, "Representatives from Fedora QA, Rel-Eng and Development met on IRC to review determine whether the Fedora 13 Alpha release criteria<ref>https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria</ref> have been met.  The team agreed that the Alpha criteria have been met, and to proceed with releasing F-13-Alpha-RC4.  For additional details, please refer to the attached minutes.


-------------- next part --------------
* '''fedora-meeting: F-13-Alpha engineering readiness meeting'''
=========================================================
 
#fedora-meeting: F-13-Alpha engineering readiness meeting
Meeting started by jlaska at 01:00:03 UTC. The full logs are available at <ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-03-04/f-13-alpha-eng-readiness.2010-03-04-01.00.log.html</ref>.
=========================================================
Meeting started by jlaska at 01:00:03 UTC. The full logs are available
at <ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-03-04/f-13-alpha-eng-readiness.2010-03-04-01.00.log.html</ref>.


'''Meeting summary'''
'''Meeting summary'''

Revision as of 21:42, 7 March 2010

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 Development News

[Guidelines Change] Changes to the Packaging Guidelines 04/09 - 02/10

Tom "spot" Callaway announced[1] the changes to the Packaging Guidelines 04/09 - 02/10. He said, "It has been almost a year since we announced changes to the Packaging Guidelines, so this will be a long list. In the future, we'll try to be more timely in writing up changes and announcing them to the Fedora Community.

Here are the list of changes to the Fedora Packaging Guidelines: When selecting which source to download from upstream and use in a Fedora package, the smallest available (and Fedora compatible) source should be used:[2]

The Fortran Packaging Guidelines have been updated: [3]

The Ant Sample Spec in the Java Packaging Guidelines has been corrected:[4]

The R Packaging Guidelines have been updated:[5]

The Scrollkeeper scriptlets were removed from the Packaging Guidelines:[6]

The Python Packaging Guidelines were significantly rewritten including changes to address:

  • Python 3
  • PyGTK2 and Numpy

[7]

Dos2unix is no longer forbidden when removing DOS line breaks in a file:[8]

The Packaging Guidelines now contain a lengthy explanation of why Bundled Libraries are not permitted in Fedora: [9]

The Packaging Guideline section on dealing with pre-built libraries has been improved:[10]

Fedora packages no longer need to explicitly define a BuildRoot, as RPM now always defines one:[11]

The Fedora Packaging Guidelines now contain more information on how to deal with Conflicting Files in scenarios involving "common names": [12]

There are now Packaging Guidelines for Wordpress Plugins:[13]

There are now Packaging Guidelines for Globus Toolkit components: [14]

Since RPM now detects pkgconfig dependencies in all Fedora releases, it is no longer necessary for Fedora packages with .pc files to explicitly Require: pkgconfig :[15]

Fedora packages should contain man pages for all included binaries and scripts, and if not present, Fedora packagers should work with upstream to add them: [16]

There are now Packaging Guidelines for MPI packages: [17]

There are now Packaging Guidelines for proper usage of Environment Modules: [18]

There are now Packaging Guidelines for proper usage of Alternatives: [19]

The Packaging Guidelines now have a section covering how to properly handle filtering of Automatic Provides and Requires:[20]

The GConf scriptlets have been rewritten to use macros (and be much simpler): [21]

The Guidelines concerning RPath have been clarified:[22]

The Guidelines concerning File and Directory ownership have been clarified:[23]

The Emacs Packaging Guidelines have been changed:[24]

The PHP Packaging Guidelines have been changed:[25]

The Fedora Packaging Guidelines now contain a section on dealing with Buildtime Macros in Source RPMS: [26]

A clarification note has been added to the SourceURL section, reminding Fedora packagers to use "downloads.sourceforge.net": [27]

These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC) and ratified by FESCo.

Many thanks to Pierre-Yves Chibon, Remi Collet, Mattias Ellert, Adam Jackson, Jussi Lehtola, David Malcolm, Till Maas, Bill Nottingham, Orcan Ogetbil, Rahul Sundaram, Alexey Torkhov, Jonathan Underwood, Ivana Varekova, Ian Weller, Chris Weyl and all of the members of the FPC and FESCo, 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:[28]

  1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-March/000584.html
  2. https://fedoraproject.org/wiki/Packaging/SourceURL#Referencing_Source
  3. https://fedoraproject.org/wiki/Packaging:Fortran
  4. https://fedoraproject.org/wiki/Packaging/Java
  5. https://fedoraproject.org/wiki/Packaging:R
  6. https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scrollkeeper
  7. https://fedoraproject.org/wiki/Packaging:Python
  8. https://fedoraproject.org/wiki/Packaging/Guidelines#Rpmlint_Errors
  9. https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries
  10. https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-built_binaries_or_libraries
  11. https://fedoraproject.org/wiki/Packaging:Guidelines#BuildRoot_tag
  12. https://fedoraproject.org/wiki/Packaging:Conflicts#Conflicting_Files
  13. https://fedoraproject.org/wiki/Packaging:WordPress_plugin_packaging_guidelines
  14. https://fedoraproject.org/wiki/Packaging:Globus
  15. https://fedoraproject.org/wiki/PackagingGuidelines#Pkgconfig_Files
  16. https://fedoraproject.org/wiki/Packaging:Guidelines#Man_pages
  17. https://fedoraproject.org/wiki/Packaging:MPI
  18. https://fedoraproject.org/wiki/Packaging:EnvironmentModules
  19. https://fedoraproject.org/wiki/Packaging:Alternatives
  20. https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering
  21. https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GConf
  22. https://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath
  23. https://fedoraproject.org/wiki/Packaging:Guidelines#File_and_Directory_Ownership
  24. https://fedoraproject.org/wiki/Packaging:Emacs
  25. https://fedoraproject.org/wiki/Packaging:PHP
  26. https://fedoraproject.org/wiki/Packaging:Guidelines#Source_RPM_Buildtime_Macros
  27. https://fedoraproject.org/wiki/Packaging:SourceURL#Sourceforge.net
  28. http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure

Build F-13 collection packages for all language translators

Noriko Mizumoto announced[1] to the Fedora package maintainers, "This is kind reminder asking you to rebuild your package with latest translation. Localization team has been translating for updated and/or newly added strings since the String is frozen (2010-02-09). To allow translators to review and correct their latest translation in UI, this is essential. This is different from 'Rebuild all translated packages for Beta', this is added entry since Fedora 12[2].

"Build F-13 collection packages for all language translators" is expected between 2010-03-03 to 2010-03-05. Please make sure your build is completed by 2010-03-05, so that a live image to be composed on 2010-03-05.

The packages to be built are: ABRT » master anaconda » master audit-viewer » tip authconfig » tip chkconfig » master comps » HEAD desktop-backgrounds » HEAD desktop-effects » master firstboot » master im-chooser » trunk initscripts » master iok » trunk kexec-tools » HEAD libuser » tip liveusb-creator » master mlocate » tip multimedia-menus » master newt » master passwd » tip policycoreutils » HEAD pykickstart » master python-meh » master readahead » master redhat-menus » HEAD setroubleshoot » tip-framework setroubleshoot » tip-plugins setuptool » master smolt » master smolt » master-smoon sos » trunk switchdesk » HEAD system-config-audit » tip system-config-bind » tip system-config-boot » master system-config-date » master-docs system-config-date » master system-config-date » master-timezones system-config-display » master system-config-firewall » master system-config-httpd » tip system-config-kdump » new system-config-keyboard » trunk system-config-kickstart » master system-config-language » trunk system-config-lvm » master system-config-netboot » trunk system-config-network » master system-config-nfs » master system-config-nfs » master-docs system-config-printer » master system-config-rootpassword » trunk system-config-samba » master system-config-samba » master-docs system-config-services » master system-config-services » master-docs system-config-users » master system-config-users » master-docs system-switch-java » tip system-switch-mail » HEAD usermode » tip"

Fedora 13 Alpha Go/No-Go Meeting

Fedora 13 Alpha Go/No-Go Meeting RESCHEDULED: 2010-02-25 at 19:00 UTC (14:00 EST)

Adam Williamson announced as an important note[1], "...we are rescheduling the Go/No-Go meeting for Fedora 13 Alpha. Previously scheduled for 2010-02-25 01:00 UTC, it is now scheduled for 2010-02-25 19:00 UTC (14:00 EST, 11:00 PST). This delay is to give sufficient time for the QA team to test the expected RC3 build.

The original announcement, with the new time, is reproduced below for reference.

Join us on irc.freenode.net #fedora-meeting for this important meeting. Thursday, February 25, 2010 @ 19:00 UTC (14:00 EST).

"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 important meeting see: [2]"

Feodra 13 Alpha slip by one week

Jesse Keating announced[1] on the basis of the announcement[2], "Today at the go / no-go meeting[3] we decided to slip the Alpha by one week. This slip is needed to verify blocker bug fixes and validate new builds of software necessary to fix those bugs. We are confident that the fixes we have are valid, however we do not have enough time to prove them valid. We will spend the next few days doing that validation. In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be pushed unless they are fixing a release blocking issue. Once we've validated all the fixes we will do more frequent pushes to 13 stable. At this time we are not adjusting later milestone dates, as with no frozen rawhide we are not taking away any developer time."

Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC (2010-03-03 @ 20:00 EST)

Adam Williamson announced[1], "Join us on irc.freenode.net #fedora-meeting for this important meeting. This is Thursday, March 4, 2010 @ 01:00 UTC, which makes it WEDNESDAY EVENING in North America: 20:00 EST, 17:00 PST.

"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 important meeting see:[2]"

Fedora 13 Alpha Go/No-Go Meeting: 2010-03-04 @ 01:00 UTC Recap

James Laska announced[1] the meeting summary, "Representatives from Fedora QA, Rel-Eng and Development met on IRC to review determine whether the Fedora 13 Alpha release criteria[2] have been met. The team agreed that the Alpha criteria have been met, and to proceed with releasing F-13-Alpha-RC4. For additional details, please refer to the attached minutes.

  • fedora-meeting: F-13-Alpha engineering readiness meeting

Meeting started by jlaska at 01:00:03 UTC. The full logs are available at [3].

Meeting summary

  • Waiting for critical mass . (jlaska, 01:00:25)
  • adamw representing QA (jlaska, 01:03:02)
  • Oxf13 representing Rel-Eng (jlaska, 01:03:07)
  • Oxf13 wearing the notting mask, representing Devel (jlaska,01:03:21)

Why are we here? (jlaska, 01:03:44)

  • The purpose is to decide whether the alpha has met the release criteria (jlaska, 01:03:49)
  • LINK:[4](jlaska, 01:03:54)

Go or No Go? (jlaska, 01:04:57)

  • all desktop and install validation tests for alpha point have been run (jlaska, 01:08:36)
  • only bug blocking alpha is [5] - we have decided it's okay as it has a usable workaround, so we should take it off the list (jlaska, 01:08:52)
  • ACTION: Decided that bug#567346 can be removed from F13Alpha(jlaska, 01:13:10)
  • LINK: [6](jlaska, 01:15:09)
  • IDEA: should KDE Live image be respun to address kpackagekit issue?(jlaska, 01:16:44)
  • source DVD is 5.0G (Oxf13, 01:20:49)
  • IDEA: need to determine how to handle source ISO's for F-13-Final(jlaska, 01:24:01)
  • ACTION: several remaining CommonBugs? needing documentation(jlaska, 01:25:15)
  • AGREED: QA + Rel-Eng + Devel* agreed to proceed with releasing F-13-Alpha-RC4 as the Alpha (jlaska, 01:26:09)

What's next? (jlaska, 01:26:38)

  • ACTION: adamw + jlaska to document remaining CommonBugs? issues(jlaska, 01:28:44)
  • LINK: [7] (Oxf13, 01:32:06)
  • ACTION: jlaska - send out the meeting minutes to devel-announce@test-announce@ and logistics@ (jlaska, 01:33:34)
  • expect to be fully staged for mirrors by tomorrow (Oxf13, 01:34:16)

Open Discussion (jlaska, 01:34:45)

Meeting ended at 01:36:45 UTC.

Action Items

  • Decided that bug#567346 can be removed from F13Alpha
  • several remaining CommonBugs? needing documentation
  • adamw + jlaska to document remaining CommonBugs? issues
  • jlaska - send out the meeting minutes to devel-announce@test-announce@ and logistics@

Action Items, by person

  • adamw
 * adamw + jlaska to document remaining CommonBugs? issues
  • jlaska
 * adamw + jlaska to document remaining CommonBugs? issues
 * jlaska - send out the meeting minutes to devel-announce@
   test-announce@ and logistics@
  • **UNASSIGNED**
 * Decided that bug#567346 can be removed from F13Alpha
 * several remaining CommonBugs? needing documentation

People Present (lines said)

  • jlaska (67)
  • Oxf13 (41)
  • adamw (32)
  • juhp (10)
  • poelcat (6)
  • rhe (4)
  • zodbot (4)
  • skvidal (2)

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 (March 2010 to May 2010)

  • 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.