From 4b9cd86c335b187fee34798c184c71c757417e47 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Sat, 31 Jul 2021 13:10:35 +0300 Subject: add minutes of planning meeting minutes for today Sponsored-by: author --- blog/2021/07/30/meeting.mdwn | 117 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 117 insertions(+) create mode 100644 blog/2021/07/30/meeting.mdwn diff --git a/blog/2021/07/30/meeting.mdwn b/blog/2021/07/30/meeting.mdwn new file mode 100644 index 0000000..4a90f6c --- /dev/null +++ b/blog/2021/07/30/meeting.mdwn @@ -0,0 +1,117 @@ +[[!meta title="Iteration planning: July 31"]] +[[!tag meeting]] +[[!meta date="2021-07-31 18:00 +0300"]] + +[[!toc levels=2]] + +# Review of actions from last meeting + +- There were no actions. + +# Review of the iteration that has ended + +[[!milestone 32]] has the following issues still open: + +* [[!issue 198]] -- Unify language handling for multi-impl-lang test suites +* [[!issue 202]] -- Test suite assumes cargo puts binaries in target/debug +* [[!issue 205]] -- Newer pandoc does not have `--filter pandoc-citeproc` but rather `--citeproc` +* [[!issue 206]] -- CI sometimes fails in a flaky way +* [[!issue 207]] -- Release process is too manual, CI build of release .deb changes files +* [[!issue 208]] -- Change release process to be automatable + +Reminder: It's A-OK for us to not complete all the work we plan for an +iteration. This is a project for fun, and if other things happen (such +as work or life) that preempt Subplot work, then Subplot work gets +postponed. No excuses need be presented. + +We had MRs from an outside developer and had trouble merging them, as +they hadn't enabled CI on their fork of Subplot. After they did, it +went smoothly. + +# Review of the repositories + +There's two in-progress MRs in the `subplot` repository + +* [[!mr 193]] -- docs: update release process: more explicit +* [[!mr 194]] -- test: sleep for a second before running docgen + +These need review in the new iteration. + +No other in-progress MRs in any of the repositories. No spare branches +in the container images or web repositories. The "Rust for subplot.md" +branch remains in the subplot repository. Pipelines all looked good. + +We triggered the pipeline to build new container images so that we +have a fresher image. + +# Current goal + +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. + +# Issue review + +We reviewed all issues changed since the previous meeting.. + +- [[!issue 198]] -- Unify language handling for multi-impl-lang test suites + - work has begun but there is no changes to review yet + - Daniel thinks the design in the issue should more or less work +- [[!issue 202]] -- Test suite assumes cargo puts binaries in + target/debug + - we'll be looking at `cargo metadata` + - re-assigned to Lars who need to fix this for Obnam as well +- [[!issue 205]] -- Newer pandoc does not have `--filter + pandoc-citeproc` but rather `--citeproc` + - removed Daniel as assignee +- [[!issue 206]] -- CI sometimes fails in a flaky way + - Lars has been doing work on this, and it may be fixed + - Daniel merged [[!mr 194]] during the meeting + - issue closed during meeting +- [[!issue 207]] -- Release process is too manual, CI build of release + .deb changes files + - Lars has an MR to update `RELEASE.md` + - we also need to make a release with the new process +- [[!issue 208]] -- Change release process to be automatable +- [[!issue 210]] -- ./check doesn't allow running only one scenario in + subplot.md + - is it worth making `./check` more complicated to allow this? + - maybe supporting `cargo xtask` would make more sense? + - labeled "someday/maybe" +- [[!issue 211]] -- Doesn't explain acceptance criteria, acceptance + tests, or workflow + - we agree this is worthwhile + - Daniel added a comment with suggested wording improvement + - assigned to Lars + +# Plan for next iteration + +We opened [[!milestone 33]] to cover this iteration. It has XXX +issues: + +- [[!issue 198]] -- Unify language handling for multi-impl-lang test suites +- [[!issue 202]] -- Test suite assumes cargo puts binaries in target/debug +- [[!issue 207]] -- Release process is too manual, CI build of release .deb changes files +- [[!issue 208]] -- Change release process to be automatable +- [[!issue 211]] -- Doesn't explain acceptance criteria, acceptance + tests, or workflow + +And an extra in case there's time: + +- [[!issue 205]] -- Newer pandoc does not have `--filter pandoc-citeproc` but rather `--citeproc` + +In addition, we decided to decide on Wednesday the 4th whether we want to +make a release using the new release process. We will create an issue +for the release then. + +# Other business + +No notes. + +# Actions + +* Daniel: Create a merge request template that asks for CI to be set + up on the source repository before creating the MR. -- cgit v1.2.1