Hotfix: Issue 178 -- time attribute serialization in JUnit reports

Hotfix for issue 178. Updated release notes in BOLD

Release Notes:
[Fix: 178] Time attribute should not be serialized as a tag in the JUnit report
[Fix: 177] Correction for the malformed XML Attribute names
[Fix: 169] Test Runner now filters the Excluded VI List when dscovering tests
[Fix: 166] Test Runner linkage info now errors on invalid/broken test during discovery
[Fix: 164] Inverted inputs in Assert Almost Equal are now consistent with other assertions
[Fix: 163] Linkage Info now skips conditionally disabled methods
[Feature: 161] XML JUnit can now be localized (defaults to system's regional settings)
[Fix: 160] Space character in test label now has no impact on result tree location
[Feature: 158] Verbose explanations can now be forced even for tests that assert
[Fix: 155] Conditionally disabled methods do not produce bad linkage in Test Runners
[Feature: 152] Test manager generates event as each individual tests and assertions are processed
[Feature: 151] Verbose explanations can now be added to any assertion
[Feature: 148] Failure descriptions can now be added to any report, including JUnit

Thanks for all the contributions that led to this release, whether by reporting bugs, requesting features that made it to release or by lending a hand in fixing issues or releasing features:

Tanner Blair (@tannerblair)
Sébastien Michaud (@SebMichaud)
Ajay MV (@digiajay)
Pascal Neuperger (@logmanoriginal)
Francois Normandin (@francois-normandin)
Roberto Olea (@Robbie20)
Hunter Smith (@HunterJKI)
(@phollyni)