From Fedora Project Wiki

< FWN‎ | Beats

mNo edit summary
No edit summary
Line 14: Line 14:
<references/>
<references/>


====Your input requested at the Fedora Board IRC meeting this Friday====
====Announcing EPEL 6====
Fedora Project Leader [[User:Jsmith|Jared K. Smith]]<ref>Jared K. Smith jsmith at fedoraproject.org</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-January/002905.html</ref> on Thu Jan 6 13:04:42 UTC 2011,


"Over the past few months, the Fedora Board has focused on coming up with two or three overarching goals that can be accomplished over the next few release cycles. We've got a fairly healthy list of goals at this point, and welcome your input in helping us decide which two or three goals are most important. The Fedora Board will be having its bi-weekly IRC meeting this coming Friday, and we invite you to attend that meeting and share your input with us. Instead of our normal question and answer session, we'll instead focus on prioritizing our list of goals.
Kevin Fenzi <ref>kevin at tummy.com</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-January/002908.html</ref> on Wed Jan 19 23:33:37 UTC 2011,


The meeting is in the #fedora-board-meeting channel on the Freenode IRC network at 2:00pm EST (19:00 UTC).  In order to keep the meeting organized and easy to follow, we ask that participants follow the instructions in the "General Rules" section of <ref>https://fedoraproject.org/wiki/Board_public_IRC_meetings</ref>."
"The Extra Packages for Enterprise Linux (EPEL) project is happy to announce the release of EPEL 6 today!


<references/>
EPEL 6 is a collection of add-on packages available for Red Hat
 
Enterprise Linux (RHEL) 6 and other compatible systems, maintained by
=== Fedora Development News ===
the community under the umbrella of the Fedora Project. EPEL 6 is
 
designed to supplement RHEL 6 by providing additional functionality
The development list<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref> is intended to be a LOW TRAFFIC announce-only list for Fedora development.
and does not replace any RHEL 6 packages. As a community project,
 
EPEL is maintained and supported by volunteers via Bugzilla and
'''Acceptable Types of Announcements'''
mailing lists.  EPEL is not commercially supported by Red Hat, Inc.
* 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
 
<references/>


====evolution-data-server (2.91.5) soname bump and library files location changes in Rawhide==== 
Included are over 2500 source packages that build into over 5600
Milan Crha<ref>Milan Crha mcrha at redhat.com </ref> announced <ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-January/000740.html</ref> on Mon Jan 10 10:06:25 UTC 2011,
binary packages. We are always seeking volunteers eager and willing
to help maintain new packages. Refer to the URL below to join us!


"with the recent evolution-data-server 2.91.5 release in Rawhide are done some internal changes in the soname versions and a location where the backend files for the addressbook and calendar should be saved.
=====Some highlights=====


>From the commit log:
* rt3 - The Request Tracker Bug and Ticket tracking system, as well as
it's 90 perl packages dependencies.


Change the installation path for E-D-S backends.
* trac - Project management system, along with many plugins.  
 
Address book and calendar backend modules are now split into different installation directories so the D-Bus factory processes will only load relevant backend modules.


This changes some pkg-config details for third-party backend modules.
* haproxy, varnish and lighttpd proxies and web servers.  
   
Instead of querying the backend directory with:
'''pkg-config --variable=extensiondir evolution-data-server-1.2'''


you must query the directory for address book backends with:
* BackupPC, rdiff-backup and other backup clients.  
'''pkg-config --variable=backenddir libedata-book-1.2'''


and the directory for calendar backends with:
* A large stack of Ruby packages.  
'''pkg-config --variable=backenddir libedata-cal-1.2'''"


<references/>
* Spamassassin plugins, clamav and other mail server and filtering
solutions.


====gtk2 2.99.0==== 
* rkhunter and chkrootkit security scanners.  
Matthias Clasen<ref>Matthias Clasen mclasen at redhat.com </ref> on Mon Jan 10 20:00:33 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-January/000741.html</ref>,


"I have just tagged gtk3-2.99.0 into rawhide. There are abi and api changes, so all dependent packages will have to be rebuilt (the most obvious change is that the libraries are now called libg[dt]k-3.0.so instead of libg[gt]k-x11-3.0.so).
* collectd, munin, nagios and cacti monitoring solutions.  


There are a number of api changes that I am not going to list one-by-one here, the following changes are relevant for packagers:
* Over 600 perl packages.


* gtk-update-icon-cache-3.0 and gtk-builder-convert-3.0 have been dropped (since they were identical to their un-suffixed cousins in the gtk2 package). If you are using gtk-update-icon-cache in %post of a gtk3-using package, you should add Requires(post): /usr/bin/gtk-update-icon-cache (and similar for %postun).
* And many more...  


* The .pc files no longer define a 'target' variable, instead there is a 'targets' variable which can contain multiple gdk backend names (for now, it is still just 'x11', eventually it might change to be 'x11 wayland' or so). Some configure scripts use that variable to detect the platform they are running on and will need adjustment.
=====To use EPEL 6:=====


I have built most packages that had a gtk3 dependency already, and tagged them into rawhide. The following are the leftovers:
<ref>https://fedoraproject.org/wiki/EPEL6-FAQ#How_do_I_use_it.3F</ref>


* gtkmm30
=====To Join us, or for more information on the EPEL project:=====
* libindicator-gtk3
* tracker
* gedit
* gnome-color-manager
* gnome-nettool
* gtk-vnc2
* eekboard
* input-pad
* ibus-input-pad
* seahorse-plugins
* rhythmbox"


<ref>https://fedoraproject.org/wiki/EPEL</ref>"
<references/>
<references/>


====bodhi v0.7.10 production update==== 
=== Fedora Development News ===
Luke Macken<ref>Luke Macken lmacken at redhat.com</ref> on Mon Jan 10 23:46:02 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-January/000742.html</ref>,


"I just pushed a new release of bodhi into production.
The development list<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref> is intended to be a LOW TRAFFIC announce-only list for Fedora development.


<ref>http://bodhi.fedoraproject.org</ref>
'''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


It's a minor release that contains a small number of fixes, including:
'''Unacceptable Types of Announcements'''
 
* Periodic automated reports (violates the INFREQUENT rule)
====='''Backend bug fixes'''=====
* Discussion
* Don't try and remove the -pending koji tags when resuming a push
* Anything else not mentioned above
* Don't fetch security bug details when resuming a push
* Don't show obsolete critpath updates in our testing digest
* Ensure the updateinfo epoch is '0' as opposed to None (rel-eng#3971)
* Stop spamming proventesters with old critpath mails, as this data is available in the updates-testing digests that go out with each push
 
====='''Web frontend changes'''=====
* Fix the testing status tooltips for EPEL (#486)
* Add the update ID back to the search results (#558)
* Don't hide updates that are not approved by the security team from the admin push view, since we no longer require approval
 
====='''API changes (for AutoQA)'''=====
* Support querying and commenting on updates by the Update ID, as well as title
 
====='''Tool changes'''=====
* Make `bodhi --push-type` work for updates going to testing as well as stable (rel-eng only)
* Add pkg_resources __requires__ hacks to get things working on F14
 
As always, please file tickets here: https://fedorahosted.org/bodhi/newticket
 
Thanks,"
 
<references/>
 
====New test case and package test plan creation SOPs in production: call for test cases!==== 
Adam Williamson<ref>Adam Williamson awilliam at redhat.com </ref> on Tue Jan 11 13:21:02 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-January/000743.html</ref>,
 
"Hi, everyone. Thanks to everyone who sent feedback on the drafts for the
test case and package test plan creation SOPs. I have now put these SOPs
into production, at the following addresses:
 
<ref>https://fedoraproject.org/wiki/QA:SOP_test_case_creation</ref>
<ref>https://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation</ref>
 
I have created links to them from other places in the QA wiki space. It
would be nice to have them called out from within the developers/package
maintainers space, but I'm not sure where would be appropriate: does
anyone have suggestions?
 
Now these are in production, it would be great if people could start
contributing test cases for packages, particularly test cases covering
critical path functions. If you maintain a critical path package, please
take a look at these two SOPs, and consider contributing test cases
covering at least the critical path functionality of your package; this
would help us greatly, and contribute to the improvement of critical
path testing by the proven testers. For the QA group, please also
consider contributing critical path test cases - you don't have to be a
maintainer of a package to do it! If you know how to test the critical
path functionality of a given package, please read the SOPs, write up
test case(s) to do it, and categorize them appropriately. Thanks a lot!"


<references/>
<references/>
====EPEL6 moving from Beta to release status soon==== 
Kevin Fenzi <ref>Kevin Fenzi kevin at scrye.com </ref> on Tue Jan 11 21:33:21 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-January/000744.html</ref>,
"Greetings.
Just a heads up that EPEL will soon be moving it's EPEL6 branch from
the Beta mode (like rawhide) that it's been in to a release mode (like
EPEL4/5 are). (I have cc'ed Fedora's devel-announce here as there may
be people not on the epel-devel list that might find this of interest).
=====Timeline: =====
2011-01-13 - Have any builds you wish done before release done. After
this point you will need to request a package be tagged into the stable
or testing repos or wait until bodhi is up for EPEL6.
2011-01-14 - EPEL rel-eng will work on composing and moving things
around. This may include untagging packages that have broken deps, or
moving them into testing, test composing, etc. Hopefully we can mirror
out trees.
2011-01-15
2011-01-16 - Maintainers encouraged to check new trees and help with
wiki prep, etc.
2011-01-17 - Bodhi will be enabled for EPEL6 and things will move to a
release mode: All packages spend 2 weeks in testing or +3 karma, bodhi
is used for updates, buildroot overrides are required as usual.
2011-01-18 - RELEASE DAY. Help with press release or announcements
would be welcome.
=====Work/help needed:=====
* Would be great if someone could make us a press release and had a way to distribute it out.
* We need work on our wiki pages. A EPEL6 FAQ would be very nice.
* Maintainers need to determine what packages they want to ship for EPEL6. If you do not want to ship whats there now, please untag it before thursday.
Feel free to drop by #epel on freenode or drop an email to the
<ref>https://www.redhat.com/mailman/listinfo/epel-devel-list</ref>
Thanks for all the work folks, and enjoy EPEL6!"
<references/>


=== Fedora Events ===
=== Fedora Events ===

Revision as of 17:10, 20 January 2011

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. ↑ https://admin.fedoraproject.org/mailman/listinfo/announce

Announcing EPEL 6

Kevin Fenzi [1] announced[2] on Wed Jan 19 23:33:37 UTC 2011,

"The Extra Packages for Enterprise Linux (EPEL) project is happy to announce the release of EPEL 6 today!

EPEL 6 is a collection of add-on packages available for Red Hat Enterprise Linux (RHEL) 6 and other compatible systems, maintained by the community under the umbrella of the Fedora Project. EPEL 6 is designed to supplement RHEL 6 by providing additional functionality and does not replace any RHEL 6 packages. As a community project, EPEL is maintained and supported by volunteers via Bugzilla and mailing lists. EPEL is not commercially supported by Red Hat, Inc.

Included are over 2500 source packages that build into over 5600 binary packages. We are always seeking volunteers eager and willing to help maintain new packages. Refer to the URL below to join us!

Some highlights
  • rt3 - The Request Tracker Bug and Ticket tracking system, as well as

it's 90 perl packages dependencies.

  • trac - Project management system, along with many plugins.
  • haproxy, varnish and lighttpd proxies and web servers.
  • BackupPC, rdiff-backup and other backup clients.
  • A large stack of Ruby packages.
  • Spamassassin plugins, clamav and other mail server and filtering

solutions.

  • rkhunter and chkrootkit security scanners.
  • collectd, munin, nagios and cacti monitoring solutions.
  • Over 600 perl packages.
  • And many more...
To use EPEL 6:

[3]

To Join us, or for more information on the EPEL project:

[4]"

  1. ↑ kevin at tummy.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2011-January/002908.html
  3. ↑ https://fedoraproject.org/wiki/EPEL6-FAQ#How_do_I_use_it.3F
  4. ↑ https://fedoraproject.org/wiki/EPEL

Fedora Development News

The development list[1] 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
  1. ↑ https://admin.fedoraproject.org/mailman/listinfo/devel-announce

Fedora Events

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]
  1. ↑ http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29
  2. ↑ http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29_2
  3. ↑ http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29_2
  4. ↑ http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29_3

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