<p dir="ltr">Hi Eric.</p>
<p dir="ltr">Thanks for looking at this. We have a few versioning options:</p>
<p dir="ltr">1. Keep versioning in sync with the main distribution<br>
2. Keep the current versioning scheme (not milestone based, generally bumped on major feature inclusion or sufficient number of fixes)<br>
3. Version based on hitting milestones (containing planned features)</p>
<p dir="ltr">One of the benefits of approach 1 would be that compatibility between the CLI and the core might be clearer to a user if the versions match. One of its potential disadvantages would be in coupling the two, the CLI might lag behind core if a major change happens.</p>
<p dir="ltr">As far as distribution is concerned, inclusion in the community ZIP files seems like a sensible option. Do you have any suggestions on folder structure? It's one (uber-) JAR and the bat/sh scripts right now.</p>
<p dir="ltr">All the best,</p>
<p dir="ltr">Pete</p>
<br><div class="gmail_quote"><div dir="ltr">On Mon, 29 Feb 2016, 16:18 Eric Wittmann, <<a href="mailto:eric.wittmann@redhat.com">eric.wittmann@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Pete.<br>
<br>
I was just doing a community release of 1.2.2.Final today and was<br>
thinking about the CLI. Do you have any thoughts on how to<br>
version/release the CLI whenever we do a community release?<br>
<br>
Also, any thoughts on whether/how we should include the CLI in the<br>
community distributions (zip files)?<br>
<br>
-Eric<br>
<br>
PS: @apiman-dev subscribers - feel free to offer thoughts/opinions! :)<br>
</blockquote></div>