Ok, let's wait for Ron to comment on whether 2.2.0 API is backwards
compatible with 2.0.0.
There have also been countless over changes/fixes between remoting 2.0
and 2.2, so all these would need to be backported to remoting 2.0.1 as well.
This would effectively be the same as renaming remoting 2.2.0 to
remoting 2.0.1... Is this the right way to go?
Dimitris Andreadis wrote:
The idea is that point releases (4.2.0, 4.2.1) must be backwards
compatible so unless we can apply those critical fixes to produce
remoting 2.0.1 instead, I don't see how we can avoid scoping messaging/esb.