re-release as version 0.2.11

[bhalsey]

Issue:

FusionAuth/fusionauth-issues#2498

Problem:

Updating applications to use latest java-http version of 0.3.0 would require all their dependencies (such as prime-mvc) to use version 0.3 of java-http. Recent TLS updates of java-http are backwards compatible with previous versions, so technically, the current version should be 0.2.11. (Version 0.*.* rules of Semver.)

Solution:

Re-release java-http with a minor version change to 0.2.11

[robotdan]

This will work. Another option is to checkout 0.3.0 and create a maintenance branch off of that - and then release from there. The convention for this branch name would be 0.3.0.maintenance.

If we do this (which is fine) it just means that we need to make another commit after we release this to go back to 0.3.0.

[bhalsey]

If we do this (which is fine) it just means that we need to make another commit after we release this to go back to 0.3.0

Ack. Will do this.