Hi folks,
We released an alpha of Django 1.4 on December 22nd. We plan to release a beta
on Feb 2nd and the final version an March 1st. By then, we'd like to fix as
many bugs as possible, starting with those that matter most to you.
You may be familiar with our contributing processes, but in case you aren't, on
behalf of the core team, here's a summary of what you can do to help us.
1) Test the new features in 1.4 alpha and report bugs
There isn't much to explain here :)
Release notes: https://docs.djangoproject.com/en/dev/releases/1.4-alpha-1/
How to report bugs:
https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-features/
2) Run the test suite on your favorite platform (OS, Python, database)
Django 1.4 supports all mainstream OSes, CPython 2.5 to 2.7, and 4 database
engines (including their geospatial versions). If you see a failure that isn't
reported in our bug tracker yet, please open a ticket!
How to run the test suite:
https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/
3) Review existing patches
Once a contributor has uploaded a patch for a ticket, we ask that someone else
reviews it, in order to guarantee its quality.
If the patch matches all the criteria for inclusion in Django, the reviewer can
move the ticket from "Accepted" to "Ready For Checkin" — and then a core
developer will take ownership of the ticket and commit the patch. If it
doesn't, the reviewer should explain how to improve the patch.
In short, the quality criteria are:
- all comments made on the ticket are taken into account (or rebutted),
- code makes sense (comments count there)
- code is clean (PEP 8, see the coding style guide in the documentation for
more information),
- relevant tests are included,
- relevant docs are included,
- there is one patch, relative to the `trunk` directory, that contains all
the changes and applies cleanly on the latest SVN revision.
We're currently stuck with around 200 patches waiting for review:
https://code.djangoproject.com/query?status=!closed&needs_better_patch=0&needs_tests=0&needs_docs=0&has_patch=1&stage=Accepted&desc=1&order=changetime
Add some search criteria, such as "Easy pickings = yes", or "Component =
Documentation", to locate easy patches.
4) Triage unreviewed tickets
Anyone can triage unreviewed tickets. That gives the core team more time to
spend on other tasks, such as committing patches or making design decisions.
Also, with the 5-for-1 deal, if you triage 5 unreviewed tickets, you may ask a
core developer to review one ticket of your choice — just send to this list the
ticket numbers and your question.
You can track tickets counts here: http://dddash.ep.io/ The core team handles
tickets whose triage stage is "Design Decision Needed" and "Ready For Checkin";
everything else is in your hands!
If you're interested in contributing to Django, you'll find a wealth of
information here: https://docs.djangoproject.com/en/dev/internals/contributing/
Finally, there are always a few core devs hanging out in #django-dev on
FreeNode. If you have questions, just ask and we'll do our best to help you.
Thanks in advance!
--
Aymeric Augustin.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
