CMake Nightly Date Stamp
Merge topic 'minor-cleanups'

f6cae4ea Tests: Remove some trailing black lines.
c0ea4c5c Makefile: Fix comment indentation.
5e0c73c7 cmGlobalGenerator: Remove unused variable.
907c09cd include_directory: Add missing include.
a74d125a Help: Fix typo
317d8498 Small typo fix
Merge topic 'doc-package-registry'

bf012e0c Help: Format find_package() command documentation
bd6887e4 Help: Document the package registry in cmake-packages.7
Merge topic 'FindBoost-namespace'

17485e37 FindBoost: Add suport for custom namespaces
Merge topic 'FindJNI-ppc64le'

ac2527e1 FindJNI: Add ppc64le architecture
Merge topic 'FindOpenSSL-prefer-root'

e346c47a FindOpenSSL: Prefer OPENSSL_ROOT_DIR first (#14764)
Merge topic 'doc-usage-requirements'

0c54b775 Help: Document the purpose of usage requirements clearly.
Help: Consolidate remaining 3.0 release notes
Help: Rename 3.0 release notes to 3.0.0

Bug-fix releases 3.0.x may have their own notes so this will look more
consistent.
Help: Drop development topic notes to prepare release

Release versions do not have the development topic section of
the CMake Release Notes index page.
CMake 3.0.0-rc1 version update
Change version scheme to use only two components for feature levels

Historically CMake used three version components for the feature level.
We released new features while incrementing only the third version
component.  Since commit v2.8.2~105^2~4 (New version scheme to support
branchy workflow, 2010-04-23) we used the fourth version component for
bug-fix releases and the development date:

 <major>.<minor>.<patch>[.<tweak>][-rc<n>] = Release
 <major>.<minor>.<patch>.<date>[-<id>]     = Development

This solidified use of three components for the feature level, and was
necessary to continue releasing 2.x versions because:

* Some existing projects performed floating-point comparisons of
  ${CMAKE_MAJOR_VERSION}.${CMAKE_MINOR_VERSION} to 2.x numbers
  so ``x`` could never be higher than 9.

* Version 2.9.<date> was used briefly in post-2.8.0 development in
  CVS prior to the transition to Git, so using it in releases may
  have caused confusion.

Now that we are moving to 3.x versions, these two restrictions go away.
Therefore we now change to use only two components for the feature
level and use the scheme:

 <major>.<minor>.<patch>[-rc<n>] = Release
 <major>.<minor>.<date>[-<id>]   = Development
Merge branch 'release'
Begin post-3.0 development
CMake Nightly Date Stamp
CMake Nightly Date Stamp
stringapi: Use strings for property names

Property names are always generated by CMake and should never be NULL.
stringapi: Use strings for variable names

Variable names are always generated by CMake and should never be NULL.
stringapi: Accept strings in cmStrCmp
stringapi: Accept string parameters in methods which store to strings