Closed keathley closed 10 years ago
I think it'll be doable to release a new tag quite soon.
There have been some rather significant changes in the gem since the last release, which breaks some backwards-compability (hopefully only for the better) and should also fix the last known deadlock bug. I updated the changelog to reflect the changes: https://github.com/Burgestrand/spotify/blob/master/CHANGELOG.md#head
I have one uncomitted change left that breaks backwards-compatibility that I'd like to get into the same release bunched together with all other backwards-breaking changes, so I don't have two make two backwards-breaking releases in a short timespan. It's nearly finished, but if I determine that I can't complete it fast enough I'll make a release without it.
:+1: Let me know if there's anything I can do to help.
I appreciate it :)
With d80b92491d911c86236157612260026d9df56d9c, I believe most of the stuff I want is there. I'd just like to smoke it a little before releasing a new version, but I think I can release a new gem version this week.
'tis out: 12.6.0!
Would it be possible to release a new tag with the current changes? It's a bit confusing to try to follow the example code when the version that is installed through ruby gems is out of sync with master.
I'm happy to contribute or help.