[TIMOB-13910] CLI: node-appc needs to follow the major.minor.point numbering scheme like other projects
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2014-01-17T00:24:57.000+0000 |
| Affected Version/s | Release 3.1.0 |
| Fix Version/s | n/a |
| Components | CLI |
| Labels | n/a |
| Reporter | Bryan Hughes |
| Assignee | Chris Barber |
| Created | 2013-05-17T22:20:36.000+0000 |
| Updated | 2017-03-20T16:48:07.000+0000 |
Description
The current versioning scheme for node-appc doesn't allow for multi-branch development like the other products do (e.g. there's no way to work on 3.2.0 and 3.1.1 at the same time). We need to bump to version 1.0.0 and increment the minor version to coincide with the SDK minor version increases.
Note: all other projects that depend on node-appc will need to update their package.json dependencies to match.
I don't think node-appc will be bumped to 1.0 for TiSDK 3.2. I don't think we need multi-branch dev unless there is something we change in node-appc that breaks backwards compatibility. If anything, node-appc might see a 0.2 for 3.2.
I'm marking this as invalid since we now have 3_1_X and 3_2_X branches and things seem to be working smoothly.
Closing ticket as invalid.