[INTPAK-167] Document what to do in Int/Pack when new release drops Created: 30/Apr/18 Updated: 21/Jun/18 Resolved: 21/Jun/18 |
|
| Status: | Closed |
| Project: | integration-packaging |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Daniel Farrell | Assignee: | Daniel Farrell |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Most Int/Pack packages are built using the CD pipeline, which of course doesn't require any intervention from humans, but proper releases do require someone to go through a manual process. Document that process vs it just being in my head. Document what I do in |
| Comments |
| Comment by Daniel Farrell [ 20/Jun/18 ] |
|
I think this will be done, at least to an acceptable level of quality, once 71650 is merged. |