Remove v0.14 to avoid version confusion

Signed-off-by: Masahiro Nakagawa <repeatedly@gmail.com>

Author: repeatedly

developer/api-plugin-base.md

@@ -1,6 +1,6 @@
 # Plugin Base API
 
-All plugin types are subclass of `Fluent::Plugin::Base` in Fluentd v0.14
+All plugin types are subclass of `Fluent::Plugin::Base` in Fluentd v1
 or later. Base class has some features and methods which provides basic
 mechanism as plugins. This page shows these methods provided by
 `Fluent::Plugin::Base`, and other methods provided commonly in some type

developer/api-plugin-formatter.md

@@ -68,7 +68,7 @@ should look like `100,200`
 
 Formatter plugins are designed to be used from other plugins, like
 Input, Filter and Output. There is a Formatter plugin helper for that
-purpose (v0.14.1 or later):
+purpose:
 
 ```
 # in class definition

developer/api-plugin-parser.md

@@ -86,8 +86,7 @@ For more details about `<parse>` section, see [Parse section configurations](/co
 ## How To Use Parsers From Plugins
 
 Parser plugins are designed to be used from other plugins, like Input,
-Filter and Output. There is a Parser plugin helper for that purpose
-(v0.14.1 or later):
+Filter and Output. There is a Parser plugin helper for that purpose:
 
 ```
 # in class definition

developer/plugin-development.md

@@ -33,20 +33,19 @@ before they dive into writing their own plugins.
 [RubyKaigi 2014 talk](http://rubykaigi.org/2014/presentation/S-NaotoshiSeo/).)
 
 This slide is based on Fluentd v0.12. There are many difference between
-v0.12 and v0.14/v1.0 API, but it may help our understanding about
-Fluent's total design.
+v0.12 and v1 API, but it may help our understanding about Fluent's total design.
 
 
 ### Fluentd version and Plugin API
 
-Fluentd now has two active versions, v1.0 and v0.12. v1.0 is current
-stable and v1.0 has brand-new Plugin API. v0.12 is old stable and v0.12
+Fluentd now has two active versions, v1 and v0.12. v1 is current
+stable and v1 has brand-new Plugin API. v0.12 is old stable and v0.12
 has old Plugin API.
 
-The important point is v1.0 supports v1.0 and v0.12 APIs. It means the
-plugin for v0.12 works with v1.0.
+The important point is v1 supports v1 and v0.12 APIs. It means the
+plugin for v0.12 works with v1.
 
-We recommend to use new v1.0 plugin API for new plugins.
+We recommend to use new v1 plugin API for new plugins.
 
 
 ### Send a patch or fork?

developer/plugin-update-from-v0.12.md

@@ -1,18 +1,18 @@
-# Updating plugin for v1.0 from v0.12
+# Updating plugin for v1 from v0.12
 
 This guide is for plugin authors to show how to update
 input/output/filter plugins written for Fluentd v0.12 or earlier.
 
 There are something to be considered (see following "Updating Plugins
 Overview" section for details):
 
--   Plugins which use v0.12 API will be supported between Fluentd v0.14
-    and v1 (will be obsoleted at v2).
--   Users can use new features of Fluentd v1.0 only with plugins using
+-   Plugins which use v0.12 API will be supported in Fluentd v1
+    (will be obsoleted at v2).
+-   Users can use new features of Fluentd v1 only with plugins using
     new API.
 -   Plugins which use new API don't work on Fluentd v0.12.x.
 
-Fluentd core team strongly recommend to use v1.0 API to make your
+Fluentd core team strongly recommend to use v1 API to make your
 plugins stable, consistent and easy to test.
 
 
@@ -24,7 +24,7 @@ These are steps to update your plugins safely.
 2.  update dependency
 3.  update code and tests
 4.  update CI environments
-5.  release the newer version for Fluentd v0.14.x and later
+5.  release the newer version for Fluentd v1 and later
 
 
 ### 1. release a latest version
@@ -46,23 +46,19 @@ newer versions for Fluentd v0.12 users without breaking anything.
 ### 2. update dependency
 
 Following updates are on master branch. You should update dependency in
-gemspec at first to depend on Fluentd v0.14.
+gemspec at first to depend on Fluentd v1.
 
--   fix dependency about `Fluentd` to `[">= 0.14.0", "< 2"]`
+-   fix dependency about `Fluentd` to `[">= 1", "< 2"]`
 -   execute `bundle install`
 
-Is it correct to use `>= 0.14.0` instead of `~> 0.14.0`? Yes. Fluentd v1
-will be compatible with v0.14.0 (especially for plugin APIs), so you
-should use `>= 0.14.0`. Let's think about v2 few years later.
-
 Recommended dependency in gemspec:
 
 ```
 # in gemspec
 Gem::Specification.new do |gem|
   gem.name = "fluent-plugin-my_awesome"
   # ...
-  gem.add_runtime_dependency "fluentd", [">= 0.14.0", "< 2"]
+  gem.add_runtime_dependency "fluentd", [">= 1", "< 2"]
 end
 ```
 
@@ -80,12 +76,10 @@ plugins.
 ### 4. update CI environments
 
 If you have CI configurations like `.travis.yml` and `appvayor.yml`,
-these should be updated to support Fluentd v0.14/v1.0. Fluentd
-v0.14/v1.0 supports Ruby 2.1 or later. CI environments should not
-include Ruby 2.0 or earlier. It's good idea to add latest Ruby (2.4 at
-Nov 2017).
+these should be updated to support Fluentd v1. Fluentd v1 supports Ruby 2.4 or later.
+CI environments should not include Ruby 2.3 or earlier.
 
--   remove Ruby 2.0 or earlier from CI environments
+-   remove Ruby 2.3 or earlier from CI environments
 -   add Ruby 2.4 (or other latest version) to CI environments
 
 
@@ -98,8 +92,8 @@ Add requirements section to `README.md` like following:
 
 | fluent-plugin-may_awesome | Fluentd    | Ruby   |
 |:--------------------------|:-----------|:-------|
-| >= 1.0.0                  | >= v0.14.0 | >= 2.1 |
-| < 1.0.0                   | >= v0.12.0 | >= 1.9 |
+| >= 1.0.0                  | >= v1      | >= 2.4 |
+| < 1.0.0                   | >= v0.12.0 | >= 2.1 |
 ```
 
 This helps that plugin users can understand plugin requirements.
@@ -112,7 +106,7 @@ not patch version up. If the current major version of your gem is equal
 or larger than 1, you should bump major version up (e.g., from 1 to 2).
 If the current major version is 0, you should bump minor version up
 (e.g., from `0.4.2` to `0.5.0`). Then, you can publish a new release
-which is available with Fluentd v0.14/v1.0.
+which is available with Fluentd v1.
 
 -   bump the version up
 -   release it to rubygems.org

overview/faq.md

@@ -15,8 +15,8 @@ Use td-agent 3. It includes v1.
 
 ## What is the differences between v1 or v0.14?
 
-No differences. v1.0 is built on top of v0.14. Use v1.0 for newer
-installation. We use v1.0/v1.x on our document.
+No differences. v1 is built on top of v0.14. Use v1 for newer
+installation. We use v1 or v1.x on our document.
 
 
 ## Known Issue