[TIMOB-13835] Code Processor: tag the source with <version> when publishing a version to global npm
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-05-17T00:03:42.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2013 Sprint 10 JS, 2013 Sprint 10, Release 3.2.0 |
| Components | Code Processor |
| Labels | n/a |
| Reporter | Michael Xia |
| Assignee | Praveen Innamuri |
| Created | 2013-05-13T04:07:20.000+0000 |
| Updated | 2017-03-09T18:30:40.000+0000 |
Description
When a new version of code processor is released, e.g. 3.1.1, the corresponding source code should be tagged with 3.1.1. This is to help Studio implemnt TISTUD-4632.
We are going to leave the tagged versions in the format "X.Y.Z".
Re-opening as this request is for tagging the git source in addition to tagging the npm package.
Tagged the 1.0.0 release of the code processor (on the 1_0_X branch). Future versions will be tagged on release.
Closing ticket as fixed.