This is an automated email from the ASF dual-hosted git repository.
joshsh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/master by this push:
new 237a8f6 Put the main header at the top so it appears as an HTML title
237a8f6 is described below
commit 237a8f67ac62ac51229aed26babc0b3102292c3a
Author: Joshua Shinavier <[email protected]>
AuthorDate: Thu Nov 25 07:41:10 2021 -0800
Put the main header at the top so it appears as an HTML title
---
docs/src/dev/future/index.asciidoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/src/dev/future/index.asciidoc
b/docs/src/dev/future/index.asciidoc
index 0852582..f31c090 100644
--- a/docs/src/dev/future/index.asciidoc
+++ b/docs/src/dev/future/index.asciidoc
@@ -1,3 +1,5 @@
+= TinkerPop Future
+
////
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
@@ -18,8 +20,6 @@
image::apache-tinkerpop-logo.png[width=500,link="https://tinkerpop.apache.org";]
:toc-position: left
-= TinkerPop Future
-
This document offers a rough view at what features can be expected from future
releases and catalogs proposals for
changes that might be better written and understood in a document form as
opposed to a dev list post.
@@ -107,4 +107,4 @@ it comes time to promote `4.0-dev` to `master` the
procedure for doing so will b
From this point 3.x development will occur on `3.x-master` and 4.x development
occurs on `master` (with the same version
branching as we have now, e.g `3.3-dev`, `4.1-dev`, etc.) The `3.x-master`
branch changes will likely still merge to
-`master`, but will all merge as no-op changes.
\ No newline at end of file
+`master`, but will all merge as no-op changes.
