Thinking about releasing 2.1.0

[timmolter]

From a general perspective, there are no critical API refactors currently taking place, and it's due time for a release.

Does anyone have any critical fixes they want to squeeze in beforehand? Any other comments?

[sutra]

But we should release rescu first, as we are depending on si.mazi.rescu.ValueFactory which is introduced in rescu-1.7.0-SNAPSHOT.

[rafalkrupinski]

ValueFactory needs one critical change, the object that is used as a monitor isn't shared between exchange services. Ill look into in the evening.

[timmolter]

@rafalkrupinski Thanks. I'll ask @mmazi to release ResCU afterwards then in preparation for XChange 2.1.0

[rafalkrupinski]

https://github.com/rafalkrupinski/XChange/tree/sync-nonce is waiting for mmazi/rescu#45 to be merged

[timmolter]

I think once issue #647 is resolved, I'll do the release.

[rafalkrupinski]

@timmolter Are there any outstanding issues blocking the release?

[timmolter]

No, unless you are aware of one. I asked @mmazi for a rescu release.