Subplot → blog → 2022 → 03 → 26 → Iteration planning: March 26th – April 9th
  1. Assessment of the iteration that has ended
  2. Repository review
    1. The subplot repository
    2. The subplot-web repository
    3. The subplot-container-images repository
  3. Discussion and decisions
    1. Recurring agenda items
    2. Reaching out for feedback
  4. New iteration
    1. Current goal (not changed this iteration)
    2. Issues for this iteration
  5. Any other business
  6. Actions
  7. Meeting participants

Assessment of the iteration that has ended

We had planned to work on the following issues for the previous iteration (Subplot milestone 46), and finished them:

We had also planned to work these issues, but failed to do so:

  • Subplot issue 221 – Command line tool has insufficient logging
    • Lars looked into this, and thinks Subplot issue 6 (Subplot should separate warnings and errors) needs to be done to sensibly improve the logging.
  • Subplot issue 262 – Subplotlib’s ScenarioContext should be able to be introspected for state
    • Daniel made some progress, but not enough to close the issue.

We carried these over to the new iteration.

Repository review

We reviewed the open issues, merge requests, and CI pipelines for all the projects in the Subplot group on gitlab.com.

The subplot repository

There were 56 open issues, of which 27 were not tagged someday-maybe. We reviewed the ones that had been changed since the previous meeting, and added any new comments to the issues.

  • Subplot issue 220 Generated Rust test programs are hard to debug
    • This was dropped from the current goal, and turned into a tracking issue.
  • Subplot issue 221 Command line tool has insufficient logging
  • Subplot issue 278 Doesn’t document that rustfmt is needed, or check that it’s available in ./check
  • Subplot issue 280 Rust scenario steps should output their full text for debugging
    • This was filed during the meeting.

There are no open merge requests.

There were open, old branches:

  • subplot-rust – we removed this during the meeting
  • docgen-cmark – we will keep this until the next goal is finished

CI pipelines are OK.

The subplot-web repository

There were no open issues, no open merge requests, no extra branches, and no CI enabled.

The subplot-container-images repository

There was one open issue.

  • subplot-container-images #2 – There is no Docker image for using Subplot
    • we’re not going to work on this until we stop making breaking changes

There were no open merge requests, no extra branches, and the latest run of CI was successful. (That’s the run that was automatically triggered yesterday.)

Discussion and decisions

Recurring agenda items

  • Subplot issue 119 – Subplot is in not in Debian unstable
    • we’re not going to work on this now
  • Subplot issue 272 – Migrate project to issue-based iteration meetings
    • we’re not going to work on this now
  • Subplot issue 273 – Perform whole-codebase review and cleanup
    • we’re not going to work on this now

Reaching out for feedback

We won’t be reaching out for feedback until goal 3 is done. We didn’t open issue for this, to avoid naming people in public.

New iteration

Current goal (not changed this iteration)

The current development goal is:

Subplot provides a set of libraries with identical capabilities in each of the supported languages. Python remains a supported language. Rust is promoted to supported-language status. Subplot will be tested with all supported languages. In addition, any quality of life improvements which can be done shall be done. This goal will be considered complete when a release of Subplot has been made with the unified language handling support complete.

This is represented as label goal::2 in the GitLab.com issue tracker.

Issues for this iteration

We collect issues for this iteration in Subplot milestone 47. We decided to not make a release.

Lars intends to work on:

Daniel intends to work on:

  • Subplot issue 262 Subplotlib’s ScenarioContext should be able to be introspected for state
  • Subplot issue 280 Rust scenario steps should output their full text for debugging

Any other business

We discussed whether Rust step functions could or should be async, but decided it would be too complicated for now.

Actions

None.

Meeting participants

  • Daniel Silverstone
  • Lars Wirzenius