Release 3.3.3

[xordoquy]

Release manager is @xordoquy.
Pull request is #3924.

During development cycle:

• Upload the new content to be translated to transifex.

Checklist:

• Create pull request for release notes based on the 3.3.3 milestone.
• Update the translations from transifex.
• Ensure the pull request increments the version to 3.3.3 in restframework/__init__.py.
• Confirm with @tomchristie that release is finalized and ready to go.
• Ensure that release date is included in pull request.
• Merge the release pull request.
• Push the package to PyPI with ./setup.py publish.
• Tag the release, with git tag -a 3.3.3 -m 'version 3.3.3'; git push --tags.
• Deploy the documentation with mkdocs gh-deploy.
• Make a release announcement on the discussion group.
• Make a release announcement on twitter.
• Merge back into master.
• Close the milestone on GitHub.

[johnraz]

I'm a bit confused about the release number, 3.3.3 is available on pypi and I see this issue is still open?
@xordoquy can you clarify the situation please?

[tomchristie]

Notice I'd wrongly tagged #4040 as 3.3.3 - have just re-milestone'd now. Perhaps I confused @xordoquy with that?

[johnraz]

At least it confused me :-)

[xordoquy]

nop. I need to take some time and write down things.

[xordoquy]

Some explanations are given in #4044.
I'll close this issue and the associated milestone once #4044 is merged.
I'll still have to update the release guide and template.

[johnraz]

k, so bugfixes should still submitted against master right? and you take care of backporting them to 3.3.x ? What is not clear to me is why you then need to merge back to 3.3.x to master... But well I guess you guys are dealing with it.

[buzzijavier]

Shouldnt this be closed? https://pypi.python.org/pypi/djangorestframework/3.3.3

[xordoquy]

as explained above, no

[xordoquy]

Ok, #4044 merged, closing this.