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.1 #2233

Closed
10 tasks done
tomchristie opened this issue Dec 8, 2014 · 16 comments
Closed
10 tasks done

Release 3.0.1 #2233

tomchristie opened this issue Dec 8, 2014 · 16 comments
Labels
Milestone

Comments

@tomchristie
Copy link
Member

Release manager is @xordoquy.
Release pull request is #2251.

Checklist:

  • Create pull request for release notes based on the 3.0.1 milestone.
  • Ensure the pull request increments the version to 3.0.1 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.1 -m 'version 3.0.1'; 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.
@tomchristie tomchristie added this to the 3.0.1 Release milestone Dec 8, 2014
@tomchristie tomchristie changed the title Release 3.0.1. Release 3.0.1 Dec 10, 2014
@xordoquy
Copy link
Collaborator

@tomchristie mind if we open the wiki and put it there ? It'll make it easier to find for later release managers.

@tomchristie
Copy link
Member Author

I don't want to use a wiki, but I don't mind if we have a page in the documentation which describes our project management & polices etc...

@xordoquy
Copy link
Collaborator

Perfect then

@tomchristie
Copy link
Member Author

Ok I think we're good to go on this one. I may create the release notes pull request tomorrow morning unless you get there first. Rest up to you. :)

@xordoquy
Copy link
Collaborator

I'm currently doing them and almost got them finished.
However I noticed I have an issue with #2197
It seems to me it break the deprecation policy within a micro release which is a bad thing.

@xordoquy
Copy link
Collaborator

PR for the release notes and version bump is #2251

@tomchristie
Copy link
Member Author

No actually the rename doesn't matter. We're passing that argument by position, not by keyword argument so if overriding the method then whatever name the developer uses for that parameter will work fine.

@xordoquy
Copy link
Collaborator

Rereading the #2251, I agree with you. Feel free to merge #2251 if you feel ok with it and we'll go on the next steps.

@tomchristie
Copy link
Member Author

@xordoquy Some fixes commented against #2251. What do you think about @kevin-brown and @jpadilla's Q on hyperlinking the issues, or is that a bit much?

@xordoquy
Copy link
Collaborator

I'll fix the comment and add the links today.

@tomchristie
Copy link
Member Author

Happy for the release to happen whenever is good for you.

@xordoquy
Copy link
Collaborator

Will do this evening.

@xordoquy
Copy link
Collaborator

Note: make sure you have wheels installed while doing the setup.py publish

@xordoquy
Copy link
Collaborator

Looks like the doc generation removed 2 images (c05c1f5)

@xordoquy
Copy link
Collaborator

ok, done !

@xordoquy
Copy link
Collaborator

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

2 participants