Tracking issue for 0.5

[Geobert]

Once the async work has landed, what are the next steps in order to stabilize 0.5?

Known interface deficiencies:

• Allow exact url in registrar, enabling faster literal redirect_uri comparison. #68
• Interface of Solicitor is not evolvable #108

[Geobert]

Now that async is merged, what do we need to have a 0.5 published on crates.io?

[HeroicKatora]

I'll cut another pre-release tonight and when I had time to ensure that I didn't overlook any interface changes that are compatibility risks then a full release of 0.5 and release notes etc. (this weekend, maybe).

[Geobert]

Thank you, I though there were more work planned to have a 0.5 live ready :)

[HeroicKatora]

There's probably one necessary more small change after the pre-release: Encapsulating the parameter to the solicitor to ensure forward compatibility with introducing some additional state information in a future minor release. (Solving #42 in the long run)

[Geobert]

Oh yes this issue, I have implemented a work around but I'm just realizing it won't work: I stored state in a HashMap with client_id as the key. Which will fails on multi requests from the same client…

[Geobert]

Congratulation for 0.5! Didn't notice it was out 5 days ago already :D

[HeroicKatora]

Thanks, it literally wouldn't have been possible without You.

[Geobert]

Thanks, it literally wouldn't have been possible without You.

You're welcome! We needed it and that's how Open Source works ;)