Remove old docs (#890)

* Update deprecated 'docs' files

* Remove Vagrantfile, as it's well out of date

* Update RELEASING.md to reflect current truth

Author: rnorth

AUTHORS

@@ -1,12 +1,3 @@
-Richard North <[email protected]>
-Gurpreet Sohal <[email protected]>
-Alex Boldt <[email protected]>
-Robert Požarickij <[email protected]>
-Matthieu Baechler <[email protected]>
-Krystian Nowak <[email protected]>
-Viktor Schulz <[email protected]>
-Asaf Mesika <[email protected]>
-Sergei Egorov <[email protected]>
-Pete Cornish <[email protected]>
-Miguel Gonzalez Sanchez <[email protected]>
-Julien LAMY <[email protected]>
+This file is deprecated. Please see the [contributors](https://github.com/testcontainers/testcontainers-java/graphs/contributors) listing.
+
+[Richard North](https://github.com/rnorth), [Sergei Egorov](https://github.com/bsideup) and [Kevin Wittek](https://github.com/kiview) are the core maintainers.

README.md

@@ -20,4 +20,4 @@ MS SQL Server module is (c) 2017 - 2018 G DATA Software AG and other authors.
 
 Hashicorp Vault module is (c) 2017 Capital One Services, LLC and other authors.
 
-See [AUTHORS](AUTHORS) for all contributors.
+See [contributors](https://github.com/testcontainers/testcontainers-java/graphs/contributors) for all contributors.

RELEASING.md

@@ -8,8 +8,9 @@ Testcontainers' release process is automated as a Travis deployment. This descri
 1. Ensure that the [`CHANGELOG`](CHANGELOG.md) file is up to date and includes all merged features.
 1. Create a new release on GitHub. **The tag name is used as the version**, so please keep the tag name plain (e.g. 1.2.3).
 1. Check that the Travis build passed.
-1. Release of published artifacts is fully automated. Once the Travis build completes, there are no further actions to perform on the repository.
-1. When available through Maven Central, poke [@whichrich](https://twitter.com/whichrich) to announce the release on Twitter!
+1. Release of published artifacts to Bintray is fully automated.
+1. After successful publication to Bintray, the artifacts must be synced to Maven Central.
+1. When available through Maven Central, poke [Richard North](https://github.com/rnorth) to announce the release on Twitter!
 
 ## Internal details
 

Vagrantfile

@@ -10,16 +10,5 @@ Exact future features aren't set in stone, but here are the principles we should
 * In line with the above, we should aim for feature completeness soon.
 * Similarly, it should leverage good things that already exist (like reliable public Docker images) and be composable with other tools.
 * That said, don't lock us in to more third-party components than absolutely necessary, and only use well maintained dependencies.
-* It must be possible for a developer to use _or build_ this library with just minimal standard tools (Java JDK, Maven), and a local Docker environment. Do not use any non-public dependencies in the core lib or standard modules. (see the `proprietary-deps` maven profile for how we're dealing with the Oracle XE module that has a test-time dependency on the properitary Oracle JDBC driver JAR)
+* It must be possible for a developer to use _or build_ this library with just minimal standard tools (Java JDK, Maven), and a local Docker environment. Do not use any non-public dependencies in the core lib or standard modules.
 
-## Future goals/anti-goals
-
-This list may cross over with the [issues list](https://github.com/testcontainers/testcontainers-java/issues) some times.
-
-* **Better documentation and log messages**. We need this.
-* **Database state snapshotting**. Some projects have complex test data that is time consuming to reload. This means that either testing takes a very long time (test data has to be reloaded often), or tests aren't sufficiently independent (test data is not reloaded and therefore tests aren't independent). Testcontainers should provide a way to snapshot DB state and quickly reload that state. Docker [native Checkpoint/Restore In Userspace](http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html) looks like the best way to accomplish this.
-* **Support docker images pulled from private registries**
-* **Support integration testing in other languages/environments**. .NET and NodeJS seem like sensible options here.
-* **Allow a JUnit @Rule to point to a local `Dockerfile` rather than an imagename**. Perhaps.
-* **Don't enter the build tools space**
-* **Don't become involved in live run-time environments**. This is a tool for testing. Some features could technically be misused in a live environment, but this isn't something we should want to support.