This section includes many of the reference materials used by the Apache HTTP Server Project.

The Apache HTTP Server Project has begun development of the 2.1-dev branch! The developers seek to maintain module compatibility between 2.0.42 and future 2.0 releases for administrators and end users, while continuing the forward progress that has made the 2.0 server faster and more scalable.

Developers who have active CVS trees may want to cvs up -r APACHE_2_0_BRANCH to continue to work with the current httpd-2.0 cvs sources. Developers who want to work in the 2.1-dev sandbox should continue to use cvs HEAD.

The simplest way for committers to work with this change is to commit new work to the 2.1-dev sources (cvs HEAD), obtain appropriate feedback, and finally commit back to the APACHE_2_0_BRANCH those stable and well tested changes that don't break compatibility with the most recent 2.0 release.

• Contributing bug reports
• Contributing code patches
• Tips to debug your server

• Project guidelines
• Release guidelines
• Style guide

• Apache Development Notes about using CVS and maintaining the Apache site.
• Instructions on developer access to the repository via Anonymous CVS.
• Instructions on developer access to the repository via CVSup.
• CVS and SSH for NT users, useful for NT developers.
• Record of changes to the module magic number: 1.3 2.0
  

• A Web-based view of the CVS history of the development effort
• The latest source tree pulled from the CVS repository, packaged with tar, and compressed with gzip. Not guaranteed to do anything, especially not compile or work.
• Doug MacEachern wrote a Perl script which you can use to automate fetching from the above from-cvs location.

• Release guidelines
• Instructions for rolling the release tarballs
• How to build binary distributions
• A shell script to build a binary release
• Verifying Apache HTTP Server releases

• The latest draft of the project plan
• notes on the API
• A prototype reference dictionary for the Apache HTTP Server API
  (note: this link may not take you anywhere useful; the documents may be missing or in a state of flux. Caveat spectator.)
• The old to-do list of the Apache developers.
• Old voting guidelines