Index of CFEPs

Changes to the project should be submitted as conda-forge enhancement proposals (CFEP). These CFEPs are similar to Python's PEP and IPython's IPEP processes.

CFEPs are stored in the cfep GitHub repository. A list of conda-forge enhancement proposals (CFEP) are as follows:

• CFEP-00: CFEP Template -- Proposed
• CFEP-01: CFEP Purpose and Guidelines -- Proposed
• CFEP-02: Upgrade default macOS Travis image to xcode6.4 -- Accepted
• CFEP-03: Providing manually uploaded builds on the conda-forge anaconda channel -- Accepted
• CFEP-04: Policies for packaging X11-based software in conda-forge -- Deferred
• CFEP-05: Providing pre-release builds on the conda-forge anaconda channel -- Accepted
• CFEP-06: staged-recipes code review lifecycle -- Deferred
• CFEP-07: Migration strategy to Anaconda compilers -- Proposed
• CFEP-08: Packages which are "Too Big to Fail" -- Deferred
• CFEP-09: Pinning Proposal System for Automatic Rebuilds -- Accepted
• CFEP-10: Feedstock Statuses -- Deferred
• CFEP-11: Automated Closing of Excessively Old PRs on Staged Recipes -- Accepted
• CFEP-13: Securing conda-forge Uploads to anaconda.org -- Accepted
• CFEP-14: Security and Systems Subteam -- Accepted
• CFEP-15: Deprecate Python 2.7 and vs2008 -- Accepted
• CFEP-16: Setting license and license_family field -- Accepted
• CFEP-17: Branches for Globally Pinned Packages -- Deferred
• CFEP-18: Packaging static libraries -- Accepted
• CFEP-19: Pinning Epochs -- Deferred
• CFEP-20: Standard package split (dev / doc / dbg) -- Deferred
• CFEP-23: Migration to the Zulip chat platform -- Accepted
• CFEP-24: More Secure Package Name Approval Process -- Accepted
• CFEP-25: Globally Pinned Minimum Python Version for noarch: python Packages -- Accepted