Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1530

Design workflow for releasing Early Access IGB

        Details

        • Type: Task
        • Status: Closed (View Workflow)
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: None
        • Fix Version/s: None
        • Labels:
          None

          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

              Ascending order - Click to sort in descending order
              ann.loraine Ann Loraine created issue -
              ann.loraine Ann Loraine made changes -
              Field Original Value New Value
              Epic Link IGBF-1525 [ 17611 ]
              ann.loraine Ann Loraine made changes -
              Rank Ranked higher
              ann.loraine Ann Loraine made changes -
              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.
              ann.loraine Ann Loraine made changes -
              Sprint Spring 2019 Sprint 2 [ 60 ]
              ann.loraine Ann Loraine made changes -
              Rank Ranked higher
              ann.loraine Ann Loraine made changes -
              Sprint Spring 2019 Sprint 2 [ 60 ]
              ann.loraine Ann Loraine made changes -
              Rank Ranked lower
              ann.loraine Ann Loraine made changes -
              Summary Describe workflow for releasing Early Access IGB Design workflow for releasing Early Access IGB
              Hide
              Permalink
              ann.loraine Ann Loraine added a comment -

              Update:

              • Would like to do this every two weeks at the end of each sprint, but isn't practical at the moment.
              • Bioviz site contains some simple scripts that can be used to do an early access release manually.
              • Noor Zahara has added git commit information to About IGB screen. This ensures a user can easily determine which version of IGB is being run.
              Show
              ann.loraine Ann Loraine added a comment - Update: Would like to do this every two weeks at the end of each sprint, but isn't practical at the moment. Bioviz site contains some simple scripts that can be used to do an early access release manually. Noor Zahara has added git commit information to About IGB screen. This ensures a user can easily determine which version of IGB is being run.
              ann.loraine Ann Loraine made changes -
              Resolution Done [ 10000 ]
              Status Open [ 1 ] Closed [ 6 ]
              ann.loraine Ann Loraine made changes -
              Workflow Loraine Lab Workflow [ 18246 ] Fall 2019 Workflow Update [ 20019 ]
              ann.loraine Ann Loraine made changes -
              Workflow Fall 2019 Workflow Update [ 20019 ] Revised Fall 2019 Workflow Update [ 22146 ]

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  ann.loraine Ann Loraine
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: