as per the synse v3 docs, all synse components should have their major version be the platform version they support.. so for synse v3, that would be 3.X.X
synse-cli currently has a 3.0.0 release which is compatible with synse v2. this issue is to do some cleanup with the project releases. I think generally this is a big no-no, but since nobody uses this tool right now, I'm not uncomfortable with this since it wont break things for anyone.
the steps for this would be to checkout at the commit which the current 3.0.0 tag, create a new tag (e.g. 2.1.0), push that tag, cut a release for 2.1.0, delete the 3.0.0 release, delete the 3.0.0 tag.
Then, when the v3 work is ready for prime time, a new 3.0.0 tag will be pushed, so the CLI's versioning will be in sync with the rest of the synse platform.
as per the synse v3 docs, all synse components should have their major version be the platform version they support.. so for synse v3, that would be 3.X.X
synse-cli currently has a 3.0.0 release which is compatible with synse v2. this issue is to do some cleanup with the project releases. I think generally this is a big no-no, but since nobody uses this tool right now, I'm not uncomfortable with this since it wont break things for anyone.
the steps for this would be to checkout at the commit which the current 3.0.0 tag, create a new tag (e.g. 2.1.0), push that tag, cut a release for 2.1.0, delete the 3.0.0 release, delete the 3.0.0 tag.
Then, when the v3 work is ready for prime time, a new 3.0.0 tag will be pushed, so the CLI's versioning will be in sync with the rest of the synse platform.