Django internals

Documentation for people hacking on Django itself. This is the place to go if you’d like to help improve Django or learn about how Django is managed.

• Contributing to Django
  • Advice for new contributors
  • Reporting bugs and requesting features
  • Triaging tickets
  • Writing code
  • Writing documentation
  • Localizing Django
  • Committing code
• Mailing lists
  • django-users
  • django-core-mentorship
  • django-developers
  • django-i18n
  • django-announce
  • django-updates
• Organization of the Django Project
  • Principles
  • Core team
  • Technical board
  • Changing the organization
• Django’s security policies
  • Reporting security issues
  • Supported versions
  • How Django discloses security issues
  • Who receives advance notification
  • Requesting notifications
• Django’s release process
  • Official releases
  • Release cadence
  • Deprecation policy
  • Supported versions
  • Release process
• Django Deprecation Timeline
  • 3.0
  • 2.1
  • 2.0
  • 1.10
  • 1.9
  • 1.8
  • 1.7
  • 1.6
  • 1.5
  • 1.4
  • 1.3
• The Django source code repository
  • High-level overview
  • The master branch
  • Other branches
  • Tags
• How is Django Formed?
  • Overview
  • Prerequisites
  • Pre-release tasks
  • Preparing for release
  • Actually rolling the release
  • Making the release(s) available to the public
  • Post-release
  • New stable branch tasks
  • Notes on setting the VERSION tuple