Changes in template files are not shipped with upgrade packages (unless a security issue is fixed) because someone could have modified changed templates and he might lose those changed after upgrading.
Readme files says which templates needs to be modified and how:
To manually make changes to teplates please do the following. As usual, backup the files prior to changing anything.
1. {VIVVO_TEMPLATE_DIR}box/comments.tpl
================================================== ======
Around line 6 find the following:
<vte:param name="search_order" value="ascending" />
and replace with:
<vte:param name="search_order" value="{VIVVO_COMMENTS_ORDER}" />
Also, in the same template you should find this code around line 8:
<vte:param name="search_limit" value="10" />
Just replace the line with:
<vte:param name="search_limit" value="{VIVVO_COMMENTS_NUM_PER_PAGE}" />
2. {VIVVO_TEMPLATE_DIR}_syndication/rss2.0.tpl
================================================== =======
Lines 29 and 43:
<pubDate><vte:value select="{article.created|format_date:'D, d M Y H:i O'}" /></pubDate>
should be replaced with:
<pubDate><vte:value select="{article.created|format_date:'D, d M Y H:i O','1'}" /></pubDate>
3. {VIVVO_TEMPLATE_DIR}_syndication/rss2.0_comments.tpl
================================================== ========
The following code around lines 21 and 27:
<pubDate><vte:value select="{article.created|format_date:'D, d M Y H:i O'}" /></pubDate>
should be replaced with this code:
<pubDate><vte:value select="{article.created|format_date:'D, d M Y H:i O','1'}" /></pubDate>
In the same template around line 47 instead of:
<pubDate><vte:value select="{comment.create_dt|format_date:'D, d M Y H:i O'}" /></pubDate>
place:
<pubDate><vte:value select="{comment.create_dt|format_date:'D, d M Y H:i O','1'}" /></pubDate>
changes in comments.tpl are needed if you want to use new options in configuration page on admin panel, and changes to rss templates are needed becouse output of php's date function (used for formating date/time strings) is now localized in 4.1.5, and if you have non-english language in use (and you have required strings in language file) you could have problems with some feed readers, these few changes make sure that date/time strings are in standardized format (english month names, that is).