Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 3.0.3 #2384

Closed
10 tasks done
xordoquy opened this issue Jan 7, 2015 · 6 comments
Closed
10 tasks done

Release 3.0.3 #2384

xordoquy opened this issue Jan 7, 2015 · 6 comments
Assignees
Labels
Milestone

Comments

@xordoquy
Copy link
Collaborator

xordoquy commented Jan 7, 2015

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

Checklist:

  • Create pull request for release notes based on the 3.0.3 milestone.
  • Ensure the pull request increments the version to 3.0.3 in restframework/__init__.py.
  • Confirm with @tomchristie that release is finalized and ready to go.
  • Merge the release pull request.
  • Push the package to PyPI with ./setup.py publish.
  • Tag the release, with git tag -a 3.0.3 -m 'version 3.0.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.
  • Close the milestone on GitHub.
@xordoquy xordoquy added this to the 3.0.3 Release milestone Jan 7, 2015
@xordoquy xordoquy self-assigned this Jan 7, 2015
@tomchristie
Copy link
Member

Okay, I'm now officially loving this process :)

@xordoquy
Copy link
Collaborator Author

xordoquy commented Jan 8, 2015

Anything against adding #2386 to this milestone ?

@tomchristie
Copy link
Member

Sure, go right ahead.

@trehn
Copy link

trehn commented Jan 8, 2015

Just ran into #2386 and now a fix is about to be released. Thank you! :)

@tomchristie
Copy link
Member

Thanks @trehn - useful to have an extra data point on that one. Surprised we haven't had it raised before, but more confidence inspiring to see someone else hit it.

Out of interest, what OS/installation etc... were you using that triggered it?

@trehn
Copy link

trehn commented Jan 8, 2015

It only occurred in my dev environment which I set up using python setup.py develop (and thus uses easy_install). For production installs I use and recommend pip, so the problem would never happen there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants