Feature requests are not accepted

See #860.

.github/ISSUE_TEMPLATE.md

@@ -20,7 +20,9 @@ This is … (pick one!)
 - [ ] A bug report
   - [ ] I've filled in steps to reproduce below
 - [ ] A feature request
-  - [ ] I've given a **detailed** _example_ below
+  - Sorry, feature requests are not accepted.
+    See [issue #860](https://github.com/akhodakivskiy/VimFx/issues/860)
+- [ ] A question
 - [ ] Somehting else
 
 
@@ -48,17 +50,16 @@ Steps to reproduce:
 
 1. Go to https://www.mozilla.org/en-US/about/
 2. Scroll to the bottom of the page.
-2. Press `f`.
+3. Press `f`.
 
 Expected result: There should be hint marker for the “Contact Us” link at the bottom.
 
 Actual result: There is no hint marker for the “Contact Us” link.
 -->
 
-<!-- Remember to delete the feature request stuff below :) -->
 
 
-
-<!-- For FEATURE REQUESTS: (edit the below example) -->
-
-When I go to https://www.mozilla.org/en-US/about/ and press `?`, _this_ and _that_ happens. I’d like _this_ to happen instead, because that really helps me with _that._ (Add more details here.) Perhaps something like _this_ should be added to VimFx?
+<!-- For FEATURE REQUESTS:
+Sorry, feature requests are not accepted. See issue #860:
+https://github.com/akhodakivskiy/VimFx/issues/860
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,4 +5,7 @@ Submitting a translation? Nice! Go ahead and hit that “Create pull request”
 
 Doing something else? To get your changes merged faster, check this out:
 https://github.com/akhodakivskiy/VimFx/blob/master/documentation/CONTRIBUTING-CODE.md
+
+Also remember that new features are not accepted. See issue #860:
+https://github.com/akhodakivskiy/VimFx/issues/860
 -->

README.md

@@ -11,7 +11,8 @@ for browsing and navigation, for a near mouseless experience.
 
 **New to VimFx?** Check out [Questions & Answers]!  
 Power user? Make a [config file]!  
-In either case, have look at the the [documentation] and the [wiki].
+In either case, have look at the the [documentation] and the [wiki].  
+Also check out **[the future of VimFx].**
 
 VimFx is made by [these awesome people][people].
 
@@ -22,6 +23,7 @@ VimFx is made by [these awesome people][people].
 [documentation]: https://github.com/akhodakivskiy/VimFx/tree/master/documentation#contents
 [wiki]: https://github.com/akhodakivskiy/VimFx/wiki
 [Questions & Answers]: https://github.com/akhodakivskiy/VimFx/tree/master/documentation/questions-and-answers.md
+[the future of VimFx]: https://github.com/akhodakivskiy/VimFx/issues/860
 [people]: https://github.com/akhodakivskiy/VimFx/blob/master/PEOPLE.md
 
 ## Why VimFx was created

documentation/CONTRIBUTING-CODE.md

@@ -71,6 +71,9 @@ Finally send a pull request to same branch as you based your topic branch on
 
 VimFx uses three numbers to describe its version: x.y.z, or major.minor.patch.
 
+For the time being, it is the most likely that only the last number (patch) is
+going to change. See [issue #860] for more information.
+
 When version 1.0.0 has been released, the first number (major) will only be
 incremented when there are backwards-incompatible changes, such as changes to
 defaults or to the [config file API]. This should be avoided. The idea is that
@@ -99,4 +102,5 @@ branch, while most other things go into the master branch.
 Trying to choose the right branch is important in order to be able to keep a
 rapid release cycle.
 
+[issue #860]: https://github.com/akhodakivskiy/VimFx/issues/860
 [config file API]: api.md