Upgrade all Rails v2.x apps to v2.3.15, except for Radiant, which
is fiddly and has been patched instead. This is required due to two
critical security vulnerabilities recently discovered in Rails
versions 2 and 3.

http://weblog.rubyonrails.org/2013/1/8/Rails-3-2-11-3-1-10-3-0-19-and-2-3-15-have-been-released/
https://groups.google.com/forum/?fromgroups=#!topic/radiantcms/b-2DPZlWt3o

By request, remove redundant author and time information from the
text title of an RSS feed item in the 'recent posts' feed for the
forum. The author and time are available in other fields anyway.
This should help out newsreaders that guess at threading based on
title strings.

Canvass was converting e-mail addresses to lower case
when it saved User details for some reason. This meant
that any Hub user with a mixed-case e-mail address would
be able to access one page from Canvass, then nothing
else; Canvass would fail to find a matching local user
with their Hub-based mixed case address, create a new
user, save it and in saving convert the address to
lower case and thus encounter an exception as a local
user would already exist with the lower case version of
the mixed case address.

Very simple fix; verified by checking access to Canvass
on the ROOL site using a mixed case e-mail address in a
Hub account.

Version 1.0.1 of the Hub application, which adds reCaptcha
verification to the sign-up form. Implemented after spambots
attacked the ROOL site and signed up hundreds of bogus users.

Simple modification to Canvass to let it read from a plain
text file and report the first line of this as an amount left
in a donation matching "pot" in the list of bounties.

The forum list now highlights forums containing topics with recent
replies even if sticky items are present. The topic updated date is
used for this too, to avoid having to make further changes to the
way that the forum change date was propagated. It's "more correct"
this way anyway.

Gave up trying to figure out what was wrong with the YAML
syntax colouring engine this time and just wrote it off as
a bad job - the whole thing is commented out. It's not as
if many people browse the SVN tree anyway! We can most
definitely live without it.

Add ROOL site-specific links to CMS and forum pages in the
list and details views for bounties. Make the title of a
bounty in the list view a link to the 'show' page too.

Under certain conditions the YAML syntax parser could get caught in a
tight loop. This was causing the bug tracker Ruby process to crash if
client browsers visited particular YAML files in the Subversion tree.

For some reason, the RCVSWeb default layout was claiming that the page was
in German in the HTML tag.

Sort out the Instiki default layout's handling of titles, which
was a bit of a mess and looks like it's not been historically
properly maintained across Instiki versions and Rails releases
(e.g. the use of "@action_name", rather than "action_name()").
The current document's heading - Home Page aside - is shown as
the main title now. Existing pages with their own duplicate
titles inline will need amending.

Remove most of the Instiki styles related to tables in the content area,
now that the global stylesheet takes care of this. Use of Textile such as:

table(bordered).
| cell | cell | cell | (etc.)

...will give bordered tables as before, else tables have no borders. This
seems to look best on average.

Don't let images make the body column too wide; scale them instead.

Increase hub idle timeout to 4 hours.

Ticket #276 asks for the forum description to be included in the detail
view for a topic, listing posts. The list of topics within a forum sets
a precedent by putting this information in the sidebar, so I've copied
that mechanism for the posts index view.