[Preview] QIIME 2 2020.8 development changelog

:exclamation: Important :exclamation:

The following is an early developer preview of the changes expected in 2020.8

This post is a live-document which will be updated throughout our development cycle. Any links will in this topic will be broken until the release is officially published. When we are ready for release, we’ll copy this changelog and create a new post in the Announcements category.

Important Developer Information

Dates (please keep an :eye: on this post, these :calendar: might change):

  • PRs must be submitted by: August 10, 2020
  • PRs must be merged by: August 17, 2020
  • Repo Freeze and Package Building: August 20, 2020
  • Release Day: August 24, 2020

Developer Project Board: https://github.com/orgs/qiime2/projects/20

:exclamation: BREAKING CHANGES

Please update scripts, workflows, etc. as appropriate. Stuck? Reach out here on the forum for help. Want to test this prior to the next release of QIIME 2? Check on the “development environment” instructions here:


Here’s the highlights of the release:

  • QIIME 2 Framework

    • @Oddant1 fixed a bug preventing the usage of TypeMatch on methods with a List or Set type parameter.
    • @Oddant1 Changed an error message so it points out a common mistake seen when importing metadata
  • docs

    • placeholder
  • q2cli

    • placeholder
  • q2-plugin

    • @Oddant1 pinned matplotlib and matplotlib-base to <3.3
  • q2-plugin

    • @Oddant1 cleaned up new linting errors introduced by the latest flake8
    • @Oddant1 Temporarily changed precision of a test
  • q2-plugin

    • @Oddant1 Removed the previously deprecated q_score_joined method

Hey all - the 2020.8 development cycle is quite a bit shorter than normal (since 2020.6 wound up running a bit long). Anyway, we are planning on shipping in the first half of August, so today(ish) is the cutoff for PR submissions. If you have something you’re working on, but it isn’t yet on our radar please ping us here so that we can discuss a plan for ensuring your work catches the 2020.8 train, so to speak.

Thanks! :t_rex:

Just a quick follow-up, we had a change in plans that has allowed us to push the release out a little bit, which is great news, it’ll allow us to get a few more features etc pushed in. Please see above for a revised schedule.