Adding time format examples for working periods
Making working periods table more standard
Out of working hours changes

When out of working hours, an icon is now displayed instead of text
(with a tooltip to give more info).
Unfortunately, to do this, I had to completely dismantle the
'issue_fields_rows' table structure and convert it to the raw html. This
was necessary, because otherwise the icon and tooltip options get added
to both the title and the text of the resulting row.

Also, this icon does not appear when in breach.
The icon itself is also temporary (an hourglass). Will get a proper one
when I hear back from Stig.
Add in more docs for the release process.
Add in changelog for 0.9.1
Make the lifeguard project private by default.
Add in en-GB translations, probably will need doing again in a bit :)
Also removed superfluous plugin left over from the first version of the knowledge base.
Out of hours fix

Accidentally made out-of-hours icon disappear when issue in breach in
last commit, rather than if closed as was requested. This is now fixed.
Merge pull request #81 from alexlatchford/private-lifeguard

Make the lifeguard project private by default.
Merge pull request #82 from alexlatchford/en-gb

Add in en-GB translations, removed unused plugin,
Merge pull request #80 from alexlatchford/fix-docs

Add in more docs for the release process.
Making start/end time tips language specific
Working period fields now stay on error

When creating a new working period, the fields will now keep their
previous value if an error is encountered.
Merge pull request #84 from dannybutler/working_period_changes

Working period changes
Deal with bug #59128176
Send issue priority as part of ticket to Producer
Ensure priority-based issue list colouring will work as expected in other scenarios.
Removing out of working hours tooltip detail
Merge pull request #79 from dannybutler/out_of_hours_changes

Out of working hours changes
Add in first go at near breach sla status.
Rename the function so it's easier to find.
Modified near breach calculation

I have added a near_breach_date field to issues and modified the
save_due_date code to also work out the near_breach_date.