Bump doc version to 7.0.0

Author: ocadaruma

docs/consuming-any-data.adoc

@@ -1,6 +1,6 @@
 Consuming Arbitrary Topic
 =========================
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: common,protocol,processor
 
 This document guides you how to consume and process topics containing records not consists of Decaton's protocol (not produced by DecatonClient) using Decaton processors.

docs/dynamic-property-configuration.adoc

@@ -1,6 +1,6 @@
 Dynamic Property Configuration
 =============================
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: centraldogma,processor
 
 == Property Supplier

docs/getting-started.adoc

@@ -1,6 +1,6 @@
 Getting Started Decaton
 =======================
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: common,client,processor,protobuf
 
 Let's start from the most basic usage of Decaton client/processor.

docs/key-blocking.adoc

@@ -1,5 +1,5 @@
 = Key Blocking
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: processor
 
 == Introduction

docs/monitoring.adoc

@@ -1,6 +1,6 @@
 Monitoring Decaton
 ==================
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: processor
 
 This document guides you how to monitor your Decaton processor applications.

docs/rate-limiting.adoc

@@ -1,5 +1,5 @@
 = Rate Limiting
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: processor
 
 == Introduction
@@ -37,7 +37,7 @@ The value can have three different meanings:
 Note that the actual processing rate may not reach the given value if a task takes over a second to process or the value is greater than actual throughput per second.
 |===
 
-=== Example 
+=== Example
 Just like other properties, you can set it through `SubscriptionBuilder#properties`, as shown in the following example:
 
 [source,java]

docs/retry-queueing.adoc

@@ -1,5 +1,5 @@
 = Retry Queuing
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: processor
 
 == Introduction
@@ -95,7 +95,7 @@ But if you invoke `ProcessingContext#retry` in the processor, you **don't** have
 .RetryingProcessorAsync.java
 ----
 public class RetryingProcessorAsync implements DecatonProcessor<PrintMessageTask> {
-    
+
     @Override
     public void process(ProcessingContext<PrintMessageTask> context, PrintMessageTask task)
             throws InterruptedException {
@@ -119,7 +119,7 @@ public class RetryingProcessorAsync implements DecatonProcessor<PrintMessageTask
     }
 }
 ----
-<1> You still need to call `#complete` when the asynchronous job finishes normally.  
+<1> You still need to call `#complete` when the asynchronous job finishes normally.
 <2> If you call `ProcessingContext#retry` then you don't need to call it explicitly.
 
 == Implementation

docs/task-compaction.adoc

@@ -1,5 +1,5 @@
 = Task Compaction
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: processor
 
 == Introduction
@@ -24,7 +24,7 @@ To use `Task Compaction`, you need to do two things:
 2. Add `CompactionProcessor` to the head of your processor pipeline.
 
 === CompactionProcessor
-`CompactionProcessor` can be seen as a selector that decides whether a task should be kept or compacted. `CompactionProcessor` constructor takes two 
+`CompactionProcessor` can be seen as a selector that decides whether a task should be kept or compacted. `CompactionProcessor` constructor takes two
 arguments:
 
 |===
@@ -75,11 +75,11 @@ public class TaskCompactionMain {
     private static CompactionProcessor<LocationEvent> createCompactionProcessor() {
         return new CompactionProcessor<>(1000L, (left, right) -> { // <3>
             if (left.task().getTimestamp() == right.task().getTimestamp()) { // <4>
-                return CompactChoice.PICK_EITHER; 
+                return CompactChoice.PICK_EITHER;
             } else if (left.task().getTimestamp() > right.task().getTimestamp()) {
                 return CompactChoice.PICK_LEFT; // <5>
             } else {
-                return CompactChoice.PICK_RIGHT; // <6> 
+                return CompactChoice.PICK_RIGHT; // <6>
             }
         });
     }

docs/tracing.adoc

@@ -1,5 +1,5 @@
 = Tracing
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: brave,processor
 
 Decaton can integrate with distributed tracing frameworks so that you can associate the processing of a message
@@ -23,4 +23,4 @@ SubscriptionBuilder.newBuilder("tracing-key-processor")
                    .enableTracing(
                            new BraveTracingProvider())
 ...
----
+----

docs/why-decaton.adoc

@@ -1,6 +1,6 @@
 Why Decaton
 ===========
-:base_version: 6.0.0
+:base_version: 7.0.0
 :modules: processor
 
 This document explains why we have decided to create a new consumer framework.