Move release dev note to post-release

Allows image to be released before run-examples.sh pulls

docs/src/dev/developer/release.asciidoc

@@ -80,7 +80,7 @@ Take care to commit or not commit changes related to that as necessary.
 
 == Release Manager Requirements
 
-If this is your first time as release manager, you will need to setup keys for signing purposes per the Apache
+If this is your first time as release manager, you will need to set up keys for signing purposes per the Apache
 release process. Generally speaking, this will mean that you will need to generate a key-pair and then publish your
 public key.
 
@@ -120,7 +120,6 @@ during this period.
 .. Run the full integration test suite: `docker/build.sh -t -i -n`
 .. Build and test the Docker images: `mvn clean install -pl gremlin-server,gremlin-console -DdockerImages`
 .. Ensure that the Gremlin.Net.Template gets packaged successfully: `mvn clean install -pl :gremlin-dotnet-source -Dnuget`
-.. Ensure that the GLV examples are compiling and running successfully: `bin/run-examples.sh`
 .. Deploy a final SNAPSHOT to the Apache snapshot repository for Java.
 .. Review LICENSE and NOTICE files to make sure that no <<dependencies,changes are needed>>.
 .. Review javadoc filters on the "Core API" docs to be sure nothing needs to change.
@@ -328,6 +327,8 @@ the help of a PMC member for those steps.
 .. Commit and push the `SNAPSHOT` changes to git
 . Examine the `future.asciidoc` and update the "Roadmap" as needed.
 . Send email to advise that code freeze is lifted.
+. Ensure that the GLV examples compile and run with the latest image and dependencies: `bin/run-examples.sh`.
+.. Make changes as necessary to update the examples.
 . Generate a list of dead branches that will be automatically deleted and post them as a DISCUSS thread for review, then once consensus is reached removed those branches.
 . Set up the IO tests for the current `SNAPSHOT` as discussed in the <<io,IO Documentation and Testing Section>>