Dj-stripe: v1.0.0 usable?

Created on 22 Nov 2016  路  7Comments  路  Source: dj-stripe/dj-stripe

Hi, sorry for jamming up issues, I'll delete this after...

But is v1.0.0 usable in production? Or are some things broken?

Looking around I couldn't get a clear picture of where development is at,

What features are still in development? I would like to contribute so it would be good to know where to direct my efforts...

Thanks.

question

Most helpful comment

Hi @allthetime, @lskillen is right -- 1.0.0 is stable and we only have a few more things to button up. Development has slowed down quite a bit as I'm low on free time at the moment, but we're getting there.

Definitely check out #307. Theres a full changelog along with a list of what still needs to be done.

@lskillen: Documentation is almost there. @aleccool213 has been working hard on it and I have about 15 PRs to sift through. Also, I believe the last API check was back in March, so we are a bit behind on parity.

All 7 comments

@allthetime: Don't take this as a guarantee (DYOR) but I suppose it is a reasonable testimonial we have 1.0.0 in production (albeit "public alpha release") without any issues. If you're looking to utilise the latest version of the Stripe API then the 1.0.0 branch is the only way forward really. As for what was left to do for release, I also asked this in #307 , but other than improving object synchronisation and plan initiation, it seems the major task left is updating documentation. Our BDFL/maintainer @kavdev can confirm. :-)

HTH!

Hi @allthetime, @lskillen is right -- 1.0.0 is stable and we only have a few more things to button up. Development has slowed down quite a bit as I'm low on free time at the moment, but we're getting there.

Definitely check out #307. Theres a full changelog along with a list of what still needs to be done.

@lskillen: Documentation is almost there. @aleccool213 has been working hard on it and I have about 15 PRs to sift through. Also, I believe the last API check was back in March, so we are a bit behind on parity.

@kavdev Aye, been keeping tabs - definitely on the right track! If it's worth anything I've been testing on the latest version of the Stripe API (and continue to update where possible) without issues. Changes are primarily to do with retrieval so haven't affect model structure.

@lskillen: Good to hear!

What about now?

@rigothedev Same policy, but 1.0.0 is being used in production by many of us and seems quite stable.

@rigothedev we've been using this for half a year now without issue to manage multiple recurring subscriptions

Was this page helpful?
0 / 5 - 0 ratings

Related issues

isaac-jordan picture isaac-jordan  路  4Comments

skjortan23 picture skjortan23  路  3Comments

radyz picture radyz  路  6Comments

mattstrayer picture mattstrayer  路  5Comments

PabloCastellano picture PabloCastellano  路  3Comments