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
83
84
85
86
87
88
89
90
91
92
93
94
95
|
[[!meta title="Iteration planning: November 21—December 5"]]
[[!meta date="Sun, 21 Nov 2021 10:05:03 +0200"]]
[[!tag meeting]]
[[!toc levels=2]]
# Assessment of the iteration that has ended
[previous iteration]: /blog/2021/11/07/planning
The goal of the [previous iteration][] was:
> The goal of this iteration is to improve the benchmark and try to
> make Obnam faster. Also, we need to re-start Obnam development.
This was completed. There is a [[benchmark results|/benchmarks]] page
on the web site. We made release 0.5.0.
# Discussion
## Minimum supported Rust version
The discussion about minimum supported Rust version for Obnam, in
[[!issue 137]], needs to be resolved. Lars suggests 1.56.0, which is
currently what is in the Debian "testing" distribution, and slated to
be in the next Debian release. Opinions on this are welcome,
especially form a non-Debian point of view.
## Policy for `cargo deny`
The Obnam release process now uses `cargo deny` to check for
vulnerabilities in dependencies (both direct and indirect), for
license incompatibilities, and more. The current policy is very
permissive. Lars made the decision to start with a lax policy, and
tighten it up over time to avoid suddenly creating a lot of
work for the Obnam project.
In [[!issue 157]] there is a discussion of how the policy should be
tightened. Feedback there most welcome.
# Goals
## Goal for 1.0 (not changed this iteration)
The goal for version 1.0 is for Obnam to be an utterly boring backup
solution for Linux command line users. It should just work, be
performant, secure, and well-documented.
It is not a goal for version 1.0 to have been ported to other
operating systems, but if there are volunteers to do that, and to
commit to supporting their port, ports will be welcome.
Other user interfaces is likely to happen only after 1.0.
The server component will support multiple clients in a way that
doesn’t let them see each other’s data. It is not a goal for clients
to be able to share data, even if the clients trust each other.
## Goal for the next few iterations (not changed for this iteration)
The goal for next few iterations is to have Obnam be performant. This
will include, at least, making the client use more concurrency so that
it can use more CPU cores to compute checksums for de-duplication.
## Goal for this iteration (new for this iteration)
The goal of this iteration is to get a better picture of where the
performance bottlenecks currently are.
# Commitments for this iteration
We collect issues for this iteration in [[!milestone 11]].
Lars intends to work on the following issues for this iteration:
* [[!issue 132]] -- _A non-existent backup root should be treated as
an error, not a warning_
- 1h
* [[!issue 147]] -- _obnam.md could do with an easier way to set for a
scenario_
- 1h
* [[!issue 158]] -- _Lacks benchmark of incremental backup of large
number of unchanged files_
- 1h
* [[!issue 159]] -- _Lacks a baseline benchmark result with release
0.4.0_
- 1h
* [[!issue 160]] -- _Needs a release with changes after 0.5.0_
- 1h
That's a total of about 5 hours, rough estimate, for Lars.
# Meeting participants
* Lars Wirzenius
|
