Apache Subversion Community Guide (aka "HACKING")

Table of Contents

• General Overview
  • Participating in the community
  • Theory and documentation
  • Code to read
  • Directory layout
  • Branch policy
  • Documentation
  • Patch submission guidelines
• Community Roles
  • Committers
  • Release Manager
  • Patch Manager
• Coding and Commit Conventions
  • Code modularity and interface visibility
  • Coding style
  • Using page breaks
  • Error message conventions
  • APR pool usage conventions
  • APR status codes
  • Exception handling
  • Secure coding guidelines
  • Destruction of stacked resources
  • Variadic argument lists
  • Other coding conventions
  • Writing log messages
  • Crediting
  • GitHub
• Building and Testing
  • The configuration/build system under unix
  • Automated tests
  • Build farm
  • Writing test cases before code
• Debugging Subversion
  • Debugging with SVN_DBG
  • Debugging the server
  • Tracing network traffic
  • Tracking down memory leaks
• Web Site Changes
  • Introduction
  • Obtaining the web site source
  • Setting up a mirror for testing
  • Validating your changes
  • Creating a patch and a log message
• Mailing Lists
  • Where to post
  • When to post
  • Formatting
  • Replying
  • Sending patches
  • Languages and encodings
• Bugs/Issues
  • How to report a bug
  • Where to report a bug
  • Milestone management
  • Issue triage
  • Security
• Making Subversion Releases
  • Subversion release process
  • Release numbering
  • Inter-release compatibility
  • Custom releases
  • Deprecation
  • Stabilizing and maintaining releases
  • Creating a Subversion release
  • Notify translators
  • Preparing to roll a release
  • Rolling a release
  • Signing source distribution packages (a.k.a tarballs)
  • The actual releasing
  • Creating and maintaining release branches
  • Preparing to create a new minor release branch
  • Creating a new minor release branch
  • Porting changes to a release branch
  • Managing the CHANGES file
  • Writing the initial content for a branch
  • Adding content for patch release
  • How not to make a Subversion release
• Localization
  • Localization overview
  • Software version requirements
  • Starting a new translation
  • Verifying your po file
  • Submitting your po file
  • Updating existing po files
  • Maintenance on branches
  • Requirements for po and mo files
  • Conventions for the empty string msgid section
  • Translation teams
  • Single versus double quotes
  • Error message conventions