Packages are peer reviewed against extensive packaging guidelines before being imported into the repository. Only updates that fix important bugs get pushed to the stable repository directly. Other updates hit a testing repository first and get released as an EPEL scheduled update in parallel with the EL scheduled updates. Packages often are tested in Fedora, too. The Fedora Packaging Guidelines and QA team back up all these efforts, helping to avoid errors.

A large number of contributors and users of Fedora and Enterprise Linux want to work within Fedora to provide these packages. The Fedora Project is a user of EPEL packages within the Fedora infrastructure itself. The Fedora Project is in a position to know the pain of not having a desired piece of software included in the RHEL distribution, and also a unique position to do something about it.

The plan is to have one primary maintainer per packages who is responsible for making certain that the package enhancements applied to one tree (for example, EL4) find their way into the other trees (for example, Fedora devel). This maintainer decides what makes sense to apply for the package in general. New EL branches for new EL releases are normally be created from the associated Fedora branch on which the EL release is based.

EPEL project provides add-on packages for Red Hat Enterprise Linux 5.x and 4.x releases and compatible derivatives. Packages for Red Hat Enterprise Linux 3 and 2.1 are not provided since they are under maintenance phase following the errata support policy from Red Hat and packages sourced from Fedora is unlikely to build properly against the older version of packages available in these releases making it very difficult to maintain properly.

You have to follow the same process as Fedora except that you can request an EPEL branch, tag, and build.

We view quality as a process not an end result, thus we have established quality control procedures for each stage of a construction project starting in the design phase. Our staff is dedicated to upholding these controls and providing our customers with a complete quality process according to the high standards of our company. | Back to Top

No, you don't have to. You can if you want, or you can ask somebody else to maintain the package in EPEL for you. In some cases, you may be approached by a current EPEL maintainer who wants to maintain your package in EPEL. You can use a compatible derivative of RHEL for testing, it should be 100% compatible. Mock is available in Fedora and ships config files that can be used to test build the packages. All Fedora packagers can request EPEL branches in CVS via the normal procedure.

Refer to the EPEL package maintenance and updates policy for all the details -- for a short overview, read the digest: The goal is to have packages in EPEL that enhances the Enterprise Linux distributions the packages were build against without disturbing or replacing packages from that distribution. The packages in the repository should, if possible, be maintained in similar ways to the Enterprise Packages they were built against.

The plan is for EPEL packages to get updates as long as the corresponding RHEL release is supported. That is seven years after the initial release according to the current errata support policy. The only way to be sure is to do it yourself, which is coincidentally the reason EPEL was started in the first place. Software packages in EPEL are maintained on a voluntary basis. If you to want ensure that the packages you want remain available, get involved directly in the EPEL effort.

Southtech is an ISO 9001: 2000 certified company for software analysis, design, development, testing, implementation, maintenance and sales. Our underwriter is United Registered Services (URS), a company based in the United Kingdom. Our processes are subject to frequent reviews and internal quarterly audits. Each project team has its own Quality Assurance (QA) Tester, in addition to a centrally managed independent QA Team.

We implement the Software Quality Assurance (SQA) process that addresses the quality assurance needs at every phase of the development cycle. Our QA team has developed a focused quality control checklist. In addition, we also have a comprehensive Quality Testing Checklist which ensures that every solution delivered by EEPL measures up to the highest possible international standards .

All inkTone cartridges are individually tested during manufacturing and must pass through multiple inspections before they made available to you. Our quality standards include testing each component prior to manufacturing, during production, and even after our products have reached the shelf.

All MSE cartridges are individually tested during manufacturing and must pass through a Triple Quality Control inspection before they get shipped to you. Our stringent quality standards include testing each component prior to manufacturing, during production, and even after our products are on the shelf. The result is a high performance product that has our Printer Resources Total Satisfaction Warranty.

Ensuring quality is our business. As our motto states: It's Retire-IT, or it is your word on IT! Retire-IT works solely with certified partners who follow industry best practices. We qualify each partner's processes and continuously monitor their performance. We employ rigorous statistical process control (SPC) to provide an advanced warning of potential quality problems. We internally managed logistics, not throw it over the wall to a 3rd party to manage for us.

All of our cartridges are individually tested during manufacturing and must pass through a Triple Quality Control inspection before they get shipped to you. Their stringent quality standards include testing each component prior to manufacturing, during production, and even after our products are on the shelf.

Our compatible inkjets and toner supplies are manufactured in ISO 9000 certified factories and are post tested to verify quality. All our supplies are guaranteed to perform as good or better then the OEM product.

Amerilab adheres to strict quality guidelines. We follow 21CFR 110.3 - 21CR 110.93. Amerilab has been certified by the NSF International as being compliant with GMP requirements in NSF/ANSI Standard 173, Section 8.

EPEL is just one of several add on repositories with RPM packages for RHEL and derivates. It is not a official repository. The different repositories serve different users bases or follow different ideas. Just like RHEL itself, EPEL in reality is more a "downstream" in the sense that Fedora is upstream and EPEL just like Red Hat takes packages for its product that are constantly developed, tested and received feedback in Fedora.

There are repository rpm packages for RHEL4 and RHEL5. The repository package installs the repo details on your local system for yum or up2date to use. Then you can install packages with your usual method, and the EPEL repository is included. su -c 'rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-2.noarch.rpm' ... su -c 'yum -y install foo'

This will probably happen in the future. I started making the rpms for libferris' dependancies well before Fedora started. There are many rpms that I have for the dependancies for libferris and it will take a while to feed them into the mainline Fedora project. The other point to note is that time spent packaging is time not spent coding and I tend to prefer the latter.

Fedora Core releases will be available as ISO images for both CDs and DVDs, and will also be available through other channels such as third-party online sales of physical media; distribution at Linux User Groups, included in magazines and in books, and maybe even handed out at trade shows. The bits may be actively pushed into content sharing networks such as BitTorrent. (Not all mechanisms will be used for each release, except that ISOs will be freely available for each release.

Yes, and we strongly encourage you to do so. You will need to comply with The Fedora Project trademark rules.

Security updates, bugfix updates, and new feature updates will all be available, through Red Hat and third parties. Updates may be staged (first made available for public qualification, then later for general consumption) when appropriate. In drastic cases, we may remove a package from The Fedora Project if we judge that a necessary security update is too problematic/disruptive to the larger goals of the project.

Red Hat will initially focus on the x86 family of architectures. Red Hat may also choose to build Fedora Core for other architectures, and in doing so will focus on architectures in which it has a business interest. This will make it easier to identify and fix bugs; the sooner they are found, the easier it is to isolate the change that caused the bug and therefore the easier it is to fix. Other community members are welcome to participate in building for other architectures.

One of CCBRT's maxims is to guarantee quality in all that we do. Having properly qualified staff members ensures good levels of professionalism in our work. CCBRT therefore supports staff development through internal and external training on a regular basis. In addition, professional supervisors mentor and monitor the work of community rehabilitation workers, reviewing and evaluating the rehabilitative outcomes of each child.

Providing high-quality legal staffing on a consistent basis requires the frequent attention of our staff of professional recruiters. JurisTemps closely monitors the performance, attendance, punctuality, and overall quality of our employees' work. Employers are asked to evaluate the performance of temporary employees on an on-going basis, and our recruiters maintain frequent communication with the on-site supervisor to ensure continued success.

We implement the Software Quality Assurance (SQA) process that addresses the quality assurance needs at every phase of the development cycle. Our QA team has developed a focused quality control checklist. In addition, we also have a comprehensive Quality Testing Checklist which ensures that every solution delivered by QualSoft measures up to the highest possible international standards.

Super Talent products are built only with carefully selected, quality components. All component vendors must meet our quality standards and pass our qualification testing before we can use their components. Our products are 100% tested to ensure functionality.

Recruitment is done exclusively on merit. Each employee has to undertake a mandatory 2 weeks training every 6 months. No doubt, Tricon has one of the most qualified resource pool in the country.

We implement the Software Quality Assurance (SQA) process that addresses the quality assurance needs at every phase of the development cycle. Our QA team check the design and coding of software in each stage of development and we also prepare a check list for quality control. In addition, we also have a comprehensive Quality Testing Checklist which ensures that every solution delivered by Silicon Valley measures up to the highest possible international standards.