From c844d6dd5442dd5c15188ec74c122b7984be7c7a Mon Sep 17 00:00:00 2001 From: pigmonkey Date: Thu, 7 Nov 2019 18:38:29 +0000 Subject: [PATCH] Added a comment: Consider deprecation warnings in the web app --- ...comment_1_7326382d8ff23873c2fe0d6acd984454._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/devblog/day_607__v8_is_done/comment_1_7326382d8ff23873c2fe0d6acd984454._comment diff --git a/doc/devblog/day_607__v8_is_done/comment_1_7326382d8ff23873c2fe0d6acd984454._comment b/doc/devblog/day_607__v8_is_done/comment_1_7326382d8ff23873c2fe0d6acd984454._comment new file mode 100644 index 0000000000..97e6a5cf81 --- /dev/null +++ b/doc/devblog/day_607__v8_is_done/comment_1_7326382d8ff23873c2fe0d6acd984454._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="pigmonkey" + avatar="http://cdn.libravatar.org/avatar/560cedfcec1b75e8ac2e98a10615d770" + subject="Consider deprecation warnings in the web app" + date="2019-11-07T18:38:28Z" + content=""" +If rebuilding the database is an operation that will take some time, it might be nice to have deprecation warnings in the web app before the assistant eventually autoupgrades repos. + +I use the assistant/web app to manage about 10 repos, some of which are on the larger size both in terms of disk space and number of files. I suspect that if the assistant kicked off an upgrade with a database rebuild on all of these at once, it would have a noticeable performance impact on my machine. If, after v8 is merged but before the assistant autoupgrades, the web app displayed a message like \"This repository is using a version that will soon be upgraded, click here to learn more about v8 and consider upgrading\", it would give folks (who don't read the devblog or release notes) a heads up and give them a chance to manually upgrade repositories one by one. +"""]]