Releasing a new version

[alexanderekman]

Hi!

We're using this project and highly appreciate it being frequently updated as new devices as they get released. We're currently installing it using Cocoapods and by specifying the version number, but we just noticed that there had been a bunch of new commits with new devices which hasn't yet been made into a proper release. Is this intentional, or has that step just been forgotten? Would you recommend that we switch to specifying a commit instead of version number (and by doing so trust that the master branch is always "stable")?

Thank you for keeping this repo up to date. :)

[cpsauer]

Hey Alexander! Yes, totally hear you. I don't have cocapods permissions just yet so I can't yet fix--under discussion. Could I redirect you over to #151 (also about this) for more discussion?

(I consume the library a different way but offhand might advocate for that we just "live at head" if there's a way to make that fit naturally and easily for folks coming from Xcode. That is, main represents the latest-and-greatest state and people grab the latest by commit (reproducible) or branch (maybe easier). Benefit is that it equips everyone to go direct and easily hack on the project and contribute. But if it doesn't work smoothly from Xcode then we obviously shouldn't do that. Would love your opinion!)

Thanks for writing in--and we'd love your help getting to the right solution here.

[Shubhashree97]

Hi Team, do we have any update on 7.3 Release?
#151 ,