Here is an example of creating a 2.9.2-all tag. A "-all" means that the tag includes the source code for all of the Indies. The Indies are modules or tools which are part of core Sakai, but can be released on a separate schedule (and hence can have different version numbers, "indie"-pendentally of the main Sakai build).
As a convention, the "###" sign at the beginning of a line indicates a comment. Do not type comments on your command line.
Create 2.9.2-all tag. 
### Example Steps
  1. Create a Jira ticket in the SAK project with a title like "Create 2.9.2-all tag". Note the Jira id. You will use the Jira id in the comment when you make a copy of a previous all. In this example, SAK-23696 is the Jira created for the "Create 2.9.2-all tag" ticket. 
  2. svn cp " SAK-23696  copied from 2.9.1-all tag, ready to mod" 

    Copy the files in the 2.9.1-all tag to the 2.9.2-all tag to create a baseline from which to work.

  3. svn co --ignore-externals

    Checkout 2.9.2-all to get the files you need to edit locally.

  4.  cd sakai-2.9.2-all/ 
  5. edit .externals

    On your local copy of sakai-2.9.2-all, edit the .externals file . You will need to update the versions correctly so that instead of 2.9.1, the file contents point to 2.9.2. You will also be updating the Indie versions which you can find in the POM file for the release. What you are doing is fixing versions of the tags that its pointing to and editing the various POMs.

  6. Use find command to find all pom files to make updates - find ./ -name pom.xml|xargs grep 2.9.1
  7. svn propset svn:externals -F .externals .

    the svn propset command is key to telling SVN to incorporate the source from the external projects. A nice explanation is on the Jasig wiki -,+Multi-Environment+Builds

  8. svn commit
  9. svn up

### Verify the build
mvn clean install sakai:deploy 

### Start tomcat and verify tools work