The new module system is target-based rather than variable based. All
information is passed between targets using target properties and
leveraging CMake where possible such as for things like include
directories and linking libraries.

Where CMake doesn't handle things automatically, we store properties
ourselves. This includes whether a module needs autoinit logic (and a
function to handle adding the autoinit logic to a set of targets), which
headers to wrap in various languages, etc.

We no longer provide a copy of the module with VTK, so link to
CMake's own online documentation of the module instead.

Change `ExternalData_LINK_CONTENT` from `MD5` to `SHA512` so that new
content links will be generated using the latter hash algorithm.
Update workflow documentation accordingly.

Simple change to XML readers and writers that adds the optional
support of using a field array called TimeValue to provide time
values (vtkStreamingDemandDrivenPipeline::TIME_STEPS()) to
the pipeline.

Found via `codespell`

This module provides classes and filters for rotation invariant pattern
detection in 2D and 3D scalar-, vector-, and matrix-valued datasets.
vtkComputeMoments computes the moments. Its output together with the
pattern go into vtkMomentInvariants, which puts out a field containig
the similarity of the pattern to each point.  Detailed information on
the theory can be found in Bujack and Hagen
"Moment Invariants for Multi-Dimensional Data":
http://www.informatik.uni-leipzig.de/~bujack/2017TensorDagstuhl.pdf.
A detailed description of the functionality of the module can be
found here:
http://www.informatik.uni-leipzig.de/~bujack/2017MomentInvariantsModule.pdf

The dashboard buildbot links can only be reached from the kitware network.
When developers from the outside click the link, no buildbot list is
displayed.

This patch set uses the links available to people outside the kitware
network.

For reference, see https://www.vtk.org/pipermail/vtk-developers/2017-October/035502.html

Some VTK source code still had tabs (even some of the .py files!).
Also, several comments used utf-8 quotes, which are hard to tell
from regular quotes by eye and can lead to confusing mistakes.

Fix `Announcing` section typo in `release.md` file.

This way it matches other Allocate methods.

Removed unneeded ‘const’ for vtkIdType parameters.

Other misc cleanup while review some vtkDataSet stuff.

The text is vague because occasionally we don't know exactly
what the next release will be called. For example, when we
think the next release will be a major update, but aren't
entirely certain.

Clarify that each branch update requires
a new test command and describe what buildbot
does if a new test command is issued before
a test for a previous update begins.

doxy and misc. typos pt2

Adding guidelines for commit logs. This is needed to ensure some
uniformity in commit logs for the project.

We need more information from developers for new merge requests. This
adds guidelines that we can point them to, if needed.

Removed *_END tags.

Added instructions for verifying that pushed data has been uploaded
successfully after 'git gitlab-push'.

Code extracted from:

    https://gitlab.kitware.com/third-party/proj.git

at commit 41bdf05361007f8c5186f3df9944d86bb273ed13 (for/vtk).

The default NULL value for UpdateExtent(const int extent[6]) was a typo.

This removes the Kaapi and Simple backends, as they are no longer supported.
OpenMP and TBB are the supported backends.

Both rebase and cherry-pick are the normal ways.

These branches are not tied to our master branch in our workflow. Direct
merges to the old release branches are valid.

The way algorithms were updated (made to execute) with
request meta-data (such as update extent) was very error
prone and counter-intuitive. Added new methods to make
updating with meta-data easier. I also deprecated a number
of methods to set request meta-data. This will encourage
developers to migrate to the new API which is less error-
prone.