• U branches/dev-2006.10-MarkupAndSpamFilterAndMetaUsers/backend/subversion/sv_extra_svn_postcommit_brigde.pl
• U branches/dev-2006.10-MarkupAndSpamFilterAndMetaUsers/frontend/php/include/trackers/format.php

Do no longer include list of changed files in the comment added. It can too easily break the layout (long lines with no space within) and the link to the revision on viewcvs should be enough (task #2594)

(Browse SVN revision 6254)

• U branches/dev-2006.10-MarkupAndSpamFilterAndMetaUsers/frontend/php/include/trackers/data.php
• U branches/dev-2006.10-MarkupAndSpamFilterAndMetaUsers/frontend/php/include/trackers/format.php

Add the frontend counterpart of task #2594

(Browse SVN revision 6252)

I guess this question would not matter so much.

We can write this assuming that:
- username on the system eq savane username
- if user got write access on the repository, he is obviously
project member
- if item belong to this group, the commit log is relevant to
the items mentioned

We could improve the thing later, but first it would be helpful to have a comment added automatically. Just that.
We can consider acceptable that no notification are sent, because commits are already sent to mailing-lists. If twenty commits are posted and would then get notif also on the item, that could be a real nuisance.
(indeed, this is questionable, but the point here is to avoid reimplementing parts of the frontend in the backend, if we can)

I would save me lot of time this month if a frontend for cvs/svn was able to close item with a comment on the tracker.

Or maybe not close items but push a comment into the database and set the status to "Ready For Test".