fixed login routing issue causing onboarding to not be shown
If the users credentials are removed for whatever reason, set the user to logged out
Switch $$merge$$ to :shipit:
Made a specific versions of _getSourceLink and _getRevnoLink for
BrowserCharmView.
Merge pull request #21 from garyposter/shipit

Document the noble and important change from $$merge$$ to :shipit:
Merge pull request #20 from bac/fix-branch-reference

 Made a specific versions of _getSourceLink and _getRevnoLink for BrowserCharmView.
Update process docs and Makefile for git releases.
Merge pull request #22 from mitechie/update-distfile

- Update the makefile to convert bzr-ism to git-ism
- I have qa'd a developer release up through uploading, but killed it when I needed to auth launchpad with an oauth credential.
- I have followed most of the release steps, but not all. There might still be a snag/two to work out on our first real release which we'll do next week and I'll volunteer to help with that in case I've missed a step, I just don't want to go through with a real release right now.
Merge pull request #19 from hatched/fix-login-redirect

To QA:
Sandbox:
Make sure you are able to log in/out. (u: admin p: admin)
Make sure the onboarding can be displayed at the root url. To clear your localstorage, open up the app and type `localStorage.clear()` in the console, then refresh, it should show the onboarding.

Real Env:
Make sure you are able to log in/out (password is in your environments.yaml file)
http://jujugui.wordpress.com/2013/10/15/if-you-want-to-run-a-custom-gui/
Remove heading per UX request (bug 1261347)
Allow configuring mocha color escape codes
Merge pull request #23 from garyposter/bug1261347

https://bugs.launchpad.net/juju-gui/+bug/1261347
Update hacking to use the juju-sync alias
Merge pull request #25 from mitechie/update-git-docs
Merge pull request #24 from mitechie/jenkins-mocha

- Upgrade mocha-phantomjs to get access to the --no-color feature. It's only listed in the hacking docs.
- Add a in the Makefile so it's evident the option exists in the test-server.sh script.
- Update test-server.sh script to check for the ENV var and set the mocha command appropriately. 

QA:

This is done so that test results are easier to read in the jenkins CI output. The change should be present and qa'able now by looking at the test run of this pull request vs an older pull request. You have to look at the console data to see the test output. 

http://ci.jujugui.org:8080/job/juju-gui/88/

vs. 

http://ci.jujugui.org:8080/job/juju-gui/87/


NOTE: 

It appears that the GET requests still escape. There's nothing in phantomjs I can see to set for this and it appears this is a limitation in the implementation of the --no-color flag to mocha-phantomjs. Perhaps a patch upstream would be worthwhile at some point, but this at least helps reading/finding the actual test lines.