Preparing a 2.0 Release

[mmauksch]

As there is already a request to update the maven artifacts ( #361 ) I would also support doing a new release on maven central.

One caveat though: the extensive 2.0 implementation provided by @robert-s-ubi might lead to some compatibility issue if released on the 1.x Version.

Therefore if would like to discuss the option to release the current code with updates and the 2.0 implementation as version 2.0. to maven central. This way we can give people the option to use the new features without the risk of breaking their stuff.

Any ideas @robert-s-ubi @TVolden

[robert-s-ubi]

If time permits, I would propose looking into these things before a new release:

1. Issue I think the validation for retries/retryInterval (updatefirmware/getdiagnostics) may be incorrect #362 seems to be a real bug, but would be an easy fix.
2. PR Cleanup after sending to avoid memory leak #334 looks like it is fixing a serious issue, but I have not found the time to dig into it, since this is code I never touched and don't understand.
3. OCPP 2.0.1 actually requires WebSocket compression support (though hardly anyone is aware of this). I've already helped the Java-WebSocket project get this working in their 1.6.0 release, and prepared a commit for this library which bumps the dependency and adds the support. I need to find the time to polish & submit this.