diff options
author | 2013-11-21 18:05:46 -0400 | |
---|---|---|
committer | 2013-11-21 18:05:46 -0400 | |
commit | 2bf5da36810e84808340bf417463e2a8ac945be5 (patch) | |
tree | 9ff1ea1471f86f772fbc4e0db06b8c90a117efc4 /doc | |
parent | 40c91a0d45a875b8ef58c42a38fb29f4a608b425 (diff) |
devblog
Diffstat (limited to 'doc')
-rw-r--r-- | doc/devblog/day_62__upgrade_alerts.mdwn | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/devblog/day_62__upgrade_alerts.mdwn b/doc/devblog/day_62__upgrade_alerts.mdwn new file mode 100644 index 000000000..0b3078563 --- /dev/null +++ b/doc/devblog/day_62__upgrade_alerts.mdwn @@ -0,0 +1,22 @@ +Still working on the git repair code. Improved the test suite, which found +some more bugs, and so I've been running tests all day and occasionally +going and fixing a bug in the repair code. The hardest part of repairing a +git repo has turned out to be reliably determining which objects in it are +broken. Bugs in git don't help (but the git devs are going to fix the one I +reported). + +But the interesting new thing today is that I added some upgrade alert code +to the webapp. Ideally everyone would get git-annex and other software as +part of an OS distribution, which would include its own upgrade system -- +But the [survey](http://git-annex-survey.branchable.com/polls/2013/how_installed/) +tells me that a quarter of installs are from the prebuilt binaries I +distribute. + +So, those builds are going to be built with knowledge of an upgrade url, +and will periodically download a small info file (over https) to see if a +newer version is available, and show an alert. + +I think all that's working, though I have not yet put the info files in +place and tested it. The actual upgrade process will be a manual +download and reinstall, to start with, and then perhaps I'll automate it +further, depending on how hard that is on the different platforms. |