Key

This line was added.

This line was removed.

Formatting was changed.

...

The core contributors to Clojure try to code patches for bugs first, and then move on to feature requests. Therefore if you have an accepted CA, there is a major feature that interests you, and it is missing a patch, feel free to code the patch yourself. As with most open source projects, if you find a missing feature bothersome, your you are most likely the right person to code the implementation.

...

Once a patch has been screened, it is sent to Rich Hickey for final approval. Rich can perform one of three actions on the ticket. He can outright reject it (perhaps asking that it be put into a contrib library), he can approve it for the current release, or he can approve it for the next release.

If a ticket is marked for the current release, one of the Clojure committers will take the patches attached to the ticket and commit them to the github repository. At this point the ticket is marked as done, and the ticket number is placed into the changelog for the next release of Clojure.

One Once beta testing starts for a given version of Clojure, all new features will be placed in the backlog for the next release , and only bug fixes will be accepted for the current release. Once the current version of Clojure has been released, the next release backlog will be comited committed to the source repository.