From 61ab718349b243c3fd71e1ff120d2845159ace09 Mon Sep 17 00:00:00 2001 From: Lars Date: Wed, 8 Jan 2020 23:07:41 +0100 Subject: [PATCH] Clarification for update mechanism #2 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 93203fc..194b277 100644 --- a/README.md +++ b/README.md @@ -6,4 +6,4 @@ Script for Mozilla Firefox and Google Chrome browser to [send geocaches directly Changes must be done on the `master` branch. Once the changes are validated and ready to release, they can be merged to the `release` branch. The script version number needs to be raised after that merge to roll it out. -The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release` users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update. +The script download link on the [c:geo homepage](http://cgeo.org) as well as the update mechanism for the installed script directly targets the raw script on the `release` branch, which means after merging the changes to `release`, together with the required version number increase, users will see the update on the website and script hosts (e.g. Greasemonkey) will detect and notify users to update.