Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.5
-
Epic Link:
-
Sprint:Summer 7, Fall 1, Fall 2, Fall 3
Description
Investigate the available options to create a release branch without the Ensembl code in it, either revert the commits or drop them, find out which would be the best suitable option and then create the release branch.
Attachments
Issue Links
- blocks
-
IGBF-3881 Add samtools filter by and color by options for CR and CB tags
-
- Closed
-
Activity
After the discussion with Ann Loraine and Nowlan Freese, we have decided on the below approach to create a release branch:
- First to remove the Ensembl code, we have decided to use the revert option as it keeps the git commit history clean and it allows us to revert the revert to get the original code.
- To do this, we will be creating a release branch first from the updated main branch and then we will remove the Ensembl code, this way main will have the Ensembl code and the release branch won't and any further bugfixes to the release branch should be merged to main as well (i.e., two PRs for each bugfix).
This will be done once all the tickets related to UCSC and the Google Analytics are finished and merged into the main. (IGBF-3853, IGBF-3813 and IGBF-3865)
Downloaded IGB-macos-universal-10.1.0.dmg from Loraine Lab Bitbucket (date: 2024-10-15) and installed on Mac.
Ensembl does not appear as a data provider in the Data Sources window.
Closing ticket.