Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

djangocon.eu 2012 sprint

stefanfoulis edited this page · 13 revisions
When:
on the 7th and 8th of June 2012 starting 10:00 CET
Where:
Cigarettenfabrik Zürich and IRC (#django-cms on freenode)
Core devs and organizers:
Jonas (@ojii), Stefan (@stefanfoulis), Beni (@piquadrat), Chris (@Tribaal)

Day 2 Focus

morning:
fix the open 2.2.1 Must issues.
afternoon:
intensive frontend testing / test integration in existing projects

Sprint Focus

Our goal is a 2.2.1 RC release containing important bugfixes and django 1.4 compatibility.

Issues / Milestones

The relevant issues have been organized into three milestones on github.

Workflow

1. Claim

Have a look at the open issues and find one you feel comfortable solving. Then contact one of the core devs to claim it. We'll then tag the issue as claimed and add [claimed by @username] to the description.

2. Code

Make a feature branch and start coding. Don't forget tests ;-)

3. Pull Request

Make a pull request to the develop branch on divio/django-cms. A core dev will review your pull-request, give you feedback and eventually merge it.

Tips

  • Important: We're working on django-1.4 support. But don't forget that we have to maintain backwards compatibility to django-1.3+. Supported python versions are 2.5, 2.6 and 2.7
  • Contributing to django-cms from the django-cms docs
  • Always make feature branches (the git flow extension is awesome). If you'd use your develop branch for feature development, you'd be screwed if the pull request is not accepted. Also it makes it hard to work on multiple features without cluttering pull requests with unrelated commits.
  • you can run the testsuite with ./runtests.sh. To run them for a specific version: ./runtests.sh -d 14, ./runtests.sh -d 13 or ./runtests.sh -d 14.
  • jenkins ci: http://ci.django-cms.org/job/django-cms/
Something went wrong with that request. Please try again.