Finishing up default value work
-Modifying test to demonstrate that ParsedFunctions or ConstantFunctions can be used where FunctionName parameters are requested.
closes #3047
Fixing up HeatSource in modules (inherits from BodyForce)
refs #3047
Removing MooseVariableBase::index() (closes #3094)

It is not needed, since it returns the variable number which is the
task done by number().
Removing mesh dimension restriction from PenetrationLocator (closes #3099)

When having a higher dimensional mesh and using lower-dimensional
elements, PenetrationLocator cannot deal with it, since it assumes that
all elements have dimension equal to the mesh dimension.
Used new default coupling in GBEvolution.C
Used new default coupling in GBEvolution.C #3093
Merge pull request #3098 from andrsd/3094

Removing MooseVariableBase::index() (closes #3094)
Limit around_normals test to serial mesh (#3078)
Fixing a slight namespace issue after a namespace issue was fixed in libmesh.

Refs #000.
Merge pull request #3103 from tonkmr/feature_3093

Feature
Merge pull request #3104 from aeslaughter/sidesets-parmesh

Limit around_normals test to serial mesh
Merge pull request #3100 from andrsd/3099

Removing mesh dimension restriction from PenetrationLocator (closes #309...
Merge pull request #3106 from jwpeterson/fix_namespace

Fixing a slight namespace issue after a namespace issue was fixed in lib...
Miscellaneous DiracKernel improvements

* Storing a vector<Point> per Elem rather than a set<Point> for
  DiracKernels.  A std::set<Point> is always somewhat dangerous due to
  the floating point nature of operator< for Points.
* The DiracKernel object now uses two DiracKernelInfo objects to avoid duplicating code.
* Give DiracKernelInfo a more standard interface since it is used in a few more places now...
* Adding DiracKernel::hasPoint()
* Implement DiracKernelInfo::addPoint() in terms of DiracKernelInfo::hasPoint()
* Adding documentation.

Refs #2847.
Merge pull request #3095 from jwpeterson/dirac_set

Miscellaneous DiracKernel improvements
Merge pull request #3091 from permcody/default_values_final

Finishing up default value work
removed FunctionControlledDT.  I never use it, and it's rather inconvenient to use anyway compared with the MOOSE-supplied timesteppers, and it is untested
OrientedBoxMarkerDepr removed from Richards.  Use moose OrientedBoxMarker instead
Fixed #3046 .  Seemingly huge update with no functionality change - just cosmetic stuff.  Most of the work was doxygenating everything.  Also i made use of RangeCheckedParam whenever i could.  All auxvar/pp/fcn stuff is up-to-date with the new default-for-coupling.  However, i have NOT changed RichardsMaterial since i need to consider backwards compatibility, as mentioned in the comments to ticket #3046
Changed execution of material output and improved tests (#3096)