summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2020-11-07 19:16:53 +0200
committerLars Wirzenius <liw@liw.fi>2020-11-07 19:16:53 +0200
commit81404ae59c26ce7f95322493da35e9984ac44c09 (patch)
tree9d59efc65036524f3cceef9fd860e15a223b71b1
parentdc0a3cb2a8cd7cea57e361c7fdd7bc2c00754a26 (diff)
downloadsubplot.liw.fi-81404ae59c26ce7f95322493da35e9984ac44c09.tar.gz
Publish log entry
-rw-r--r--blog/2020/11/07/iteration_planning_meeting_november_7th.mdwn82
1 files changed, 82 insertions, 0 deletions
diff --git a/blog/2020/11/07/iteration_planning_meeting_november_7th.mdwn b/blog/2020/11/07/iteration_planning_meeting_november_7th.mdwn
new file mode 100644
index 0000000..7ae369e
--- /dev/null
+++ b/blog/2020/11/07/iteration_planning_meeting_november_7th.mdwn
@@ -0,0 +1,82 @@
+[[!meta title="Iteration planning meeting: November 7th"]]
+[[!tag meeting]]
+[[!meta date="2020-11-07 15:40"]]
+
+
+# What has happened?
+
+We met with Lars's co-worker Ahmon earlier this week. Lars had taken
+notes of the chat, and we discussed them at this meeting. We filed
+[[!issue 116]]. We agreed that we need a few putative scenarios for
+"assuming" scenarios, and that we need to experiment with various
+approaches ([[!issue 20]]).
+
+We also discussed a hypothetical USING keyword, but didn't settle on
+an approach on that either, yet, except we think it and "ASSUMING"
+should use the same approach. We might add a new block type "`meta`"
+where ASSUMING and USING and other meta data about scenarios would go.
+
+This all needs further discussion.
+
+We finished [[!milestone 16]], completing [[!issue 93]] and [[!issue
+104]]. We discussed the issues that weren't completed:
+
+* [[!issue 96]]: didn't know about error contexts
+* [[!issue 100]]: script, but needs more work
+* [[!issue 108]]: problems running generated test programs
+* [[!issue 111]]: cronjob
+
+No progress was made on the following:
+[[!issue 20]],
+[[!issue 74]],
+[[!issue 102]],
+[[!issue 107]].
+
+We closed [[!milestone 16]] and created [[!milestone 17]], with issues
+
+* [[!issue 20]]: continue discussion about ASSUMING, create scenarios
+ that need it in different way.
+* [[!issue 74]]: Lars to add support for user to specify environment
+ variables when running the generated test program.
+* [[!issue 96]]: Lars to investigate contexts in anyhow, and using
+ that to provide information on where error happens.
+* [[!issue 100]]: Lars to update the MR based on feedback, then ping
+ Daniel.
+* [[!issue 101]]: Daniel to create a single-file template for Rust
+ test programs. Doesn't need to be very complete, or even have
+ contexts, but should have something so we get this moving.
+* [[!issue 102]]: Carried over.
+* [[!issue 107]]: Carried over.
+* [[!issue 108]]: Carried over. Blocked on [[!issue 115]].
+* [[!issue 111]]: Lars to set up a cron job to mirror from gitlab to
+ git.liw.fi sufficiently frequently.
+* [[!issue 114]]: Lars to add a pandoc-citeproc dependency.
+* [[!issue 115]]: Lars to find out what breaks and why, and to submit
+ a fix if possible.
+* [[!issue 116]]: Daniel to update documentation to explain the
+ Gherkin-like language in a clearer way.
+
+
+
+# Review
+
+Outstanding MRs: [[!mr 93]]: Daniel has a suggestion, Lars will
+implement.
+
+
+# Discussion
+
+Others using Subplot: we need to improve documentation, and fix
+[[!issue 116]] at least. We could do a trial where we watch a willing
+volunteer use Subplot: a shared screen, screen, probably recorded for
+our use (but not made public), using the Python template and Context,
+to implement some subplot that's realistic, but not tiresome. [[!issue
+117]], [[!issue 118]].
+
+Getting Subplot into Debian: Initial Debian freeze happening early
+January. We are not ready to support the version of Subplot we will
+have then for years. We are, however, about ready for Subplot to be in
+Debian unstable. [[!issue 119]]
+
+Daniel and Lars are both happy to support and mentor Dan to work on
+Subplot and help him maintain momentum on contributing.