Fixing tests build file
Bumping up the versions.
bumping up the version
Update README.md

point to release branch build badge
Remove unused classes
Remove exporting package that no longer exists
TISTUD-6031 Windows: SplashScreen links lead to incorrect URL
  - Try to run Program.launch to open a URL first, if that fails fall back to our custom code for trying to launch an URL in a browser.
  -  try to better parse the output of reg query to grab location/args to launch browser. Add unit tests for launching browser by command.
TISTUD-6031 Windows: SplashScreen links lead to incorrect URL
  - Try to run Program.launch to open a URL first, if that fails fall back to our custom code for trying to launch an URL in a browser.
  -  try to better parse the output of reg query to grab location/args to launch browser. Add unit tests for launching browser by command.
TISTUD-6514 Allow selecting the base repo and branch for a pull request
TODO: Add unit tests for the new methods on GithubRepository: getForks, getSource, equals, hashcode, getFullName
- Add unit tests for GithubUser, GithubOrganization, GithubRepository
- Implements equals() and hashcode() for GithubRepository, GithubPullRequest, GithubOrganization, GithubUser
Remove usage of CoreMacOSX.FileManager_findFolder to lookup user's Documents and Desktop folders on Mac. Instead cheat and assume they live under ~/Documents and  ~/Desktop, where we fill in ~ with the value of user.home

I'm doing this because 9 times out of 10 when I launched junit tests in a dev instance, they'd never start, and under the debugger I could see these calls as being locked. I've seen instances of this in the past as well.
Merge pull request #205 from sgtcoolguy/perf_fix

perf_fix
Remove usage of CoreMacOSX.FileManager_findFolder to lookup user's Documents and Desktop folders on Mac. Instead cheat and assume they live under ~/Documents and  ~/Desktop, where we fill in ~ with the value of user.home

I'm doing this because 9 times out of 10 when I launched junit tests in a dev instance, they'd never start, and under the debugger I could see these calls as being locked. I've seen instances of this in the past as well.
Merge pull request #204 from sgtcoolguy/TISTUD-6514

TISTUD-6514 Allow selecting the base repo and branch for a pull request
TISTUD-6162 Titanium Studio shows psuedoproperty assignments as errors
  - Add support for get and set syntax
  - Fix up so it formats semi-decent
  - Add tests around lexer/parser for new terminals and syntax
Fix broken tests:
- When inferring type of ObjectNode with no docs (or no docs with @type tag), assume Object.
- Add sanity check and test case to enforce that a type cannot have itself added as a parent (which is what was happening to break the tests).
TISTUD-6584 Importing sample apps from Dashboard or Samples gives intermittent 'Auto-share exception'
Merge pull request #206 from sgtcoolguy/TISTUD-6162

TISTUD-6162 Titanium Studio shows psuedoproperty assignments as errors
Merge pull request #208 from pinnamur/TISTUD-6584

TISTUD-6584 Importing sample apps from Dashboard or Samples gives interm...
TISTUD-6376 Appcelerator Studio 3.3.0.201405211748 (RC) is very slow to work
  - Refactor the ChangedFile class and how we perform Gitindex refreshes
  - Make ChangedFile hold an IPath, not two Strings to represent portable/OS versions of path. Use IPath in API, not String.
  - try to encapsulate most changes to ChangedFile. It's intended to be a value object pattern, so when we want a modified version we clone or merge into new instances - try to keep immutable as much as possible.
  - When we do refreshes, don't use a shared list across the three jobs/callables that gather the staged/unstaged/other files. Instead have each build it's own mapping from IPath to ChangedFile, then if we have multiple entries for the same path, merge the ChangedFile instances. This should avoid synchronization issues - and hopefully should be faster.