summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-04-23 18:23:58 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-04-23 18:23:58 -0400
commit45b7dc1279e42e28b9e7579cda6bc36de4d420c9 (patch)
tree50bea406494c6c2c6ba75e834a3e84fc94685497
parent697b510c9343a1fa5013bb307a5ce5e38c46e46e (diff)
blog for the day
-rw-r--r--doc/design/assistant/blog/day_246__bug_treadmill.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_246__bug_treadmill.mdwn b/doc/design/assistant/blog/day_246__bug_treadmill.mdwn
new file mode 100644
index 000000000..36ee0c617
--- /dev/null
+++ b/doc/design/assistant/blog/day_246__bug_treadmill.mdwn
@@ -0,0 +1,18 @@
+There seem to be a steady state of enough bug reports coming in that I can
+work on them whenever I'm not working on anything else. As I did all day
+today.
+
+This doesn't bother me if the bug reports are of real bugs that I can
+reproduce and fix, but I'm spending a lot of time currently following up to
+messages and asking simple questions like "what version number" and "can I
+please see the whole log file". And just trying to guess what a vague
+problem report means and read people's minds to get to a definite bug
+with a test case that I can then fix.
+
+I've noticed the overall quality of bug reports nosedive over the past
+several months. My guess is this means that git-annex has found a less
+technical audience. I need to find something to do about this.
+
+With that whining out of the way ...
+I fixed a pretty ugly bug on FAT/Android today, and
+I am 100% caught up on messages right now!