Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1.5
-
Epic Link:
Description
Describe (at a high level) how the continuous, automated release of Early Access IGB will work.
Requirements:
- It should be possible for users to tell the difference between Early Access IGB and the released version.
- It would be nice if users can tell the difference between different Early Access IGB releases. For example, can we include commit hash in the file name or ???
- It would be nice if Early Access IGB would automatically update using the Install4J mechanism, and also that it would not over-write released IGB if already installed.
Early Access IGB, from the users' perspective, should seem like a separate, cutting edge version of IGB.
Once the design is made, create issues capturing tasks required for implementation.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-1525 [ 17611 ] |
| Rank | Ranked higher |
| Description |
Describe (at a high level) how the continuous, automated release of Early Access IGB will work.
Requirements: * It should be possible for users to tell the difference between Early Access IGB and the released version. * It would be nice if users can tell the difference between different Early Access IGB releases. For example, can we include commit hash in the file name or ??? * It would be nice if Early Access IGB would automatically update using the Install4J mechanism, and also that it would not over-write released IGB if already installed. Early Access IGB, from the users' perspective, should seem like a separate, cutting edge version of IGB. |
Describe (at a high level) how the continuous, automated release of Early Access IGB will work.
Requirements: * It should be possible for users to tell the difference between Early Access IGB and the released version. * It would be nice if users can tell the difference between different Early Access IGB releases. For example, can we include commit hash in the file name or ??? * It would be nice if Early Access IGB would automatically update using the Install4J mechanism, and also that it would not over-write released IGB if already installed. Early Access IGB, from the users' perspective, should seem like a separate, cutting edge version of IGB. Once the design is made, create issues capturing tasks required for implementation. |
| Sprint | Spring 2019 Sprint 2 [ 60 ] |
| Rank | Ranked higher |
| Sprint | Spring 2019 Sprint 2 [ 60 ] |
| Rank | Ranked lower |
| Summary | Describe workflow for releasing Early Access IGB | Design workflow for releasing Early Access IGB |
| Resolution | Done [ 10000 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | Loraine Lab Workflow [ 18246 ] | Fall 2019 Workflow Update [ 20019 ] |
| Workflow | Fall 2019 Workflow Update [ 20019 ] | Revised Fall 2019 Workflow Update [ 22146 ] |