[Bug 431929] New: Please add perl-Module-Versions-Report to the EPEL repos

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.




https://bugzilla.redhat.com/show_bug.cgi?id=431929

           Summary: Please add perl-Module-Versions-Report to the EPEL repos
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: low
          Priority: low
         Component: perl-Module-Versions-Report
        AssignedTo: cweyl at alumni.drew.edu
        ReportedBy: xavier at bachelot.org
         QAContact: extras-qa at fedoraproject.org
                CC: fedora-perl-devel-list at redhat.com


Hi!

There are people around that would like to see some of your Fedora
packages in Extra Packages for Enterprise Linux (EPEL) [1] -- I for
example would like to see perl-Module-Versions-Report in EPEL, which is
needed for rt3 (Request Tracker 3) and mainly send you this mail on
behalf of the EPEL team as you didn't yet let the team know via the
Contributor Status [2] page if you are planning to build some or all of
your Fedora packages for EPEL.

Are you interested in maintaining your packages in EPEL? EPEL is similar
to Fedora Extras -- just that EPEL is a add-on repo for RHEL and
compatible spinoffs such as CentOS. EPEL uses the same CVS and the same
build servers as Fedora and a lot of Fedora maintainers are EPEL
maintainers as well; the main difference is just that packages in EPEL
are updated more carefully and supported for a longer timeframe. See [3]
and [4] for details. In short: EPEL tries to ship a package once and
update it to later versions only when there is a strong need to.

For branching your packages for EPEL follow the standard Fedora
procedure[5] -- instead of FC-6 or F-7 targets just use EL-4 or EL-5 as
branch names. If you maintain several packages (> 2) you can also use a
scripted branching method (all packages from a contributor) by using the
scripted branch process[6].

If you are not interested in EPEL please let the EPEL contributors know
and update the information on [2] to avoid further mails like this --
that just takes a minute or two and would be a great help for the EPEL
team. Please note that EPEL maintainers that might want to see your
package in EPEL will likely start to maintain the package in EPEL sooner
or later and thus become co-maintainers [7] of your packages for EPEL.

The EPEL team appreciate your help with EPEL.

[1]http://fedoraproject.org/wiki/EPEL

[2]http://fedoraproject.org/wiki/EPEL/ContributorStatus

[3]http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies

[4]http://fedoraproject.org/wiki/EPEL/FAQ

[5]http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure

[6]http://fedoraproject.org/wiki/MichaelStahnke/ScriptedBranchProcess

[7]http://fedoraproject.org/wiki/Extras/Policy/EncourageComaintainership

Regards,
Xavier

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.