QIIME 2 Weekly Developer Meeting: 2017.03.17

This is the thread for the weekly developer discussion meeting on 2017.03.17.

Meeting date/time: 2017.03.17, 12pm-1pm MST (-0700 UTC)

Planned Agenda

Status Updates (1-2 min per person)

  • Caporaso Lab
  • Other attendees

Guided discussion (remainder of scheduled meeting time)

  • This list to be updated prior to the meeting to reflect the questions/discussion points proposed in this forum thread

To help us make the best use of everyone’s time please post any discussion topics to this thread before the developer meeting. This will help us identify and prepare for any questions/topics ahead of the call. Topics or questions of discussion are open to anyone, developers or users, but we ask that these discussion points be limited to thematic QIIME 2 questions (e.g. feature proposal, plugin idea, etc.) — we will not be able to provide technical support during these calls.

The developer meeting will be recorded and posted to YouTube, we will update this post with the streaming video link shortly before the meeting.

YouTube Link: TBD

If there are no discussion topics posted by 2017.03.16, 4pm MST (-0700 UTC), we will announce a meeting cancellation and share our status updates on this thread.

We are canceling tomorrow’s dev meeting because there haven’t been any agenda items / discussion points added to this topic. We will individually follow up here with updates on our end.

There will be a new forum post requesting agenda items for next week’s meeting available shortly.

1 Like

Updates for @ebolyen, @thermokarst, and myself:

We have been focusing on setting up a continuous integration / continuous deployment system (CI/CD) for automating releases, integration testing, doc builds, etc. This week we’ve been working on building, testing, and installing QIIME 2 conda packages using Travis-CI, and will transition some of those tasks to a Concourse-based CI/CD system soon.

The next QIIME 2 release, currently scheduled for late March or early April, won’t contain very many user-facing changes. This release is mainly to test out release automation using the CI/CD system. Once the CI/CD system (and associated release) is live, it will be much easier to cut releases and get important bug fixes, features, etc. to our users. To that end, we will most likely have at least one more release before the 2017.6 release that we’ve mentioned in the dev meetings (we’re planning some larger changes for the 2017.6 release, such as pipeline support).

1 Like