DailyTimeIntervalTrigger dit not behave correctly when the server was running with a time offset different than UTC+0
Tweak exception example timing
Add some thread safety to DisallowConcurrentJobExecutionTest
Add some double checking for halted condition in QuartzSchedulerThread
Tweaks to PropertySettingJobFactory and its tests
Pass the initial thread pool size, before initializing the JobStore
Schedule build constructors now protected to allow inheritance, documentation tweaks, some more schedule building methods
Fix regression that was introduced with new timestamp reading functionality, change FiredTriggerRecord timestamp to be DateTimeOffset instead of long to follow convention in SchedulerStateRecord
Documentation fixes and cleanup, also restored 3.5 build support
Remove DateBuilder.IntervalUnit and use general IntervalUnit instead, general cleanup, documentation fixes
Documentation project tweaks and content
Documentation project update
Merge pull request #33 from yorah/2efc0df1dd4ff077a1182cfe12186127474937fb

Fixing the bug with DailyTimeIntervalTrigger related to Timezones
DailyTimeIntervalTrigger should now actually work as expected
Change AnnualCalendarTest to use trigger and job builders
Force UTC ticks when storing datetimes, ado delegate cleanup
Upgraded to NAnt 0.91 final
Preparing 2.0 beta 2 release
Update AssemblyInfos for beta 2 release
Cosmetics