Dj-stripe: Official 1.0.0 Branch

[lskillen]

@kavdev - I keep meaning to bring this up but it would be extremely helpful if the existing #api-updates-through_2015-07-28 was branched (or re-branched) as something like 1.0.0, next, develop or even using master if that's your preference. The main reasons that I can think off the top of my head (in no particular order, but preference is subjective):

1. Jumping between the branches locally when developing/testing is awkward (I always have to look it up first).
2. I'm not able to (easily) target the branch via pip requirements because of the hash # in the branch name (workaround is to make my own branch).
3. It perhaps isn't as obvious to newcomers that the #api-updates-through_2015-07-28 is intended to be the "next branch".
4. Similar to the above, the API version is also upto 2016-07-06 and no longer matches the branch (which looks out of date on first inspection!)

So I think overall it would be easier to manage, more obvious, self-descriptive, accurate, etc. :+1:

Thoughts on a post-card? Also, apologies that I haven't been able contribute recently, we've been really bogged under with our own deployment issues. I'm still eager to jump back in for additional features around coupons and a few other things on my list. :-)

[kavdev]

@lskillen: I think this exact idea has been on all of our minds. I'll create a 1.0.0 branch and retarget all of the pull requests (I wasn't able to do that before).

[kavdev]

Definitely just killed the old branch before retargeting the PRs... stand by lol

[kavdev]

@lskillen: Done.

[lskillen]

Fantastic - Thanks @kavdev!