-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
port q2-phylogeny actions to q2-iqtree2 #2
Comments
That makes sense to me. :-) |
The IQ-TREE 2 actions have been ported over to Questions / Comments: |
Deprecation notice was applied to iqtree related actions in this PR. |
Sounds good @mikerobeson! I'm meeting with the engineers on my team this week - we'll follow up with you about conda and the tests then (it might make sense to do this using new functionality that we're testing for the QIIME 2 Library). |
I'm thinking a good start for this plugin would be to move iqtree action(s) from q2-phylogeny to q2-iqtree2, and deprecate those in q2-phylogeny. We can then target an initial release of this plugin with the 2020.11 release, and remove the deprecated iqtree functionality from q2-phylogeny in the 2021.2 release.
Does that strategy make sense?
The text was updated successfully, but these errors were encountered: