The RPC API compatibility is going to be absolutely destroyed with the RingCT RPC default update and adding in all the new fields to support more RingCT field information. This must require a major version update to reflect this.

v2 doesn't specifically indicate a hard fork of the protocol.