1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
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.
|
