removing rake and outdated references to it

docs/en_us/developers/source/public_sandboxes.rst

@@ -147,7 +147,7 @@ Caveats and Warnings
 
    Next, run the commands::
 
-     rake i18n:generate
+     paver i18n_generate
      python i18n/verify.py
 
    This will generate reports of broken translations in your language. This will not, however,

docs/en_us/developers/source/testing/code-coverage.rst

@@ -15,7 +15,7 @@ we can ensure that pull requests have a very high percentage of test coverage
 To check the coverage of your pull request, just go to the top level of the
 edx-platform codebase and run::
 
-    $ rake coverage
+    $ paver coverage
 
 This will print a coverage report for your branch. We aim for
 a coverage report score of 95% or higher. We also encourage you to write

docs/en_us/developers/source/testing/code-quality.rst

@@ -20,8 +20,8 @@ edx-platform codebase and run::
 
     $ paver run_quality
 
-Note: The rake commands ``rake quality``, ``rake pep8``, and ``rake pylint`` are now deprecated
-to ``paver run_quality``, ``paver run_pep8``, and ``paver run_pylint`` respectively.
+You can also use the `paver run_pep8`` and ``paver run_pylint`` commands to run just pep8 or
+pylint.
 
 This will print a report of the quality violations that your branch has made.
 

docs/en_us/install_operations/source/devstack/run_devstack.rst

@@ -36,8 +36,8 @@ Connect to the Devstack Virtual Machine
     sudo su edxapp
 
    This command loads the edxapp environment from the file
-   ``/edx/app/edxapp/edxapp_env``. This puts ``venv python``, ``rbenv ruby`` and
-   ``rake`` are in your search path.
+   ``/edx/app/edxapp/edxapp_env``. This puts ``venv python`` and ``rbenv ruby``
+   in your search path.
 
    This command also sets the current working directory to the edx-platform
    repository (``/edx/app/edxapp/edx-platform``).

docs/en_us/internal/development.md

@@ -4,9 +4,8 @@
 
 ### Ruby
 
-To install all of the libraries needed for our rake commands, run `bundle install`.
+To install all of the required ruby libraries, run `bundle install`.
 This will read the `Gemfile` and install all of the gems specified there.
-Note: Rake has been deprecated to the Python Paver. This is only needed until rake is fully deprecated
 
 ### Python
 

docs/en_us/internal/testing.md

@@ -223,7 +223,7 @@ To run JavaScript tests in your default browser:
     paver test_js_dev -s common
 
 
-These rake commands call through to a custom test runner.  For more info, see [js-test-tool](https://github.com/edx/js-test-tool).
+These paver commands call through to a custom test runner.  For more info, see [js-test-tool](https://github.com/edx/js-test-tool).
 
 
 ### Running Bok Choy Acceptance Tests
@@ -287,7 +287,7 @@ installed to run the tests in Chrome.  The tests are confirmed to run
 with Chrome (not Chromium) version 34.0.1847.116 with ChromeDriver version 2.6.232917.
 
 To run all the acceptance tests:
-    rake test:acceptance
+    paver test_acceptance
 
 To run only for lms or cms:
 
@@ -309,7 +309,7 @@ To start the debugger on failure, add the `--pdb` option to extra_args:
 To run tests faster by not collecting static files, you can use
 `paver test_acceptance -s lms --fasttest` and `paver test_acceptance -s cms --fasttest`.
 
-Acceptance tests will run on a randomized port and can be run in the background of rake cms and lms or unit tests.
+Acceptance tests will run on a randomized port and can be run in the background of paver cms and lms or unit tests.
 To specify the port, change the LETTUCE_SERVER_PORT constant in cms/envs/acceptance.py and lms/envs/acceptance.py
 as well as the port listed in cms/djangoapps/contentstore/feature/upload.py