Fix issue where install and test framework would hang if a repository was not found in the database.
Pack scripts.
Bugfix for 439510f (reported by @saketkc).

Previous logic for determining if state had been calculated for workflow steps in workflow run module would only work for data input steps - this new logic should work for data input or tools.
Workflow running - modify var names/comment to reflect 773951eb2bbf.
Metrics: make the cache use localStorage for persistence
Prevent redirect misuse on user log in.
Fix for masthead link for biostar mainpage.
Fix for registering an account with custom user information when only one custom user info form is defined. Fix editing user info when custom user info forms are defined. Fix functional tests for user info.
Client app: use in /base.mako, rework app init to use AMD definition
Fix comment in lib/galaxy/workflow/run.py
Workflow Editor: Rename can_accept to canAccept.
Workflow Editor: Improve tests related to input terminal canAccept/datatypes.
Elminate stub, create mock tree off inputs (demonstrates what server is feeding), add test for direct and subtype. Add tests for PJA changing output connection datatypes.
Workflow Editor: Break canAccept into smaller pieces (inputFilled and attachable).
Want to reuse attachable right away to fix a bug - and the smaller pieces are good refactoring to support different kinds of input types in dataset collections downstream.
Bugfix: Workflow editor could get in invalid state when trying to preserve connections.
Workflow editor would preserve connections when a tool would update its state (for instance switching a conditional or adding repeat) - but conditional switching can result in connections being invalid (wouldn't have passed can_accept previously). Consider the following tool for instance which changes datatypes of an input based on a conditional (https://gist.github.com/jmchilton/11152628).
Pack scripts.
Record history content type with output of history contents API.

Downstream in dataset collections branch this isn't just dataset, including this will allow clients to distinguish between different kinds of content.
Refactor backbone models to allow different kinds of history contents.

In particular, add a new backbone parent model (HistoryContent) refactored out of HistoryDatasetAssociation. This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API.

There are likely better ways to share common functionality between a dataset and a dataset collection contents - more JS savy developers should feel free to refactor into smaller mixins for instance. For now HistoryContent is just composed of the overlap in functionality between dataset and collection representations downstream and is an quick and dirty way to share said functionality.
Refactor backbone views to allow different kinds of history contents.

This makes room for a forth coming HistoryDatasetCollectionAssociation model that will be emitted from the history contents API. Same comment as previous changeset applies - this is a potentially crude way to share duplicated functionality and a better design would be most welcome.
Rename historyPanel.refershHdas to refreshContents.
Add simple module verions of validation stuff in base controller.

For reuse outside of controllers (i.e. in dataset collections). Objections to refactoring base controller stuff to use this?